Bug 507293

Summary: [Broadcom 5.3.z FEAT] Update bnx2 to 1.8.2b+
Product: Red Hat Enterprise Linux 5 Reporter: RHEL Program Management <pm-rhel>
Component: kernelAssignee: Ivan Vecera <ivecera>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.4CC: agospoda, andriusb, benlu, bshepher, bugproxy, bzeranski, charles_rose, dhoward, dzickus, enarvaez, ivecera, james.brown, james.leddy, jcm, jfeeney, jjarvis, jlarrew, jpirko, jtorrice, karen.skweres, martinez, niran, pm-eus, qcai, rpacheco, sandy.garza, syeghiay, tao
Target Milestone: rcKeywords: FutureFeature, OtherQA, Reopened, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-18 14:14:40 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: 475567    
Bug Blocks:    
Attachments:
Description Flags
Proposed patch none

Description RHEL Program Management 2009-06-22 08:25:46 UTC
This bug has been copied from bug #475567 and has been proposed
to be backported to 5.3 z-stream (EUS).

Comment 4 Jiri Skrabal 2009-06-24 12:34:32 UTC
Closing based on following statement:
>>> Ok, keep in mind there was some history on this.  The reason this
>>> originally had the 5.3.z flag is because that's what a prod support
>>> customer wanted, however Andy said no, so we went with the hotfix
>>> packages on it.  The 5.3.z flag was never removed and then someone
>>> asked again if we were going to do it and Andy said, only if you
>>> isolate a smaller set of patches for 5.3.z.  So, Flavio did that (I
>>> think ... some confusion here) and the latest plan was to push those
>>> into the next 5.3.z.  The original requestees have gone away, which
>>> made your customer the biggest driving factor behind this request.
>>> All that aside, do you think we should drop this request and do a
>>> kbase article instead (indicating that TSO needs disabled)?

Jiri

Comment 5 Jiri Skrabal 2009-06-24 16:17:57 UTC
*** Bug 502196 has been marked as a duplicate of this bug. ***

Comment 10 Ivan Vecera 2009-07-02 16:20:58 UTC
Created attachment 350311 [details]
Proposed patch

Proposed patch for RHEL 5.3.z

Comment 11 Ivan Vecera 2009-07-02 16:26:22 UTC
Testing kernel builds are available at:
http://people.redhat.com/ivecera/rhel-5z-ivtest/

Comment 13 Ivan Vecera 2009-07-10 12:15:38 UTC
I tried my testing kernel and issue seems to be solved.
Joe, could you confirm this also?

Comment 14 Joe T 2009-07-10 17:50:27 UTC
Ivan:
Sorry, yes, haven't seen any issues w/ this kernel. We ran 72+ hours of traffic "stress" and no issues were seen.