Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 565965

Summary:	[Broadcom 5.5 bug] tg3: Race condition - performance / panic with 57765 devices
Product:	Red Hat Enterprise Linux 5	Reporter:	Matt Carlson <mcarlson>
Component:	kernel	Assignee:	John Feeney <jfeeney>
Status:	CLOSED ERRATA	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.5	CC:	agospoda, andriusb, arindam.nath, benlu, bzeranski, cward, emcnabb, ericlrl, gloriach, henry.su, jfeeney, peterm, rdoty, shane.huang
Target Milestone:	rc	Keywords:	OtherQA
Target Release:	5.5
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-30 07:17:44 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:
Bug Blocks:	533941

Description Matt Carlson 2010-02-16 20:04:23 UTC

Description of problem:

There is a race condition between the driver and the bootcode on 57765 A0 devices.  The problem is that the bootcode will access and modify registers that are also used by the driver.  Register corruption is the consequence, which results in poor performance and possible kernel panics.

Commit ID 6b10c1653e425e30cff7f41d0e6f9743bfa9810f fixes the problem.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Andrius Benokraitis 2010-02-16 21:47:23 UTC

Matt, we are at the very end of the RHEL 5.5 development cycle - no guarantees on this making it.

Comment 2 Matt Carlson 2010-02-16 21:54:24 UTC

Understood.  At least the problem is documented and trackable.

Comment 4 John Feeney 2010-02-17 16:17:43 UTC

A rpm with this fix can be found on my people page. See
http://people.redhat.com/jfeeney/.rhel5-tg3
Testing feedback would be appreciated.

Comment 6 RHEL Program Management 2010-02-17 18:44:52 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 9 Jarod Wilson 2010-02-23 20:06:26 UTC

in kernel-2.6.18-190.el5
You can download this test kernel from http://people.redhat.com/jwilson/el5

Please update the appropriate value in the Verified field
(cf_verified) to indicate this fix has been successfully
verified. Include a comment with verification details.

Comment 12 Chris Ward 2010-03-05 12:15:54 UTC

@Matt, 

This issue should be resolved in A) the latest RHEL 5.5 snapshot B) with the test build available in comment #4. Please confirm as soon as possible that this issue is resolved as expected.

Comment 13 Ben 2010-03-05 12:59:23 UTC

We have verified the performance can reach ~1700Mbps bi-directional using netperf with test build in comment#26 of bug565964. And no panic occurred when in over-night stress.

Comment 15 errata-xmlrpc 2010-03-30 07:17:44 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-2010-0178.html

Comment 16 Red Hat Bugzilla 2023-09-14 01:20:15 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days