If I run gnome-shell long enough on my x86_64 intel video box, it will eventually crash: Program received signal SIGSEGV, Segmentation fault. drm_intel_bo_subdata (bo=0x0, offset=0, size=112, data=0x7fff454ef150) at intel_bufmgr.c:94 94 if (bo->bufmgr->bo_subdata) (gdb) bt full #0 drm_intel_bo_subdata (bo=0x0, offset=0, size=112, data=0x7fff454ef150) at intel_bufmgr.c:94 ret = <value optimized out> #1 0x00007f0dc0e3d9b6 in _mesa_meta_Clear (ctx=0x2d19980, buffers=<value optimized out>) at drivers/common/meta.c:1307 x0 = <value optimized out> y1 = <value optimized out> i = <value optimized out> y0 = <value optimized out> x1 = <value optimized out> z = <value optimized out> clear = <value optimized out> verts = {{x = 0, y = 0, z = -1, r = 0.13333334, g = 0.400000006, b = 0.733333349, a = 1}, {x = 1920, y = 0, z = -1, r = 0.13333334, g = 0.400000006, b = 0.733333349, a = 1}, {x = 1920, y = 1200, z = -1, r = 0.13333334, g = 0.400000006, b = 0.733333349, a = 1}, { x = 0, y = 1200, z = -1, r = 0.13333334, g = 0.400000006, b = 0.733333349, a = 1}} metaSave = <value optimized out> __PRETTY_FUNCTION__ = "_mesa_meta_Clear" #2 0x00007f0dc11121d2 in intelClear (ctx=0x2d19980, mask=<value optimized out>) at intel_clear.c:175 intel = 0x2d19980 tri_mask = 2 blit_mask = <value optimized out> swrast_mask = 0 fb = <value optimized out> i = <value optimized out> #3 0x00007f0dc26b4723 in __glXDisp_Render (cl=<value optimized out>, pc=<value optimized out>) at glxcmds.c:1823 entry = {bytes = 8, varsize = 0} extra = <value optimized out> proc = 0x7f0dc2692740 <__glXDisp_Clear> err = <value optimized out> req = <value optimized out> client = 0x2c37df0 left = <value optimized out> cmdlen = <value optimized out> error = 0 commandsDone = <value optimized out> hdr = 0x272ad6c glxc = 0x2d4d510 sw = <value optimized out> #4 0x00007f0dc26b892e in __glXDispatch (client=0x2c37df0) at glxext.c:578 rendering = <value optimized out> stuff = 0x272ad50 opcode = <value optimized out> cl = 0x21f3110 retval = <value optimized out> #5 0x000000000042c60c in Dispatch () at dispatch.c:445 result = <value optimized out> client = 0x2c37df0 nready = <value optimized out> start_tick = 987380 #6 0x0000000000421c9a in main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at main.c:285 i = <value optimized out> alwaysCheckForInput = {0, 1} (--) PCI:*(0:0:2:0) 8086:29b2:8086:4f4a Intel Corporation 82Q35 Express Integrat ed Graphics Controller rev 2, Mem @ 0x90380000/524288, 0x80000000/268435456, 0x9 0200000/1048576, I/O @ 0x00002488/8, BIOS @ 0x????????/131072 (--) PCI: (0:0:2:1) 8086:29b3:8086:4f4a Intel Corporation 82Q35 Express Integrat ed Graphics Controller rev 2, Mem @ 0x90300000/524288, BIOS @ 0x????????/65536 xorg-x11-server-Xorg-1.7.0-1.fc12.x86_64 xorg-x11-drv-intel-2.9.0-2.fc12.x86_64 mesa-*-7.6-0.13.fc12.x86_64 libdrm-2.4.14-1.fc12.x86_64
Actually this appears to just be memory corruption somewhere, and I can reproduce it by just starting emacs and then exiting it repeatedly. (So far it has always crashed by the 4th time.) I tried valgrinding the X server but I'm running into that strcmp_ssse3 problem
(In reply to comment #1) > Actually this appears to just be memory corruption somewhere, and I can > reproduce it by just starting emacs and then exiting it repeatedly. ie, not in gnome-shell
This is fixed by http://cgit.freedesktop.org/xorg/xserver/commit/?id=4970666827e65424ee17ccf6341ff84aac974383 it's a one-liner: - memset(reply + c->length, 0, length - c->length); + memset((char*)reply + c->length, 0, length - c->length);
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
The latest package in updates is 1.7.0-5, which does not have the fix. but I see 1.7.1 packages in koji, which do have the fix.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
this has been fixed since F13