Bug 154140 - RHEL3 U5: On ICH7 system install in IDE mode changed to AHCI mode causes a Kernel Panic
RHEL3 U5: On ICH7 system install in IDE mode changed to AHCI mode causes a Ke...
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
3.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jeff Garzik
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-07 14:52 EDT by Ed Ciechanowski
Modified: 2013-07-02 22:24 EDT (History)
5 users (show)

See Also:
Fixed In Version: U5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-29 12:51:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ed Ciechanowski 2005-04-07 14:52:22 EDT
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 14:53:42 EDT
Issue tracker 70145
Comment 2 Ed Ciechanowski 2005-08-29 12:51:50 EDT
This has been fixed and IT Closed on 5/2/2005. Closing this bug.
Comment 3 Ernie Petrides 2005-08-29 16:00:09 EDT
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 16:12:43 EDT
Above comment should read "there doesn't seem to be ...".
Comment 5 Ed Ciechanowski 2005-08-30 11:51:41 EDT
Agreed.
Thanks for straightening this out.
*EDC*

Note You need to log in before you can comment on or make changes to this bug.