Red Hat Bugzilla – Bug 241498
x server/i810/i915 won't re-initialize
Last modified: 2018-04-11 02:49:09 EDT
Description of problem:
restarting the x server doesn't work, reboot is necessary
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. login into x session
3. x server crashes
x server crashes
x server restarts und display manager appears
Created attachment 155507 [details]
Created attachment 155508 [details]
dmesg at time of crash
Created attachment 155509 [details]
lsmod at time of crash
Created attachment 155510 [details]
Created attachment 155511 [details]
/var/log/messages at time of crash
Created attachment 155512 [details]
/proc/dri/*/* at time of crash
Created attachment 155513 [details]
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.
Hm, wonder if it's related to #241225. Does rhgb behave differently on intel
vs. other configurations I wonder?
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
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.
*** Bug 448340 has been marked as a duplicate of this bug. ***
*** Bug 454055 has been marked as a duplicate of this bug. ***
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.
same for Bug 454055, that is still present in F9 and F10....
am running now on fedore 9. the bug does not occur here afaict.