[gutsy] x sometimes crashes on resume from suspend

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in xorg.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/lib/xorg/modules//libfb.so(fbFillRegionSolid+0xd5) [0xb7afbd75]
3: /usr/lib/xorg/modules//libfb.so(fbPaintWindow+0xb3) [0xb7afbed3]
4: /usr/lib/xorg/modules//libxaa.so(XAAPaintWindow+0x150) [0xb7aa11a0]
5: /usr/bin/X [0x817ca2e]
6: /usr/bin/X [0x81780f1]
7: /usr/bin/X(compPaintWindowBackground+0x6d) [0x810a77d]
8: /usr/bin/X(miWindowExposures+0xfa) [0x81265ea]
9: /usr/bin/X [0x80debbc]
10: /usr/lib/xorg/modules/extensions//libdri.so(DRIWindowExposures+0x89) [0xb7c6caf9]
11: /usr/bin/X(miHandleValidateExposures+0x78) [0x813e168]
12: /usr/bin/X(MapWindow+0x3e7) [0x807b857]
13: /usr/bin/X(ProcMapWindow+0x59) [0x808edb9]
14: /usr/bin/X [0x81575b1]
15: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
16: /usr/bin/X(main+0x495) [0x8076f05]
17: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7de0050]
18: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

Please test against Hardy alpha2 or newer to see if the crash still occurs.

Fwiw, XAA acceleration (which appears to be involved in this crash) will be deprecated in favor of EXA. So I suspect this crash will not be present as of Hardy alpha2. If you can confirm that, it'd be a great help.

I have a very similar issue ... X crashes on resume from suspend-to-RAM, so I lose my session and end up at the login screen. This only seems to happen when compiz is running. Here is the backtrace from /var/log/Xorg.0.log. I'm running gutsy on a MacBook Pro Core 2 Duo with the fglrx driver using AIGLX (no Xgl). Another odd thing is that I can't get to a text virtual terminal (Ctrl+Alt+ F1) if I run compiz.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xb7f98420]
2: /usr/lib/xorg/modules//libfb.so(fbCopyWindowProc+0x149) [0xb77082d9]
3: /usr/lib/xorg/modules//libfb.so(fbSaveAreas+0x7a) [0xb76f052a]
4: /usr/lib/xorg/modules//libxaa.so [0xb7695ee9]
5: /usr/bin/X [0x8120ddb]
6: /usr/bin/X [0x8137441]
7: /usr/bin/X(miValidateTree+0x400) [0x8138540]
8: /usr/lib/xorg/modules/extensions//libdri.so(DRIValidateTree+0x57) [0xb7c31b87]
9: /usr/bin/X(miMoveWindow+0x247) [0x813ea97]
10: /usr/bin/X(compMoveWindow+0xad) [0x810b67d]
11: /usr/bin/X(ConfigureWindow+0x775) [0x807c765]
12: /usr/bin/X(ProcConfigureWindow+0xa1) [0x808ebf1]
13: /usr/bin/X [0x81575b1]
14: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
15: /usr/bin/X(main+0x495) [0x8076f05]
16: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dac050]
17: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

I tried to disable xaa and load exa but failed. Here are the lines from Xorg.0.log

(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
dlopen: /usr/lib/xorg/modules//libexa.so: undefined symbol: fbGlyph8
(EE) Failed to load /usr/lib/xorg/modules//libexa.so
(II) UnloadModule: "exa"
(EE) Failed to load module "exa" (loader failed, 7)

I've attached my xorg.conf. Any ideas?

Seems related to https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/165093

Shiv, your issue looks to be unrelated to Mario's (the backtraces dont' match up). If you're running on Gutsy, the xserver we shipped in it didn't support EXA with -intel. Please re-test against Hardy, which should allow loading exa.

Mario, could you also test against Hardy to see if the crash still occurs?

Here is my backtrace, on a HP/Compaq nx6110 laptop.

00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1]
1: [0xffffe420]
2: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b46022]
3: /usr/bin/X(xf86CrtcSetMode+0x279) [0x80fafb9]
4: /usr/lib/xorg/modules/drivers//intel_drv.so(i830GetLoadDetectPipe+0x151) [0xb7b465e1]
5: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b42219]
6: /usr/bin/X(xf86ProbeOutputModes+0x188) [0x80f8fb8]
7: /usr/bin/X [0x80feb71]
8: /usr/bin/X(RRGetInfo+0x89) [0x8170729]
9: /usr/bin/X(ProcRRGetScreenSizeRange+0x8a) [0x817426a]
10: /usr/bin/X [0x816dda5]
11: /usr/bin/X [0x815765e]
12: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
13: /usr/bin/X(main+0x495) [0x8076f05]
14: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d0d050]
15: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

I'll test with Hardy too in a couple of days. The point is, i don't have a way to reproduce this bug, i just occurs suddenly (which makes it even nastier).

Bram, your backtrace also does not match up to Ryan's so is likely an unrelated bug. Please report it separately. It would be great if you could get a 'full backtrace'. You can ssh into the box when it has crashed from another system and attach gdb to Xorg to get it. (see https://wiki.ubuntu.com/DebuggingXorg for directions)

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the package name, under the Affects column, and change the Status back to "New". Thanks again!