Bug 154140

Summary:	RHEL3 U5: On ICH7 system install in IDE mode changed to AHCI mode causes a Kernel Panic
Product:	Red Hat Enterprise Linux 3	Reporter:	Ed Ciechanowski <ed.ciechanowski>
Component:	kernel	Assignee:	Jeff Garzik <jgarzik>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.0	CC:	jbaron, linville, peterm, petrides, riel
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:	U5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-08-29 16:51:50 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 Ed Ciechanowski 2005-04-07 18:52:22 UTC

Description of problem:
After installing RHEL3 U5 Beta release to a SATA drive with BIOS set to IDE. 
If you change the BIOS from IDE to AHCI mode, after reboot will cause a Kernel 
Panic. 

Version-Release number of selected component (if applicable):
2.4.21-31.EL

How reproducible:
Install RHEL3 U5 on an ICH7 system to an SATA drive with BIOS set to IDE mode. 
The installation will work correctly and you are able to login. Now reboot the 
system, enter the BIOS setup and change the SATA drive's mode from IDE mode to 
AHCI mode. When you save the setting and reboot you will get a Kernel Panic. 

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Kernel Panic when BIOS set to AHCI mode if it was installed in IDE mode. 

Expected results:
The OS should boot no matter what the BIOS is set to and the OS should load 
the correct driver.

Additional info:

Comment 1 Ed Ciechanowski 2005-04-07 18:53:42 UTC

Issue tracker 70145

Comment 2 Ed Ciechanowski 2005-08-29 16:51:50 UTC

This has been fixed and IT Closed on 5/2/2005. Closing this bug.

Comment 3 Ernie Petrides 2005-08-29 20:00:09 UTC

Hello, Ed.  According to a comment in IT 70145 dated 04-15-2005, this
bug reported a situation that is expected behavior.  Specifically,
there doesn't since to be any post-2.4.21-31.EL fix that went into U5
that could have addressed this.

Thus, I'm changing the disposition of this bug to CLOSED/WONTFIX.

Comment 4 Ernie Petrides 2005-08-29 20:12:43 UTC

Above comment should read "there doesn't seem to be ...".

Comment 5 Ed Ciechanowski 2005-08-30 15:51:41 UTC

Agreed.
Thanks for straightening this out.
*EDC*