Bug 249154

Summary:	Kernel regression that may be related to highpoint controllers
Product:	[Fedora] Fedora	Reporter:	Bruno Wolff III <bruno>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	7	CC:	alan, drew.middlesworth, seve141
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	2.6.22.1-41.fc7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-08-10 15:12:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bruno Wolff III 2007-07-21 15:31:23 UTC

Description of problem:
The latest kernel (kernel-2.6.22.1-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-2.6.22.1-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):
kernel-2.6.22.1-27.fc7

How reproducible:
100%

Steps to Reproduce:
1. reboot and select the 2.6.22.1-27.fc7 kernel to boot.
2.
3.
  
Actual results:
Boot fails after some raid device members aren't found and the root pivot fails.

Expected results:
Successful boot.

Additional info:
If you want lspci info and the like, you can get it from 227281.

Comment 1 Chuck Ebbert 2007-07-23 17:09:43 UTC

*** Bug 249166 has been marked as a duplicate of this bug. ***

Comment 2 Chuck Ebbert 2007-07-23 17:19:03 UTC

From Daniel Duggan's report (Bug 249166):

2.6.22:
hpt37x: DPLL did not stabilize.

2.6.21:
pata_hpt37x: BIOS has not set timing clocks.
hpt37x: HPT372: Bus clock 33MHz.

Bruno, does this match what happens on your systems?

Comment 4 Bruno Wolff III 2007-07-24 15:03:18 UTC

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.

Comment 5 Chuck Ebbert 2007-07-25 21:16:38 UTC

Patch in CVS.

Comment 6 Bruno Wolff III 2007-07-27 14:44:57 UTC

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.

Comment 7 Bruno Wolff III 2007-08-10 15:12:58 UTC

The 2.6.22.1-41.fc7 boots for me, so the fix appears to solve my problem.