Red Hat Bugzilla – Bug 249154
Kernel regression that may be related to highpoint controllers
Last modified: 2007-11-30 17:12:10 EST
Description of problem:
The latest kernel (kernel-220.127.116.11-27.fc7) will no longer complete booting. I
get a message that no devices were found for a couple of raid devices (root and
swap) and this causes the root pivot fail and the kernel panics shortly afterward.
This is similar to problems I was experiencing during f7 rawhide testing as
documented in bug 227281. The previous kernel (kernel-2.6.21-1.3228.fc7) works
just fine on this system.
I have kernel-18.104.22.168-27.fc7 installed on another machine with software raid
devices and I didn't have a problem there when rebooting after the kernel upgrade.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. reboot and select the 22.214.171.124-27.fc7 kernel to boot.
Boot fails after some raid device members aren't found and the root pivot fails.
If you want lspci info and the like, you can get it from 227281.
*** Bug 249166 has been marked as a duplicate of this bug. ***
From Daniel Duggan's report (Bug 249166):
hpt37x: DPLL did not stabilize.
pata_hpt37x: BIOS has not set timing clocks.
hpt37x: HPT372: Bus clock 33MHz.
Bruno, does this match what happens on your systems?
No it doesn't. Under 2.6.22 I seem the same message. (It isn't in my logs, but
the messages paused long enough that I am pretty sure it was the same message.
Under 2.6.21 I get:
Jul 24 09:55:30 bruno kernel: pata_hpt37x: BIOS has not set timing clocks.
Jul 24 09:55:30 bruno kernel: hpt37x: HPT302: Bus clock 33MHz.
Patch in CVS.
Unless a test kernel rpm shows up this afternoon, I won't get to test the fix
until I get back from vacation. (Even it is does, I still might not have time
before I leave.) So if you ask me to do a test, don't be surprised if I don't
provide any feedback until about the 9th or 10th of August.
The 126.96.36.199-41.fc7 boots for me, so the fix appears to solve my problem.