| Summary: | x11-base/xorg-server-1.5.3-r5 segfaults after some time | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Markus <M4rkusXXL> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | pk1 |
| Priority: | Highest | ||
| Version: | 2008.0 | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 251832 | ||
| Attachments: |
Xorg log file from crash
xorg.conf file that led to a crash |
||
|
Description
Markus
2009-04-15 11:13:33 UTC
What I figured out so far: It happens randomly but it can only take a few minutes. It happens when a window should open up. (It cant connect to the server as stated in the user xsession-errors and all other a killed because they lost the x-server.) "window should open up" is also the case for menues btw. Without doing anything, it runs without a problem for hours. (no failure at all) Another, though similar, backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4e7e16] 1: /usr/bin/X(xf86SigHandler+0x39) [0x493ef9] 2: /lib/libc.so.6 [0x7f030fa322b0] 3: /usr/bin/X(miHandleValidateExposures+0x6c) [0x4e049c] 4: /usr/bin/X(UnmapWindow+0x200) [0x4353d0] 5: /usr/bin/X(compFreeClientWindow+0x236) [0x4f8676] 6: /usr/bin/X [0x4f5bf9] 7: /usr/bin/X(FreeResource+0x133) [0x432e13] 8: /usr/bin/X(compUnredirectWindow+0x63) [0x4f8273] 9: /usr/bin/X [0x4f6636] 10: /usr/bin/X [0x4e0a3f] 11: /usr/bin/X [0x4e094c] 12: /usr/bin/X [0x4e094c] 13: /usr/bin/X(miChangeSaveUnder+0x50) [0x4e0ad0] 14: /usr/bin/X(MapWindow+0x317) [0x435a37] 15: /usr/bin/X(ProcMapWindow+0x46) [0x4490e6] 16: /usr/bin/X(Dispatch+0x364) [0x449914] 17: /usr/bin/X(main+0x445) [0x4305a5] 18: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f030fa1e486] 19: /usr/bin/X [0x42f9a9] Fatal server error: Caught signal 11. Server aborting The xorg-server should be masked untill this is resolved. It is definitly unusable! It may be something like bug 238634. Please attach a Xorg log file that explains what drivers are used. Also explain whether you did or did not rebuild x11-drivers/*. Then reopen this bug report. Also, it isn't critical or a blocker just because you happen to experience it. It seems there is a problem with nvidia. option "Backingstore" "false" is needed. Please see bugs: https://fcp.surfsite.org/modules/newbb/viewtopic.php?topic_id=65359&forum=12&post_id=311464 and http://bbs.archlinux.org/viewtopic.php?pid=463677 I am also having similar crashes. I can't produce them very reproducibly (they occur sporadically). I have noticed that trying to open openoffice makes them much more likely to occur (although I can open openoffice several times without it occurring). Here is my backtrace: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4e7e16] 1: /usr/bin/X(xf86SigHandler+0x39) [0x487c79] 2: /lib/libc.so.6 [0x34b4c311d0] 3: /usr/bin/X(XkbStringText+0x1c) [0x5642dc] 4: /usr/bin/X(XkbWriteXKBGeometry+0x17c) [0x55637c] 5: /usr/bin/X(XkbWriteXKBKeymapForNames+0x69b) [0x555a9b] 6: /usr/bin/X(XkbDDXLoadKeymapByNames+0x182) [0x55f522] 7: /usr/bin/X(ProcXkbGetKbdByName+0x36d) [0x53bffd] 8: /usr/bin/X(Dispatch+0x364) [0x449914] 9: /usr/bin/X(main+0x445) [0x4305a5] 10: /lib/libc.so.6(__libc_start_main+0xf4) [0x34b4c1e4a4] 11: /usr/bin/X [0x42f9a9] Notes: I do have an nvidia card, but did not have backstore enabled. I think this started when I moved to 1.5, but at one point I also updated my kernel and disabled acpi (this is not a laptop). I am on AMD64. I am attaching a full log of a crash (I plug/unplug my keyboard and mouse frequently which is the cause of the many messages about them coming back online) and my Xorg.conf. Created attachment 191702 [details]
Xorg log file from crash
Created attachment 191704 [details]
xorg.conf file that led to a crash
Also, I have emerge all my x11-drivers (x11-drivers/xf86-input-evdev-2.1.3 and x11-drivers/nvidia-drivers-180.29) since my last emerge of xorg-server (x11-base/xorg-server-1.5.3-r5). It does appear that multiple people are experiencing this bug so maybe it should be considered critical/blocking... it certainly outweighs any benefits from this upgrade. |