Red Hat Bugzilla – Bug 198096
kernel 2.6.17-1.2145_FC5smp hangs my system
Last modified: 2008-08-02 19:40:33 EDT
Description of problem:
System hangs cold
Version-Release number of selected component (if applicable):
Every time I boot
Steps to Reproduce:
1. Download the 2.6.17-1.2145_FC5smp through the yum update facility
3. after about 1 minute of up time... Solid Hang...
2.6.16-1.2133_FC5smp works like a charm...
Check if this solves your problem:
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.
Thanks for looking into this bug. I know what the problem is. I have an ATI
graphics card (firegl x1). The issue has to do with an AGP bug in the kernel.
Some race condition or something like that. There is a patch for it which exists
in the 2.6.16 kernel, but it got removed in the 2.6.17 kernel. This issue is
still present in the FC6 release of kernels. (both the xen and non xen kernel.)
Installing the propriatary ATI display driver seems to fix the issue. Since then
I've moved on to an NVIDA card and using the nvidia propritary drivers.