Bug 158456 - Update Emulex driver in RHEL 3 U6
Update Emulex driver in RHEL 3 U6
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
3.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tom Coughlan
Brian Brock
: FutureFeature
Depends On:
Blocks: 156321
  Show dependency treegraph
 
Reported: 2005-05-22 10:17 EDT by Tom Coughlan
Modified: 2007-11-30 17:07 EST (History)
4 users (show)

See Also:
Fixed In Version: RHSA-2005-663
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-28 11:10:53 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 Tom Coughlan 2005-05-22 10:17:26 EDT
EMC and Emulex request that we update the driver to version 7.2.4. This update
contains bug fixes, support for oem'ed (renamed) adapters, and support for
Emulex's new 4Gbps FC adapters. This driver has completed QA at Emulex, and EMC
intends to have it on their support matrix in the U6 timeframe. 

It will require 16 hours to review, prepare, and test the patch. We have the
adapters needed to do basic regression testing. We have to rely on partners for
complex SAN testing. We will requre Emulex send us some of the 4Gbps adapters
for testing.
Comment 6 Ernie Petrides 2005-07-15 20:20:18 EDT
The Emulex driver update has just been committed to the RHEL3 U6
patch pool this evening (in kernel version 2.4.21-32.12.EL).
Comment 11 Red Hat Bugzilla 2005-09-28 11:10:54 EDT
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-2005-663.html

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