1. Feature Overview: a. Update bnx2 to 2.0.x version b. Feature Description General bug fixes and feature enhancements. Newer iSCSI firmware. 2. Feature Details: a. Architectures: 32-bit x86 64-bit Intel EM64T/AMD64 64-bit Itanium2 b. Upstream acceptance information: 2.0.1 is upstream, patch submission will be ongoing. 3. Business Justification: a. Why is this feature needed? General driver update, bug fixes, etc. 4. Primary contact at Broadcom, email, phone mchan (949)926-6170
Michael - unlinking the two BZs - not sure if you did that just to save time or if they were really dependent on each other. I'm going to assume the former. This won't change the intent of the bugzilla proposed for 5.5, just FYI.
*** Bug 511974 has been marked as a duplicate of this bug. ***
*** Bug 513938 has been marked as a duplicate of this bug. ***
*** Bug 511976 has been marked as a duplicate of this bug. ***
We need to make sure this commit is included in the list of commits added for 5.5. commit 61d9e3fa7eacabfb7879e3da91709f1a5420c507 Author: Michael Chan <mchan> Date: Fri Aug 21 16:20:46 2009 +0000 bnx2: Apply BROKEN_STATS workaround to 5706 and 5708. Add flag to expand the workaround to both chips.
The fix for bz527748 was posted to rhkernel-list by Flavio Leitner today to fix problem documented by comment #6. Thanks, Andy.
@Broadcom, We need to confirm that there is commitment to test for the resolution of this request during the RHEL 5.5 test phase, if it is accepted into the release. Please post a confirmation before Oct 16th, 2009, including the contact information for testing engineers.
Yes, adding QA manager Nasser and test engineer Joe to CC.
------- Comment From lcm.com 2009-10-13 14:44 EDT------- IBM will also provide test feedback. Please coordinate through Peter Bogdanovic, pbogdano.
PQA Test Engineers are as follows: bnx2x - Tung Nguyen (tungn) bnx2 - Joe Torricelli (jtorrice) tg3 - Jeff Leu (jleu) bnx2i - Emory Bestenlehner (emoryb) BRCM will also provide periodic test results. Any questions/comments, please let me know. Thanks Ed Narvaez, enarvaez, 949-926-6456
This enhancement request was evaluated by the full Red Hat Enterprise Linux team for inclusion in a Red Hat Enterprise Linux minor release. As a result of this evaluation, Red Hat has tentatively approved inclusion of this feature in the next Red Hat Enterprise Linux Update minor release. While it is a goal to include this enhancement in the next minor release of Red Hat Enterprise Linux, the enhancement is not yet committed for inclusion in the next minor release pending the next phase of actual code integration and successful Red Hat and partner testing.
Kernel RPMs with the proposed patch to upgrade to version 2.0.2 can be found at: http://people.redhat.com/jfeeney/.rhel5-bnx2 Any testing feedback would be appreciated. This kernel includes the following upstream patches: Yang Hongyang - 4/7/2009 replace all DMA_64BIT_MASK macro w/DMA_BIT_MASK(64) 6a35528a8346f6e6fd32ed7e51f04d1fa4ca2c01 Yang Hongyang - 4/7/2009 replace all DMA_40BIT_MASK macro w/DMA_BIT_MASK(40) 50cf156af7dc68a44409bef636585ef88ebbab34 Yang Hongyang - 4/7/2009 replace all DMA_32BIT_MASK macro w/DMA_BIT_MASK(32) 284901a90a9e0b812ca3f5f852cbbfb60d10249d Michael Chan - 5/6/2009 Fix panic in bnx2_poll_work() 581daf7e00c5e766f26aff80a61a860a17b0d75a Eric Dumazet - 5/12/2009 bnx2_tx_int() optimizations d62fda082c48b417b47a553860abf75d9cf8b591 Breno Leitao - 6/8/2009 no need to check before vfreeing 25b0b999fbf5cc1893b110d530102951795d2f73 Ooiwa Naohiro - 6/24/2009 Fix the behavior of ethtool when ONBOOT=no 7959ea254ed18faee41160b1c50b3c9664735967 Dean Nelson - 7/31/2009 return PCI_ERS_RESULT_DISCONNECT on permanent failure 2ec3de26d2dc666159b79a8b9394fa00b6f414ae Michael Chan - 8/14/2009 Use mutex on slow patch cnic calls c5a889508203446c1abc1d670599b3a816841813 Michael Chan - 8/21/2009 Zero out status block before chip reset. 155d5561f570c5b3af7a178670061927d89209fb Michael Chan - 8/21/2009 Check if_running() before touching chip registers. 3767546cc24de8f104e745d59a0a43a09d9267df Michael Chan - 8/21/2009 Close device if MTU change or ring size change fails. 6fefb65e78f098c09d0ab877b2c70421e4c84116 Michael Chan - 8/21/2009 Report FTQ discard counter. 790dab2f671cb477e6179322a6c48c898e311e72 Michael Chan - 8/21/2009 Refine coalescing parameters. cf7474a6f4eda22603591b7d6253dffc224e4784 Michael Chan - 8/21/2009 Use const on flash_table structure. 0ced9d01d19795f913b95cebedd7d03986671379 Michael Chan - 8/21/2009 Update version to 2.0.2 8fea0f0db87a4aaed41a93eed147af61cc5f9e3f
*** Bug 513417 has been marked as a duplicate of this bug. ***
Will begin evaluating 2.0.2 shortly.
Created attachment 375606 [details] strace of 'ifconfig ethx mtu 9000'
Changing mtu causes ifconfig to hang. ie: ifconfig eth2 mtu 9000 Strace attached 'strace_ifconfig_mtu_change.txt'
I changed the MTU on a system with a BCM5709 and did not have trouble. I changed it a couple of times, with a load and without and did not hang ifconfig. What NIC are you using? Does it happen all the time? What else is going on?....
>What NIC are you using? 5709 Copper b/c 5.2.2 (unreleased boot code) Does it happen all the time? Yes >What else is going on?.... Will try different boot codes to see if they make a difference. Used kernels from: "http://people.redhat.com/jfeeney/.rhel5-bnx2", is there a newer release?
> >What else is going on?.... > Will try different boot codes to see if they make a difference. Regressed to two previous gold boot code versions 4.6.4 and 5.0.11. Both exhibited the same issue as 5.2.2. Running the 2.6.18-169.el5.test x86_64 kernel installed on a RHEL 5.4 gold install.
I assume there is no problem with any of these boot codes with the stock 5.4 gold driver. No, there is no newer version at this time, in answer to comment #19 question.
JF>I assume there is no problem with any of these boot codes with the stock 5.4 gold driver. Correct, no issues seen with stock 5.4 Gold Kernel and in-box driver.
John, can you provide kernel src rpm so we can debug this issue here as well? Thanks.
Michael, My apologies. See http://people.redhat.com/jfeeney/.rhel5-bnx2 for src rpm.
in kernel-2.6.18-181.el5 You can download this test kernel from http://people.redhat.com/dzickus/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.
Verified issue no longer present w/ kernel-2.6.18-181.el5 x86-64
Tests that have been run/passed: -IPv6 -Driver Load/Unload w/ Stress -Ethtool test stress test -Jumbo Frames -Reboot stress.
Update to #30 Tests that have been ran/passed: -Chariot Stress (72 hours) - Driver Load/Unload w/ Stress and NCSI enabled
*** Bug 516977 has been marked as a duplicate of this bug. ***
In terms of test progress, BRCM PQA is planning on running first pass testing and regression tests by Beta snapshots. Current bnx2 first pass L2 testing (not including iSCSI offload) is at 75% complete.
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: = Broadcom NetXtreme II network devices = The bnx2 driver for Broadcom NetXtreme II network devices has been updated to version 2.0.2 (BZ#517377)
Test progress update, BRCM PQA current bnx2 first pass L2 testing (not including iSCSI offload) is at 100% complete.
------- Comment From coschult.com 2010-02-17 16:50 EDT------- Verified Beta 1 using Broadcom 5708 and Broadcom 5709 adapters. Driver present after booting and card detected. Tested using netperf (np3d test suite) on local network. All tests passed.
I have tested bnx2 2.0.2 as provided in kernel 2.6.18-186.el5 x86_64 on a variety of Broadcom 5708/5709 based network adapters. I have not encountered any problems.
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