When running with 3d acceleration turned on on a gentoo system using xorg-server-1.1.99.902 with xf86-video-mga-1.4.4 on a Matrox G450, running glxinfo crashes the X server, leaving the computer in a state the only rebooting can recover from. (I don't have another computer I could use to log in to it via the network, so I can't tell the exact state.) Oddly, some 3d programs (such as glxgears) work fine. Configuration and log files attached to the gentoo bug here: <https://bugs.gentoo.org/show_bug.cgi?id=155444> May be related to the freedesktop bug 8666, but notice that in my case glxgears (and some other 3d programs) work, while glxinfo crashes. The traceback of the crash is: Backtrace: 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c0334] 1: [0xb7f3d420] 2: /usr/lib/xorg/modules/extensions//libGLcore.so(XMesaCreateContext+0x7d) [0xb0cca10d] 3: /usr/lib/xorg/modules/extensions//libGLcore.so [0xb0cc6fe7] 4: /usr/lib/xorg/modules/extensions//libglx.so(DoCreateContext+0x10f) [0xb7bff94f] 5: /usr/lib/xorg/modules/extensions//libglx.so [0xb7bffb44] 6: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c01a0c] 7: /usr/bin/X [0x813c7de] 8: /usr/bin/X(Dispatch+0x1ab) [0x808685b] 9: /usr/bin/X(main+0x489) [0x806e619] 10: /lib/libc.so.6(__libc_start_main+0xd8) [0xb7cbd878] 11: /usr/bin/X(FontFileCompleteXLFD+0xa5) [0x806d951] Fatal server error: Caught signal 11. Server aborting Like bug 8666, this is followed by lots of "(EE) MGA(0): [dri] Idle timed out, resetting engine...", and the system is locked up.
Looking at that stack trace, it appears that the crash only happens with indirect rendering. If I'm not mistaken, it should never go into libGLcore with direct rendering. Can you try running "LIBGL_ALWAYS_INDIRECT=y glxgears"? If my hunch is correct, that will reproduce the crash.
I tried "env LIBGL_ALWAYS_INDIRECT=y glxgears" (I use tcsh rather than bash), and there was no crash. (Also, when I'm running with xinerama turned on, which disables DRI, then 3d applications don't crash X, though of course they generally run unacceptably slowly.) However, on a whim I tried running "env LIBGL_ALWAYS_INDIRECT=n glxgears", and I did get a crash, though the traceback is different: Backtrace: 0: X(xf86SigHandler+0x84) [0x80c0334] 1: [0xb7f8a420] 2: /usr/lib/dri/mga_dri.so(__driUtilUpdateDrawableInfo+0x137) [0xb3117297] 3: /usr/lib/dri/mga_dri.so(mgaUpdateRects+0xc0) [0xb311fd40] 4: /usr/lib/dri/mga_dri.so(mgaGetLock+0x7b) [0xb315f65b] 5: /usr/lib/dri/mga_dri.so [0xb311bcba] 6: /usr/lib/dri/mga_dri.so(_mesa_Clear+0x17f) [0xb327de3f] 7: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c51979] 8: /usr/lib/xorg/modules/extensions//libglx.so(DoRender+0x175) [0xb7c4a575] 9: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c4a5fa] 10: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c4ea0c] 11: X [0x813c7de] 12: X(Dispatch+0x1ab) [0x808685b] 13: X(main+0x489) [0x806e619] 14: /lib/libc.so.6(__libc_start_main+0xd8) [0xb7d0a878] 15: X(FontFileCompleteXLFD+0xa5) [0x806d951] Setting LIBGL_ALWAYS_INDIRECT to either y or n had no effect on the glxinfo crash that I could tell.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
We're getting a similar backtrace on a Dimension E520 when running with the vesa driver: https://bugs.launchpad.net/xorg-server/+bug/119341
The bug from comment #4 was resolved due to a backported patch as of xserver 12ubuntu4
Is this still an issue?
glcore is no longer a thing, and neither is mga's 3d support.
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.