Red Hat Bugzilla – Bug 555671
MRG -146/-147 kernels have older broadcom drivers compared with RHEL5.4
Last modified: 2016-05-22 19:29:49 EDT
John G. Stultz <firstname.lastname@example.org> -
Rob Russell noted: "The Broadcom network driver (bnx2) in the current MRG is v1.7.8 from july 10,
2008. RHEL 5.4 base has bnx2 driver v1.9.3 from March 17, 2009."
Apparently some of the changes added between RHEL5.3 and 5.4 are important to the driver functioning
properly on new hardware.
Some of the changes are documented in the following RH bugs:
Would it be possible to update the MRG kernel to more recent bnx2 driver level?
Patch bz555671-update_bnx2_driver_to_2.0.8.patch, update to driver version 2.0.8 + fixes compiled by Arnaldo, has been added to kernel-rt 220.127.116.11-153
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.
Updated the Broadcom bnx2 driver to version 2.0.8 to enable new hardware
Verified by code review. Found bz555671-update_bnx2_driver_to_2.0.8.patch implemented in kernel-rt-18.104.22.168-160.src.rpm.
[root@dell-pet110-01 ~]# modinfo bnx2
description: Broadcom NetXtreme II BCM5706/5708/5709/5716 Driver
author: Michael Chan <email@example.com>
vermagic: 22.214.171.124-160.el5rt SMP preempt mod_unload 686 4KSTACKS
Version info from patch:
-#define DRV_MODULE_VERSION "1.7.8"
-#define DRV_MODULE_RELDATE "July 10, 2008"
+#define DRV_MODULE_VERSION "2.0.8"
+#define DRV_MODULE_RELDATE "Feb 15, 2010"
dmesg from booting -160:
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.8 (Feb 15, 2010)
Ran nfs and cifs connectathon tests and kernel/networking/nic/stress tests against boxes with bnx2x and igb cards without any issues. General networking tested, dhcp, ssh, wget/curl, ping. Over 20GB of data have been pushed over the interface.
------- Comment From firstname.lastname@example.org 2010-07-27 22:34 EDT-------
I think we can mark this accepted.
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.