Red Hat Bugzilla – Bug 557122
No output of xmit_hash_policy on IEEE 802.3ad Bonding
Last modified: 2014-06-29 19:01:50 EDT
Description of problem: Couldn't able to lookup the xmit_hash_policy option setup on IEEE 802.3ad Bonding on sysfs or proc. No dmesg information found. Version-Release number of selected component (if applicable): kernel-2.6.9-78.EL iputils-20020927-21.el4 Ethernet Channel Bonding Driver, v2.6.3-rh How reproducible: bonding Mode 4(IEEE 802.3ad) with xmit_hash_policy layer(layer 3+4) option Actual results: Ethernet Channel Bonding Driver: v2.6.3-rh (June 8, 2005) Bonding Mode: IEEE 802.3ad Dynamic link aggregation MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: slow Active Aggregator Info: Aggregator ID: 2 Number of ports: 2 Actor Key: 17 Partner Key: 36005 Partner Mac Address: 00:23:04:ee:bf:5e Slave Interface: eth0 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:25:b3:e0:b4:58 Aggregator ID: 2 Slave Interface: eth1 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:25:b3:e0:b4:5a Aggregator ID: 2 Expected results: Need to know xmit_hash_policy Additional info:
Created attachment 385692 [details] rhel4-bonding-hashtype-display.patch I have compile tested this patch and I think it is a reasonable option for RHEL4. I will probably not push this upstream as upstream has sysfs to export this. Generally it would not be a good idea to increase the output of a /proc file since people do not like them anyway and feel this information should be in debugfs.
Andy, I'm very new to this linux internals. I would appreciate if you could explain me more on this issue. Are you going to release a patch with update 9 for RHEL 4 or this would be temporary fix patch.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Naveen, what normally happens is that we get customers to test a fix and then include the fix in our next update if all is working well. Our next update for RHEL4 will RHEL4.9 (current version is RHEL4.8), but there are not plans to release that for quite some time (I am not sure when exactly). We always make the patches available, so those you want to use them on the older code can build their own kernels, but if a support problem arises, they will have to verify there is a problem on a kernel shipped by Red Hat as well before we can help. Feel free to ask more questions if you have them.
Created attachment 405651 [details] bonding-xmit-hash-print.patch Apparently I didn't look hard enough because this fix was already upstream. Attached is a backport of that patch. Testing is greatly appreciated.
Committed in 89.34.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
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-2011-0263.html