Today using the restricted driver fglrx I received the same crash message about 7 times before reverting to Gutsy's xserver (and holding back updates on it). I did not see the "system lock up" I saw with the open source driver.
Backtrace: 0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e] 1: [0xb7f07420] 2: /usr/lib/xorg/modules//libxaa.so [0xb78c06dd] 3: /usr/bin/X [0x8172db4] 4: /usr/bin/X(CompositeGlyphs+0x9a) [0x815a33a] 5: /usr/bin/X [0x8161cc9] 6: /usr/bin/X [0x815d055] 7: /usr/bin/X [0x81506de] 8: /usr/bin/X(Dispatch+0x2cf) [0x808d8df] 9: /usr/bin/X(main+0x48b) [0x807471b] 10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7c8f450] 11: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91] Fatal server error: Caught signal 11. Server aborting Now I'm back with Gutsy's xserver and the open source radeon driver, and can confirm I can suspend / resume from mem just fine. I'll post later regarding stability.... -- regression hardy xserver radeon / fglrx - lockup - crash - fail to resume from mem https://bugs.launchpad.net/bugs/219896 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
