Bug 504307 - openchrome wedges entire server
Summary: openchrome wedges entire server
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-openchrome
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Xavier Bachelot
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 504300
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-05 14:08 UTC by Jonathan Kamens
Modified: 2018-04-11 07:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 12:48:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
log file from the X session that crashed right before the one that hung the system (54.62 KB, text/plain)
2009-06-05 14:08 UTC, Jonathan Kamens
no flags Details
log file from the X session that hung the system (46.42 KB, text/plain)
2009-06-05 14:09 UTC, Jonathan Kamens
no flags Details
xorg.conf file (generated by X server) (3.34 KB, text/plain)
2009-06-05 14:09 UTC, Jonathan Kamens
no flags Details

Description Jonathan Kamens 2009-06-05 14:08:41 UTC
Created attachment 346659 [details]
log file from the X session that crashed right before the one that hung the system

Bug 504300 describes how to crash the X server.  If I do this a couple times in a row while using the openchrome driver (sometimes the problem happens after the first crash, sometimes it takes a few crashes), the X server fails to come back up -- the screen stays black while it's supposed to be starting -- and then the entire system hangs -- it stops pinging and requires a hard reset.

I've attached two Xorg.0.log files -- the one from the X session right before the system hang, and the one from the system hang, which shows where the X server is getting wedged.  It also shows that it tried to run on a different VT, which makes me suspect that perhaps the old, crashed X server didn't realize all its resources properly and that's why the new one is getting hosed.

Comment 1 Jonathan Kamens 2009-06-05 14:09:21 UTC
Created attachment 346660 [details]
log file from the X session that hung the system

Comment 2 Jonathan Kamens 2009-06-05 14:09:57 UTC
Created attachment 346661 [details]
xorg.conf file (generated by X server)

Comment 3 Bug Zapper 2009-06-09 17:09:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Matěj Cepl 2009-11-05 18:30:44 UTC
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. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

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.]

Comment 5 Jonathan Kamens 2009-11-12 23:14:37 UTC
I can't tell if this issue is resolved, since I do not currently have a good way to crash the openchrome server, which is when it manifests.  I've tried killing the X server repeatedly, with and without -9, and I can't reproduce this issue by doing that.  Perhaps that means the bug is fixed.

Comment 6 Bug Zapper 2010-04-27 14:39:49 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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

Comment 7 Bug Zapper 2010-06-28 12:48:51 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.


Note You need to log in before you can comment on or make changes to this bug.