Bug 534105

Summary:	EL4.8: igb driver fails to detect link status change on SERDES interface [rhel-4.8.z]
Product:	Red Hat Enterprise Linux 4	Reporter:	RHEL Program Management <pm-rhel>
Component:	kernel	Assignee:	Vitaly Mayatskikh <vmayatsk>
Status:	CLOSED ERRATA	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.8	CC:	agospoda, cward, dhoward, emcnabb, fleite, pm-eus, tao, vmayatsk
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	On certain hardware, the igb driver was unable to detect link statuses correctly. This may have caused problems for network bonding, such as failover not occurring.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-15 17:18:59 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:
Bug Depends On:	529037
Bug Blocks:

Description RHEL Program Management 2009-11-10 15:40:55 UTC

This bug has been copied from bug #529037 and has been proposed
to be backported to 4.8 z-stream (EUS).

Comment 3 Vitaly Mayatskikh 2009-11-12 15:00:27 UTC

Committed in 89.0.17

Comment 7 errata-xmlrpc 2009-12-15 17:18:59 UTC

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 therefore 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-2009-1671.html

Comment 9 Douglas Silas 2011-01-30 22:44:18 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
On certain hardware, the igb driver was unable to detect link statuses correctly. This may have caused problems for network bonding, such as failover not occurring.