[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
Some of these crashes (at least Peter's) are probably bug #60288. Please try the test package in that bug report if you can. -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
Tremaine Lea [EMAIL PROTECTED] writes: That said, I do rather hope this gets fixed as I rather like having a screensaver that will lock my station when I forget to do it myself. I just removed xscreensaver-gl, not xscreensaver itself. -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
I think I can add a vote for the screensaver triggering the problem in my instance. Based on the initial reporters experience I disabled my own xscreensaver and haven't had a crash since. That said, I do rather hope this gets fixed as I rather like having a screensaver that will lock my station when I forget to do it myself. -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
I'm getting these crashes at least twice daily on my system and have also reported the issue as a bug at https://bugs.freedesktop.org/show_bug.cgi?id=9399 ** Attachment added: Xorg.0.log.old http://librarian.launchpad.net/5481558/Xorg.0.log.old -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
I've also attached my xorg.conf if it helps. ** Attachment added: xorg.conf http://librarian.launchpad.net/5481559/xorg.conf -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
I saw this again on my system, this time on a single-head setup with just the r128. Again while running googleearth. This time the server wasn't able to recover from the segfault and restore text mode, and went into an infinite loop. I had to send it a SIGKILL before it would die. Xorg.0.log is 3.8GB (although 7zip takes it down to 568kB, an impressive factor of 7000). Google Earth ran ok once (although flickery). I turned off aniso filtering and reduced the detail level, and set texture depth to 16bit. Then I exited and started it again. This time X froze while its splash screen was up. I sshed in from another machine to kill it, but the X server kept writing its log file (and the kernel log file was growing too; up to 218MB). Backtrace: 0: /usr/X11R6/bin/X(xf86SigHandler+0x71) [0x480b81] 1: /lib/libc.so.6 [0x2b3fd2948510] 2: /lib/libc.so.6(memcpy+0x60) [0x2b3fd298eb10] 3: /usr/lib/xorg/modules/extensions/libglx.so [0x2b3fd360384e] 4: /usr/lib/dri/r128_dri.so(__driUtilUpdateDrawableInfo+0x10a) [0x2b3fd5af9448] 5: /usr/lib/dri/r128_dri.so [0x2b3fd5af98ca] 6: /usr/lib/xorg/modules/extensions/libglx.so [0x2b3fd3602aa1] 7: /usr/lib/xorg/modules/extensions/libglx.so(DoMakeCurrent+0x42d) [0x2b3fd35e1c 7d] 8: /usr/lib/xorg/modules/extensions/libglx.so [0x2b3fd35e459a] 9: /usr/X11R6/bin/X(Dispatch+0x1ba) [0x4483aa] 10: /usr/X11R6/bin/X(main+0x455) [0x431035] 11: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b3fd29350c4] 12: /usr/X11R6/bin/X(FontFileCompleteXLFD+0xa1) [0x430339] Fatal server error: Caught signal 11. Server aborting (II) AIGLX: Suspending AIGLX clients for VT switch (EE) R128(0): R128CCEWaitForIdle: CCE idle -22 (EE) R128(0): Idle timed out, resetting engine... (EE) R128(0): R128CCEWaitForIdle: CCE stop -22 (EE) R128(0): R128CCEWaitForIdle: CCE reset -22 (EE) R128(0): R128CCEWaitForIdle: CCE start -22 (EE) R128(0): R128CCEWaitForIdle: CCE idle -22 (EE) R128(0): Idle timed out, resetting engine... (EE) R128(0): R128CCEWaitForIdle: CCE stop -22 (EE) R128(0): R128CCEWaitForIdle: CCE reset -22 (EE) R128(0): R128CCEWaitForIdle: CCE start -22 (EE) R128(0): R128CCEWaitForIdle: CCE idle -22 I don't think you need to see 3.8GB of that. It compresses that well because it's pretty redundant... kernel: Dec 14 02:27:00 tesla kernel: [ 212.047457] [drm] Initialized drm 1.1.0 20060810 Dec 14 02:27:00 tesla kernel: [ 212.048563] ACPI: PCI Interrupt :00:02.0[A] - GSI 16 (level, low) - IRQ 16 Dec 14 02:27:00 tesla kernel: [ 212.048693] [drm] Initialized i915 1.6.0 20060119 on minor 0 Dec 14 02:50:23 tesla kernel: [ 1614.136780] ACPI: PCI Interrupt :06:01.0[A] - GSI 22 (level, low) - IRQ 22 Dec 14 02:50:23 tesla kernel: [ 1614.136937] [drm] Initialized r128 2.5.0 20030725 on minor 1 Dec 14 03:54:23 tesla kernel: [ 5454.112739] [drm:r128_cce_idle] *ERROR* r128_cce_idle called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112763] [drm:r128_cce_stop] *ERROR* r128_cce_stop called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112780] [drm:r128_cce_reset] *ERROR* r128_cce_reset called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112787] [drm:r128_cce_start] *ERROR* r128_cce_start called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112794] [drm:r128_cce_idle] *ERROR* r128_cce_idle called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112805] [drm:r128_cce_stop] *ERROR* r128_cce_stop called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112820] [drm:r128_cce_reset] *ERROR* r128_cce_reset called without lock held Dec 14 03:54:23 tesla kernel: [ 5454.112827] [drm:r128_cce_start] *ERROR* r128_cce_start called without lock held repeating, sometimes so fast that the dd reading kmsg couldn't keep up, and the messages got corrupted. -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
It's probably important to note that the r128 card was not the system's primary vid card. The text console was on the internal g965, and that's the hardware the BIOS POSTed; my BIOS is explicitly set to use the internal vga as the primary VGA device. X servers that start after the nasty hang that required SIGKILLing the X server all crash. They seem to be using the g965 video BIOS with the r128, even though the r128 is the only device configured. There's a line in the log like (II) R128(0): VESA VBE Total Mem: 262080 kB (II) R128(0): VESA VBE OEM: Intel(r)Broadwater-G Graphics Chip Accelerated VGA BIOS *snicker* that's some confused hardware. A reboot took care of it... Also, all X backtraces seem to include FontFileCompleteXLFD. I was confused before about which direction the backtrace was going and thought it was significant; F.F.C.XLFD is somehow showing up as the parent of _libc_start_main. So X must do something to the stack that the backtracer doesn't like. It's obviously not significant that all the backtraces have the same parent, since it's the same program. Sorry for any confusion. -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
** Attachment added: gdm log file http://librarian.launchpad.net/5377767/%3A0.log.1 -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
I guess I'm the fourth person with an X crash in FontFileCompleteXLFD. Other reports are: https://bugs.launchpad.net/distros/ubuntu/+source/xorg-server/+bug/68135 https://bugs.launchpad.net/distros/ubuntu/+source/xorg-server/+bug/67613 I have a Core 2 Duo on an Intel DG965WH (g965 graphics), running AMD64 Ubuntu Edgy. 3D was fine (except for no s3tc) with the i965 driver. Then I put in an r128 AIW card and enabled Xinerama, which disables DRI. (And I guess any indirect accel, too.) Now googleearth (an ia32 binary; installed from the medibuntu repository) crashes my X server while starting. This seemed very repeatable, and happened even with latest upstream xf86-video-intel. (ge is a 32bit app that comes with its own libraries, so it wasn't using the 64bit libdrm or mesa client-side libs I compiled.) (The Xorg.0.log I attached was with the Edgy versions of everything, though.) Some other GL progs, like glxgears and tuxkart, ran without crashing (tuxkart slowly, glxgears pretty fast on this CPU :). ** Attachment added: X backtrace from googleearth-induced crash http://librarian.launchpad.net/5392191/Xorg.0.log.old.ubuntu.ge-crash -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75592] Re: libGLcore crash (probably screensaver-induced)
And with Xinerama disabled, running glxinfo on the second head (r128) makes the server segfault! That screen (:0.1) wasn't using DRI. I think the root cause was that the r128 kernel module wasn't loaded. Maybe there's another bug here somewhere, since X should cause the dri module to load like it does for i915 for the first head. The server's i810_drv.so is v1.7.3, that I compiled myself, and the client libGL and libdrm are also the latest git versions that I compiled locally. The only files outside of /usr/local that are locally compiled are i810_drv.so, and /usr/X11R6/lib/modules/dri. No, that isn't where ubuntu puts r128_dri.so, but that's where mesa 6.5.2 in /usr/local/lib looks for them... Err, /usr/lib/dri/* is from libgl1-mesa-dri, which I built locally from Ubuntu source, because I needed to compile with -fno-strict-aliasing for the i965 driver to work. Anyway, I'll attach my Xorg log file in the hope that it's of some use even though it's not with the Ubuntu versions of everything. It's a big pain to use Edgy's i810_drv.so, because it screws up the vid mode. I'll send this now before I do anything that risks crashing X and losing what I've typed in firefox, since I'm not running it in Xvnc or anything! ** Attachment added: Xorg log from glxinfo crash http://librarian.launchpad.net/5392246/Xorg.0.log.glxinfo-r128-second-head.crash -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
