Bug#407875: X server dies with backtrace and signal 11
Sebastian Miele wrote: > Brice Goglin wrote: > >> Sebastian Miele wrote: >> > xorg sporadically dies with backtrace and signal 11 on a debian > GNU/Linux amd64 testing/etch system: > > >>> The person who owns the computer is happy with i386-debian now. Sorry. >>> >>> >> You mean that Xorg works fine in 32bits mode on this amd64 machine while >> the amd64 Xorg dies as reported in this bug initially ? >> > > Yepp > I am not sure what to do with this bug then. Do you think we should keep it open in case "the person who owns the computer" comes back to amd64-mode in the future? Is there at least any chance he tries some more recent xorg packages? If so, xserver-xorg-core 1.3 is now in unstable, and you will have to upgrade xserver-xorg-video-vesa in experimental (it should be in unstable within a couple days). Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#407875: X server dies with backtrace and signal 11
Brice Goglin wrote: > Sebastian Miele wrote: xorg sporadically dies with backtrace and signal 11 on a debian GNU/Linux amd64 testing/etch system: >> The person who owns the computer is happy with i386-debian now. Sorry. >> > > You mean that Xorg works fine in 32bits mode on this amd64 machine while > the amd64 Xorg dies as reported in this bug initially ? Yepp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#407875: X server dies with backtrace and signal 11
Sebastian Miele wrote: >>> xorg sporadically dies with backtrace and signal 11 on a debian >>> GNU/Linux amd64 testing/etch system: >>> > The person who owns the computer is happy with i386-debian now. Sorry. > You mean that Xorg works fine in 32bits mode on this amd64 machine while the amd64 Xorg dies as reported in this bug initially ? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#407875: X server dies with backtrace and signal 11
Julien Cristau wrote: > reassign 407875 xserver-xorg-core > thanks > > On Mon, Jan 22, 2007 at 02:23:59 +0100, Sebastian Miele wrote: > >> xorg sporadically dies with backtrace and signal 11 on a debian >> GNU/Linux amd64 testing/etch system: >> >> Backtrace: >> 0: /usr/bin/X11/X(xf86SigHandler+0x6d) [0x48c46d] >> 1: /lib/libc.so.6 [0x2b9607f74110] >> 2: /usr/bin/X11/X(WaitForSomething+0xa12) [0x5447e2] >> 3: /usr/bin/X11/X(Dispatch+0x8b) [0x44801b] >> 4: /usr/bin/X11/X(main+0x44d) [0x430f6d] >> 5: /lib/libc.so.6(__libc_start_main+0xda) [0x2b9607f614ca] >> 6: /usr/bin/X11/X(FontFileCompleteXLFD+0x9a) [0x43026a] >> >> Fatal server error: >> Caught signal 11. Server aborting >> > Hi Sebastian, > > could you upgrade the xserver-xorg-core package to the version from > experimental, and check if the crash still happens? > If it does, please rebuild the xorg-server package with debugging > symbols, and get a backtrace with gdb (you'll want to connect to the > machine via ssh to run gdb). > > Thanks, > Julien The person who owns the computer is happy with i386-debian now. Sorry. Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#407875: X server dies with backtrace and signal 11
On Mon, Mar 19, 2007 at 08:10:47PM +0100, Julien Cristau wrote: > Hi Eric, > > On Mon, Mar 19, 2007 at 19:29:39 +0100, Eric wrote: > > > > > Package: xserver-xorg > > Version: 1:7.1.0-15 > > > > My laptop (AMD Athlon Mobile 1200MHz running testing with Savage video > > chipset) triggers a similar bug when I try to restart X-Window. I need > > to reboot to get X working again. > > > > This bug seems to be the same as #60288 in Ubuntu. See > > https://launchpad.net/ubuntu/+source/xorg-server/+bug/60288 . > > A patch is provided there. It also might be already fixed upstream (in > > Xorg 7.2 as stated in https://bugs.freedesktop.org/show_bug.cgi?id=8537 ). > > > Your log doesn't seem to have anything to do with any of those bugs, or, > for that matter, Debian bug #407875. Please open a new report when you > have a different problem (if the backtrace printed in the X log is > significantly different, as is the case here, chances are you're hitting > a different bug). > > > I applied the patch provided in Ubuntu BTS then rebuilt and installed > > xserver-xorg which now seems to work. No more signal 11 when I restart > > X. > > That's surprising, given that the backtrace you included below doesn't > seem to be related to the code this patch touches. Hello Julien, from what I read at different places, I thought this bug were related to a call to FontFileCompleteXLFD using, somewhere deep into its call tree, an uninitialized, or not fully initialized, DRIScreenPrivPtr. Even in my stacktrace the problem is not shown into the dri library itself but, in effect, some changes to the content of the structure pointed to by this DRIScreenPrivPtr could lead to memory corruption, and such memory corruption could trigger a segfault later on. Sorry if I did it wrong. I will open a new bug if you'd rather like. Tell me. > > So, when would you plan to upgrade to 7.2 in testing? > > > Never. Etch will release with xserver 1.1, lenny will have xserver 1.3 > when etch is released. Ok, so could you apply the patch provided by Ubuntu please? It's rather annoying to have to reboot after each logout to get X working again (and I did not stressed X to discover all other usecases related to this bug). Best regards, Eric. -- Eric Delaunay | Le travail est trop sérieux pour le confier [EMAIL PROTECTED] | à ceux qui veulent se tuer avec.Jissey. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#407875: X server dies with backtrace and signal 11
Hi Eric, On Mon, Mar 19, 2007 at 19:29:39 +0100, Eric wrote: > > Package: xserver-xorg > Version: 1:7.1.0-15 > > My laptop (AMD Athlon Mobile 1200MHz running testing with Savage video > chipset) triggers a similar bug when I try to restart X-Window. I need > to reboot to get X working again. > > This bug seems to be the same as #60288 in Ubuntu. See > https://launchpad.net/ubuntu/+source/xorg-server/+bug/60288 . > A patch is provided there. It also might be already fixed upstream (in > Xorg 7.2 as stated in https://bugs.freedesktop.org/show_bug.cgi?id=8537 ). > Your log doesn't seem to have anything to do with any of those bugs, or, for that matter, Debian bug #407875. Please open a new report when you have a different problem (if the backtrace printed in the X log is significantly different, as is the case here, chances are you're hitting a different bug). > I applied the patch provided in Ubuntu BTS then rebuilt and installed > xserver-xorg which now seems to work. No more signal 11 when I restart > X. That's surprising, given that the backtrace you included below doesn't seem to be related to the code this patch touches. > So, when would you plan to upgrade to 7.2 in testing? > Never. Etch will release with xserver 1.1, lenny will have xserver 1.3 when etch is released. > Best regards, > Eric. > > - excerpt of /var/log/Xorg.0.log - > (II) SAVAGE(0): Primary V_BIOS segment is: 0xc000 > (EE) SAVAGE(0): vm86() syscall generated signal 11. > (II) SAVAGE(0): EAX=0x4f00, EBX=0x, ECX=0x, EDX=0x > (II) SAVAGE(0): ESP=0x0ffa, EBP=0x, ESI=0x, EDI=0x2000 > (II) SAVAGE(0): CS=0x, SS=0x0100, DS=0x0040, ES=0x, FS=0x, > GS=0x > (II) SAVAGE(0): EIP=0x, EFLAGS=0x00033202 > (II) SAVAGE(0): code at 0x0010ffef: > > Backtrace: > 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354] > 1: [0xb7fac420] > 2: /usr/lib/xorg/modules/libvm86.so(xf86ExecX86int10+0xdf) [0xb7bf449f] > 3: /usr/lib/xorg/modules/libvbe.so(VBEExtendedInit+0x90) [0xb7c3b820] > 4: /usr/lib/xorg/modules/libvbe.so(VBEInit+0x2a) [0xb7c3bc2a] > 5: /usr/lib/xorg/modules/drivers/savage_drv.so [0xb7c24045] > 6: /usr/bin/X(InitOutput+0x9e4) [0x80a0504] > 7: /usr/bin/X(main+0x276) [0x806e486] > 8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7dadea8] > 9: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806d9d1] > -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#407875: X server dies with backtrace and signal 11
reassign 407875 xserver-xorg-core thanks On Mon, Jan 22, 2007 at 02:23:59 +0100, Sebastian Miele wrote: > xorg sporadically dies with backtrace and signal 11 on a debian > GNU/Linux amd64 testing/etch system: > > Backtrace: > 0: /usr/bin/X11/X(xf86SigHandler+0x6d) [0x48c46d] > 1: /lib/libc.so.6 [0x2b9607f74110] > 2: /usr/bin/X11/X(WaitForSomething+0xa12) [0x5447e2] > 3: /usr/bin/X11/X(Dispatch+0x8b) [0x44801b] > 4: /usr/bin/X11/X(main+0x44d) [0x430f6d] > 5: /lib/libc.so.6(__libc_start_main+0xda) [0x2b9607f614ca] > 6: /usr/bin/X11/X(FontFileCompleteXLFD+0x9a) [0x43026a] > > Fatal server error: > Caught signal 11. Server aborting > Hi Sebastian, could you upgrade the xserver-xorg-core package to the version from experimental, and check if the crash still happens? If it does, please rebuild the xorg-server package with debugging symbols, and get a backtrace with gdb (you'll want to connect to the machine via ssh to run gdb). Thanks, Julien signature.asc Description: Digital signature
Bug#407875: X server dies with backtrace and signal 11
Package: xserver-xorg Version: 1:7.1.0-15 My laptop (AMD Athlon Mobile 1200MHz running testing with Savage video chipset) triggers a similar bug when I try to restart X-Window. I need to reboot to get X working again. This bug seems to be the same as #60288 in Ubuntu. See https://launchpad.net/ubuntu/+source/xorg-server/+bug/60288 . A patch is provided there. It also might be already fixed upstream (in Xorg 7.2 as stated in https://bugs.freedesktop.org/show_bug.cgi?id=8537 ). I applied the patch provided in Ubuntu BTS then rebuilt and installed xserver-xorg which now seems to work. No more signal 11 when I restart X. So, when would you plan to upgrade to 7.2 in testing? Best regards, Eric. - excerpt of /var/log/Xorg.0.log - (II) SAVAGE(0): Primary V_BIOS segment is: 0xc000 (EE) SAVAGE(0): vm86() syscall generated signal 11. (II) SAVAGE(0): EAX=0x4f00, EBX=0x, ECX=0x, EDX=0x (II) SAVAGE(0): ESP=0x0ffa, EBP=0x, ESI=0x, EDI=0x2000 (II) SAVAGE(0): CS=0x, SS=0x0100, DS=0x0040, ES=0x, FS=0x, GS=0x (II) SAVAGE(0): EIP=0x, EFLAGS=0x00033202 (II) SAVAGE(0): code at 0x0010ffef: Backtrace: 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354] 1: [0xb7fac420] 2: /usr/lib/xorg/modules/libvm86.so(xf86ExecX86int10+0xdf) [0xb7bf449f] 3: /usr/lib/xorg/modules/libvbe.so(VBEExtendedInit+0x90) [0xb7c3b820] 4: /usr/lib/xorg/modules/libvbe.so(VBEInit+0x2a) [0xb7c3bc2a] 5: /usr/lib/xorg/modules/drivers/savage_drv.so [0xb7c24045] 6: /usr/bin/X(InitOutput+0x9e4) [0x80a0504] 7: /usr/bin/X(main+0x276) [0x806e486] 8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7dadea8] 9: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806d9d1] -- -- Eric Delaunay | Le travail est trop sérieux pour le confier [EMAIL PROTECTED] | à ceux qui veulent se tuer avec.Jissey. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
