Red Hat Bugzilla – Bug 207398
fc5 freezes randomly shortly after booting
Last modified: 2008-05-06 12:22:59 EDT
Description of problem:
After upgrading from fc4 to fc5 system would crash (freeze) randomly shortly
after booting, sometimes before the logon screen. This still happened after
applying all updates. Happens with any kernel version. My system has a
d865perl motherboard with an ati radeon 7000 video adapter. Interactive startup
with minimal daemons to start X does not help. What did help was commenting
out the DRI section in xorg.conf AND not using the smp kernel. Neither of these
alone helped the problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
I installed the new kernels (2.6.18-1.2200.fc5 and the smp version). The system
still crashes (freezes) with the smp kernel. I only tested it once this time -
it froze after it went into X but before the login screen came up. Previously
it would sometimes freeze here, sometimes a few minutes after logging in.
Previously it would also freeze booting with the regular kernel if the DRI
section was not commented out of /etc/X11/xorg.conf, but it now seems that the
regular kernel is okay even with this section in the xorg.conf file. I should
also test booting with an older regular kernel to check if something else has
occurred allowing it to run okay with the DRI section.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.