Bug 241498

Summary: x server/i810/i915 won't re-initialize
Product: [Fedora] Fedora Reporter: jan p. springer <jsd>
Component: xorg-x11-drv-i810Assignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact:
Severity: urgent Docs Contact:
Priority: medium    
Version: 7CC: antonio.montagnani, bjorn, jbarnes, mcepl, orchard, triage, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-17 01:19:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
dmesg at time of crash
lsmod at time of crash
lspci -vv
/var/log/messages at time of crash
/proc/dri/*/* at time of crash
/proc/mtrr none

Description jan p. springer 2007-05-26 20:02:35 UTC
Description of problem:

restarting the x server doesn't work, reboot is necessary

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. login into x session
2. logout
3. x server crashes
Actual results:

x server crashes

Expected results:

x server restarts und display manager appears

Additional info:

Comment 1 jan p. springer 2007-05-26 20:03:37 UTC
Created attachment 155507 [details]

Comment 2 jan p. springer 2007-05-26 20:04:21 UTC
Created attachment 155508 [details]
dmesg at time of crash

Comment 3 jan p. springer 2007-05-26 20:04:43 UTC
Created attachment 155509 [details]
lsmod at time of crash

Comment 4 jan p. springer 2007-05-26 20:05:03 UTC
Created attachment 155510 [details]
lspci -vv

Comment 5 jan p. springer 2007-05-26 20:12:18 UTC
Created attachment 155511 [details]
/var/log/messages at time of crash

Comment 6 jan p. springer 2007-05-26 20:13:43 UTC
Created attachment 155512 [details]
/proc/dri/*/* at time of crash

Comment 7 jan p. springer 2007-05-26 20:14:11 UTC
Created attachment 155513 [details]

Comment 8 jan p. springer 2007-06-03 22:28:17 UTC
upgraded to fedora 7. when rhgb is active the xserver will still crash after the
first user session. when booting without rhgb everything works fine, so far.

Comment 9 Jesse Barnes 2008-01-10 22:39:24 UTC
Hm, wonder if it's related to #241225.  Does rhgb behave differently on intel 
vs. other configurations I wonder?

Comment 10 Bug Zapper 2008-05-14 12:14:56 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.

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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Bug Zapper 2008-06-17 01:19:48 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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.

Comment 12 Matěj Cepl 2008-09-09 20:56:39 UTC
*** Bug 448340 has been marked as a duplicate of this bug. ***

Comment 13 Matěj Cepl 2008-09-09 20:57:18 UTC
*** Bug 454055 has been marked as a duplicate of this bug. ***

Comment 14 Björn Persson 2008-09-09 22:24:14 UTC
If bug 448340 is a duplicate of this one then this bug is still present in Fedora 9 and should not have been closed when Fedora 7 was EOLd. Somebody please reopen this bug against Fedora 9. It seems I'm not allowed to do it.

Comment 15 antonio montagnani 2008-09-10 05:50:46 UTC
same for Bug 454055, that is still present in F9 and F10....

Comment 16 jan p. springer 2008-09-10 07:26:37 UTC
am running now on fedore 9. the bug does not occur here afaict.