Bug 603936
Summary: | [Broadcom 6.0 bug] tg3: TX BD corruption can happen on all devices 5755 and newer | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Matt Carlson <mcarlson> |
Component: | kernel | Assignee: | John Feeney <jfeeney> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | CC: | andriusb, benlu, branto, gideonn, jfeeney, mchan |
Target Milestone: | rc | Keywords: | OtherQA, Regression |
Target Release: | 6.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-15 14:07:35 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: |
Description
Matt Carlson
2010-06-14 22:32:31 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Just for the record, the commit listed in the first comment has the following upstream description: tg3: Avoid tx lockups on 5755+ devices In certain edge conditions, internal tx resources can get corrupted. This patch enables a bit that will fix the problem. Verified that 5755/57765/5718 can pass stress test without exception. #comment4 tested on kernel-2.6.32-33.el6.with603936.603933.3 . Patch(es) available on kernel-2.6.32-42.el6 This bug can be hard to trigger. I think the best we can do is verify that the fix is applied correctly to the tg3 sources. I have verified that. Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |