Random X crashes - radeon m 7500
alexdeucher at gmail.com
Mon Dec 1 16:14:21 PST 2008
On Sun, Nov 30, 2008 at 1:41 AM, Dave Wood <dave at unrealize.co.uk> wrote:
> In the kast few days I've had quite a few X crashes. I tried to attach
> process to gdb but I had some internal errors and locked up my laptop when
> I tried to switch back to vt 7. This is a radeon M 7500
> Is there some way of debugging this without gdbm or does anyone have any
> ideas what the cause might be?
> Googling produces some results but they seem to be various and I haven't
> found any solution.
Do either of the following options help?
Option "AccelMethod" "EXA"
Option "RenderAccel" "FALSE"
> Here is the end of my xorg log:
> 0: /usr/bin/X(xf86SigHandler+0x7e) [0x80bf1ee]
> 1: [0xffffe420]
> 2: /usr/lib/xorg/modules//libxaa.so [0xb798aded]
> 3: /usr/bin/X [0x8168704]
> 4: /usr/bin/X(CompositeGlyphs+0x9a) [0x814fd8a]
> 5: /usr/bin/X [0x8157648]
> 6: /usr/bin/X [0x8152aa5]
> 7: /usr/bin/X [0x814620e]
> 8: /usr/bin/X(Dispatch+0x2bf) [0x808688f]
> 9: /usr/bin/X(main+0x48b) [0x806ddab]
> 10: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d5a390]
> 11: /usr/bin/X(FontFileCompleteXLFD+0x20d) [0x806d121]
> Fatal server error:
> Caught signal 11. Server aborting
Any chance you could get a proper backtrace with gdb?
More information about the xorg