Backtrace: 0: /usr/bin/X(xf86SigHandler+0x89) [0x80b67d9] 1: [0xffffe420] 2: /usr/lib/xorg/modules/drivers/atimisc_drv.so [0xb79c65a0] 3: /usr/bin/X [0x80c8dfd] 4: /usr/lib/xorg/modules/extensions/libextmod.so(XvdiPutImage+0x169) [0xb7cb1ab9] 5: /usr/lib/xorg/modules/extensions/libextmod.so [0xb7cb4c2f] 6: /usr/bin/X(Dispatch+0x19b) [0x8086b3b] 7: /usr/bin/X(main+0x48e) [0x806e5de] 8: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7d93ea8] 9: /usr/bin/X(FontFileCompleteXLFD+0xad) [0x806d911] driver: ATI, card: ati 3d rage pro AIW (MACH64GT 8MB) Section "Module" # Load "GLcore" # Load "bitmap" # Load "dbe" # Load "ddc" Load "dri" Load "extmod" Load "freetype" Load "glx" # Load "int10" # Load "pex5" # Load "record" # Load "speedo" Load "type1" # Load "vbe" # Load "xie" EndSection DRI doesn't load, glx would not work latest debian unstable Linux 2.6.17 #4 PREEMPT Tue Aug 22 18:19:50 EEST 2006 i686 GNU/Linux hope that helps
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
My very verbose Debian bug report can be seen at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430067 This seems to happen to me SOMETIMES when I run mplayer. My Backtrace: 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8591] 1: /lib/libc.so.6 [0xb7dbfe28] 2: /usr/lib/xorg/modules/drivers//atimisc_drv.so [0xb7bd406e] 3: /usr/bin/X [0x80dc8bf] 4: /usr/lib/xorg/modules/extensions//libextmod.so(XvdiPutImage+0x174) [0xb7c933$ 5: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7c96398] 6: /usr/bin/X [0x81549be] 7: /usr/bin/X(Dispatch+0x19f) [0x808ed3f] 8: /usr/bin/X(main+0x495) [0x8076e85] 9: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7dabebc] 10: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x80761a1] Fatal server error: Caught signal 11. Server aborting
I wonder if this bug is driver or server specific. We got a recent bug report with intel driver 2.2.1 crashing in XvdiPutImage. And there's an old one about radeon (seems to be fixed though). Is there something similar to fix in all drivers? or can this be fixed in the server?
(In reply to comment #2) > My very verbose Debian bug report can be seen at > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430067 > > This seems to happen to me SOMETIMES when I run mplayer. > > My Backtrace: > 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8591] > 1: /lib/libc.so.6 [0xb7dbfe28] > 2: /usr/lib/xorg/modules/drivers//atimisc_drv.so [0xb7bd406e] > 3: /usr/bin/X [0x80dc8bf] > 4: /usr/lib/xorg/modules/extensions//libextmod.so(XvdiPutImage+0x174) > [0xb7c933$ > 5: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7c96398] > 6: /usr/bin/X [0x81549be] > 7: /usr/bin/X(Dispatch+0x19f) [0x808ed3f] > 8: /usr/bin/X(main+0x495) [0x8076e85] > 9: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7dabebc] > 10: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x80761a1] > > Fatal server error: > Caught signal 11. Server aborting > It just happened to me while running mplayer. Backtrace: 0: /usr/bin/X(xorg_backtrace+0x3b) [0x813277b] 1: /usr/bin/X(xf86SigHandler+0x9e) [0x80bd86e] 2: [0xb7f39400] 3: /usr/lib/xorg/modules/drivers//radeon_drv.so(RADEONCopyData+0x117) [0xb7975577] 4: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7977a0f] 5: /usr/bin/X [0x80de5de] 6: /usr/lib/xorg/modules/extensions//libextmod.so(XvdiPutImage+0x186) [0xb79fe8e6] 7: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7a025c2] 8: /usr/lib/xorg/modules/extensions//libextmod.so(ProcXvDispatch+0x3a) [0xb7a039da] 9: /usr/bin/X(Dispatch+0x347) [0x808c857] 10: /usr/bin/X(main+0x3ad) [0x807201d] 11: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7afba36] 12: /usr/bin/X [0x80714b1] Fatal server error: Caught signal 11. Server aborting --- lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc M24 1P [Radeon Mobility X600] --- Section "Module" Load "glx" ## Load "synaptics" ## Load "extmod" ## Load "GLcore" Load "dri" ## Load "record" Load "drm" ## Load "xtrap" ## Load "dbe" ## Load "freetype" EndSection
Is this still a problem?
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.