Summary: | glxinfo causes graphics lockup on mga G450 | ||
---|---|---|---|
Product: | xorg | Reporter: | 3rg34mw02 |
Component: | Driver/mga | Assignee: | Tilman Sauerbeck <tilman> |
Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | high | CC: | ajax, idr, jeremyhu |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | 2011BRB_Reviewed | ||
i915 platform: | i915 features: |
Description
3rg34mw02
2006-11-19 15:39:07 UTC
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.