ubuntu-x-swat team mailing list archive

[Bryce Harrington <720381@xxxxxxxxxxxxxxxxxx>]

Hmm, unfortunately the retracer wasn't able to generate a useful stack
trace.  I've asked them to turn it off, so I can manually get a
stacktrace next time someone reports this bug.  If you or one of the
folks on dupes wouldn't mind creating a new install with latest natty
bits and reproducing the bug, and re-filing it with apport, it would be
a huge help.

For some background...  we have been chasing this elusive memory hogging
beast through several bug reports now.  We can detect it by seeing the
following printed in the Xorg.0.log:

[   192.437] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Cannot allocate memory
[   192.437] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Cannot allocate memory
[   192.437] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Cannot allocate memory
[   192.437] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Cannot allocate memory
[   192.439] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Cannot allocate memory
[   192.439] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Cannot allocate memory
[   192.439] 
Backtrace:
[   192.439] 0: X (xorg_backtrace+0x3b) [0x80e94cb]
...

In other words, the system runs itself out of memory, and then X can't
deal with that situation (seems it's not well tested in 0-memory
conditions), and it crashes.  I've been fixing those crashes and sending
the patches along upstream, but that's treating the symptom not the
disease.  What we really need to do is sort out what is causing the out-
of-memory condition.

So far, us developers have not been able to figure out exactly how to
reproduce this bug.  But it's been reported widely enough that I figure
there must be a set of steps that reliably reproduce it, and we just
don't have a clear understanding of what those steps are.

This is where you can help - please note down every thing you did to
create your USB installation.  I mean everything... what username did
you pick?  How large is the USB key?  What language did you pick?  How
much space did you set persistent?  What did you install after setting
up the key?  What applications have you been running?  Anything and
everything that might or might not be significant.

Thanks, I know it'll probably be a good bit of work to collect all this
info, but this Moby Dick has been hitting a lot of different people
trying to do testing and I'd love to be able to harpoon it and kill it
once and for all.


** Changed in: xorg-server (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
https://bugs.launchpad.net/bugs/720381

Title:
  Xorg crashed with SIGSEGV in _start()