Bug 528482
Summary: | X freezes at startup or later on Intel hardware (82G33) - Fedora 11.91 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Patrick Proche <pproche> | ||||||
Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 12 | CC: | ajax, arya.subhransu, mcepl, xgl-maint | ||||||
Target Milestone: | --- | Keywords: | Triaged | ||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | card_G33 | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2010-12-04 07:29:59 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Patrick Proche
2009-10-12 13:16:23 UTC
Created attachment 364453 [details]
xorg-log
Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x49e758] 1: /usr/bin/X (0x400000+0x619a9) [0x4619a9] 2: /lib64/libpthread.so.0 (0x31a0e00000+0xf320) [0x31a0e0f320] 3: /usr/lib64/libdrm_intel.so.1 (0x7fa408f1b000+0x5ade) [0x7fa408f20ade] 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fa409138000+0x439db) [0x7fa40917b9db] 5: /usr/bin/X (0x400000+0x28d60) [0x428d60] 6: /usr/bin/X (0x400000+0x2c60c) [0x42c60c] 7: /usr/bin/X (0x400000+0x21c9a) [0x421c9a] 8: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x31a061eb4d] 9: /usr/bin/X (0x400000+0x21849) [0x421849] Segmentation fault at address 0x8 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting 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.] I made every update so far, the last today just before starting X (FVWM). After approx. 1 hour the system crashed again. Sorry, I have no log file of it. If it crashes again, I will send it. Despite of all the latest updates, FVWM froze again yesterday. I couldn't get a log file because I could not log in from outside. FVWM froze again several times during the last few days. I cannot get a Xorg log file because when FVWM freezes, the network connection seems to get lost, too. I cannot log in from outside with ssh anymore. I installed all available updates so far. 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 X froze again. I had a little script written which should copy the Xorg.0.log file in case X hangs. I semms that it did not work, so I cannot provide a log for the current crashes. FVWM just crashed again. It is not possible to save the Xorg.0.lof file after the crash anymore (login from outside not working, so I had a script running which copies the log file the /tmp every 3 seconds), so it is not only X/FVWM that crashes but the whole machine stops. Created attachment 374015 [details]
New X log file
I got this log file from the latest crash. Maybe you can read something out of it.
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 Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |