Bug 128015 - RHEL3 U4: SATA AHCI (ICH6)
RHEL3 U4: SATA AHCI (ICH6)
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
3.0
All Linux
high Severity medium
: ---
: ---
Assigned To: dff
IT_43786
Kernel
:
Depends On:
Blocks: 168424
  Show dependency treegraph
 
Reported: 2004-07-16 08:59 EDT by Larry Troan
Modified: 2016-04-18 05:45 EDT (History)
4 users (show)

See Also:
Fixed In Version: RHSA-2006-0144
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-03-15 10:36:50 EST
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 Larry Troan 2004-07-16 08:59:15 EDT
SATA drives with AHCI should be coming into wider use in this timeframe.  Have
seen that "Preliminary driver with full AHCI support now exists, and is being
integrated into libata mainline.[JG]".

(Is this feature not available with ICH5?)
----------
Action by: Daryl
Issue Registered
----------
Action by: cww


ltroan assigned to issue for HP-WS.

Category set to: Applications
Status set to: Waiting on Tech
Comment 3 Susan Denham 2004-08-23 16:54:08 EDT
Closing this as a DUP of 112066.  I'll capture the HP comments.

*** This bug has been marked as a duplicate of 112066 ***
Comment 4 Ernie Petrides 2005-12-01 20:39:45 EST
The SATA update that resolves this has just been committed to the
RHEL3 U7 patch pool this evening (in kernel version 2.4.21-38.EL).
Comment 5 Red Hat Bugzilla 2006-03-15 10:36:50 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2006-0144.html

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