Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 837227

Summary: 6.3 regression in bnx2 driver when used in bond [rhel-6.3.z]
Product: Red Hat Enterprise Linux 6 Reporter: RHEL Program Management <pm-rhel>
Component: kernelAssignee: Frantisek Hrbata <fhrbata>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.3CC: agospoda, benjamin.parmentier, cww, dhoward, hartsjc, jentrena, kajtzu, kbooth, lzheng, mishu, ngupta, nhorman, nkim, pasteur, pep, pm-eus, rainer.traut, rdassen, redhat-bugzilla, rik.theys, sputhenp, stanislav.polasek, tbowling, tis, toracat, werner.maes
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-2.6.32-279.2.1.el6 Doc Type: Bug Fix
Doc Text:
The bonding method for adding VLAN Identifiers (VIDs) did not always add the VID to a slave VLAN group. When the NETIF_F_HW_VLAN_FILTER flag was not set on a slave, the bonding module could not add new VIDs to it. This could cause networking problems and the system to be unreachable even if NIC messages did not indicate any problems. This update changes the bond VID add path to always add a new VID to the slaves (if the VID does not exist). This ensures that networking problems no longer occur in this scenario.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-19 19:45:32 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: 834764    
Bug Blocks:    

Description RHEL Program Management 2012-07-03 08:59:00 UTC
This bug has been copied from bug #834764 and has been proposed
to be backported to 6.3 z-stream (EUS).

Comment 7 Eliska Slobodova 2012-07-17 14:20:43 UTC
    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:
The bonding method for adding VLAN Identifiers (VIDs) did not always add the VID to a slave VLAN group. When the NETIF_F_HW_VLAN_FILTER flag was not set on a slave, the bonding module could not add new VIDs to it. This could cause networking problems and the system to be unreachable even if NIC messages did not indicate any problems. This update changes the bond VID add path to always add a new VID to the slaves (if the VID does not exist). This ensures that networking problems no longer occur in this scenario.

Comment 9 Liang Zheng 2012-07-19 03:32:04 UTC
QE Note:
Regression test is done , all the test are PASS.
The NIC we have tested:
bnx2,igb.e1000e,cxgb4,be2net,bnx2x,ixgbe,bna,sfc
The test items :
1. Connection test (all 7 bond modes)
Beaker job link in Comment 6
2. Jambo Frame test (mtu 9000)
https://beaker.engineering.redhat.com/jobs/263095
3. tcp/udp/igmp/sctp (ipv4/ipv6) protocol test
In Comment 8 & https://beaker.engineering.redhat.com/jobs/262752
4. loop change active slave test (each slave)
change_active_slave task in https://beaker.engineering.redhat.com/jobs/262968
5. loop load/unload bonding and 8021q module test (100 times)
6. Bonding Tier1 Test (arp_monitor  bond_bridge_dhcp  bond_bridge_lro  bond_dhcp  module_load_unload)
https://beaker.engineering.redhat.com/jobs/262750

Ref : https://wiki.test.redhat.com/Kernel/Testplans/RHEL59bonding

Comment 10 Liang Zheng 2012-07-19 03:38:10 UTC
(In reply to comment #9)
> QE Note:
> Regression test is done , all the test are PASS.
> The NIC we have tested:
> bnx2,igb.e1000e,cxgb4,be2net,bnx2x,ixgbe,bna,sfc 
+ tg3
> The test items :
> 1. Connection test (all 7 bond modes)
> Beaker job link in Comment 6
> 2. Jambo Frame test (mtu 9000)
> https://beaker.engineering.redhat.com/jobs/263095
> 3. tcp/udp/igmp/sctp (ipv4/ipv6) protocol test
> In Comment 8 & https://beaker.engineering.redhat.com/jobs/262752
> 4. loop change active slave test (each slave)
> change_active_slave task in https://beaker.engineering.redhat.com/jobs/262968
> 5. loop load/unload bonding and 8021q module test (100 times)
> 6. Bonding Tier1 Test (arp_monitor  bond_bridge_dhcp  bond_bridge_lro 
> bond_dhcp  module_load_unload)
> https://beaker.engineering.redhat.com/jobs/262750
> 
> Ref : https://wiki.test.redhat.com/Kernel/Testplans/RHEL59bonding

Comment 12 errata-xmlrpc 2012-07-19 19:45:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-1104.html