Bug 684188
| Summary: | [RV350] Xorg segfaults on reboot/shutdown from XFCE | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Panu Matilainen <pmatilai> | ||||||
| Component: | xorg-x11-server | Assignee: | Adam Jackson <ajax> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | mcepl, xgl-maint | ||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | Type: | --- | |||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 680764 | ||||||||
| Attachments: |
|
||||||||
|
Description
Panu Matilainen
2011-03-11 12:10:30 UTC
Could we get output of dmesg (after the crash, if it is possible to get to the console) and /var/log/messages, please? Most of the fun is now in the kernel, so unless we have a nice backtrace in /var/log/Xorg.0.log, we usually need these kernel messages as well. Thank you Sure... except that there is nothing in either dmesg or /var/log/messages related to the crash (other than abrtd noticing the crash), eg Mar 14 18:16:48 turre abrt[2402]: saved core dump of pid 1846 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-1300119407-1846.new/coredump (34922496 bytes) Mar 14 18:16:48 turre abrtd: Directory 'ccpp-1300119407-1846' creation detected Mar 14 18:16:48 turre gdm-simple-slave[1844]: DEBUG(+): GdmServer: child (pid:1846) done (signal:6) Mar 14 18:16:48 turre gdm-simple-slave[1844]: DEBUG(+): GdmSimpleSlave: server died with signal 6, (Aborted) [...continued gdm spew...] Xorg.0.log backtrace doesn't get full debug information despite the necessary -debuginfo packages being installed, but appears to be the same as the manually generated backtrace in original report: Backtrace: [ 1396.625] 0: /usr/bin/Xorg (xorg_backtrace+0x2f) [0x4a105f] [ 1396.625] 1: /usr/bin/Xorg (0x400000+0x620a6) [0x4620a6] [ 1396.625] 2: /lib64/libpthread.so.0 (0x31be000000+0xf4e0) [0x31be00f4e0] [ 1396.625] 3: /usr/bin/Xorg (ChangeGC+0x196) [0x440396] [ 1396.626] 4: /usr/bin/Xorg (miPaintWindow+0xf5) [0x458b85] [ 1396.626] 5: /usr/bin/Xorg (miWindowExposures+0xbc) [0x458dec] [ 1396.626] 6: /usr/bin/Xorg (0x400000+0x12b2be) [0x52b2be] [ 1396.626] 7: /usr/bin/Xorg (miHandleValidateExposures+0x74) [0x55ba54] [ 1396.626] 8: /usr/bin/Xorg (UnmapWindow+0x219) [0x4552d9] [ 1396.626] 9: /usr/bin/Xorg (0x400000+0x2951d) [0x42951d] [ 1396.626] 10: /usr/bin/Xorg (0x400000+0x2eab1) [0x42eab1] [ 1396.626] 11: /usr/bin/Xorg (0x400000+0x22d3a) [0x422d3a] [ 1396.626] 12: /lib64/libc.so.6 (__libc_start_main+0xed) [0x31bdc2131d] [ 1396.626] 13: /usr/bin/Xorg (0x400000+0x23021) [0x423021] [ 1396.626] Segmentation fault at address 0x2 [ 1396.627] Fatal server error: [ 1396.627] Caught signal 11 (Segmentation fault). Server aborting [ 1396.627] [ 1396.627] Additional data points: I'm seeing this on Thinkpad T60 (Intel 945GM) too, so it's not limited to just Radeon. I'll grab a proper backtrace at when I've more time, but at least the symptom is exactly the same: X segfaults and throws you back into gdm instead of restarting. And on the other hand, on my new box with ATI Radeon HD 5450 X doesn't crash and restart works. Created attachment 493100 [details]
Xorg log from T60 exhibiting the same symptom
Here's Xorg.0.log for the Intel-variant of the same syndrome. The log doesn't seem to get any meaningful symbol information despite installed -debuginfo's, so this is how it looks like from gdb (ran from another box over ssh):
Program received signal SIGSEGV, Segmentation fault.
uxa_prepare_access (pDrawable=0x0, access=UXA_ACCESS_RO) at uxa.c:145
145 ScreenPtr pScreen = pDrawable->pScreen;
(gdb) bt
#0 uxa_prepare_access (pDrawable=0x0, access=UXA_ACCESS_RO) at uxa.c:145
#1 0x00007f2369e723a8 in uxa_prepare_access_window (pWin=0xc333c0)
at uxa.c:290
#2 0x00007f2369e72431 in uxa_change_window_attributes (pWin=0xc333c0, mask=2)
at uxa.c:319
#3 0x00000000004a3ecf in compChangeWindowAttributes (pWin=0xc333c0, mask=2)
at compinit.c:116
#4 0x0000000000456866 in ChangeWindowAttributes (pWin=<optimized out>,
vmask=1, vlist=<optimized out>, client=0xe08f20) at window.c:1441
#5 0x0000000000429170 in ProcChangeWindowAttributes (client=0xe08f20)
at dispatch.c:692
#6 0x000000000042eb41 in Dispatch () at dispatch.c:431
#7 0x0000000000422dca in main (argc=<optimized out>, argv=0x7fff6d78ce68,
envp=<optimized out>) at main.c:287
The backtrace seems quite different so maybe this is a different bug, but given that both occur in the same exact way, and neither system exhibits any other X-related problems...
Might be: https://bugzilla.xfce.org/show_bug.cgi?id=7442 ? This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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 message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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 |