Description of problem: Configured bonding (balance-xor) with 3 nics (tg3 driver). When the bonding driver loads at boot a recursive locking is detected. The messages are attached to this issue. line from modprobe.conf for this options bond0 mode=balance-xor miimon=100 use_carrier=1 Version-Release number of selected component (if applicable): 2.6.17-1.2600-smp How reproducible: Only in the smp kernel Steps to Reproduce: 1. configure bonding balance-xor 2. reboot the machine 3. The output of dmesg will have this. The server is PowerEdge 6800 with 2 procs one 5701 adapter and two 5704 LOM. All nics are broadcom Actual results: when the bonding driver loads the kernel outputs possible recursive locking detected and bonding drivers also report duplicate MAC address. Expected results: There should be no recursive locking. Additional info: This does not happen with the xen kernel, but another problem that occurs is that, in the same configuration the nics are enumarated as eth1 eth2 and eth3. eth0 seems to be already used by another device. mii-tool eth0 reports "SIOCGMIIPHY on 'eth0' failed: Operation not supported"
Reassigning to correct owner, kernel-maint.
This bug is on Dell's weekly watch list. Please assign to developer to investigate. Thanks.
Created attachment 136568 [details] backtrace and dmesg output. This is the output of dmesg and also the back trace of the issue.
Created attachment 136570 [details] backtrace and dmesg output. This is the output of dmesg and also the back trace of the issue.
I'm seeing a recursive locking message with a bonded interface as well. One of the two NICs is tg3, the other is ns83820 (both GbE), but the bonding mode is active-backup.
Okay, this doesn't appear to be specific to the NIC driver. I'm getting the same thing with dual 3c59x cards.
This was posted against fc6. Changed to RHEL5 beta per sly. This is a BUG.
in kernel-2.6.18-1.2707.el5.bz208456
FC6 test kernels available here: http://people.redhat.com/linville/kernels/fc6/ Please try to replicate the issue with those kernels, and post the results here...thanks!
(In reply to comment #11) > FC6 test kernels available here: > > http://people.redhat.com/linville/kernels/fc6/ > > Please try to replicate the issue with those kernels, and post the results > here...thanks! I see no more lockdep spew with 2.6.18-1.2708.2.1.fc6.jwltest.9.i686.
Sandeep- Please try and regress with the people page kernel (see comment #11) and report results here so we can call this issue RIP!
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering. This request is not yet committed for inclusion in release.
QE ack for RHEL5B2.
(In reply to comment #11) > FC6 test kernels available here: > > http://people.redhat.com/linville/kernels/fc6/ > > Please try to replicate the issue with those kernels, and post the results > here...thanks! I did a test and found that this issue does not occur on kernel-2.6.18-1.2702 weekly RHEL 5 build 18th sept.
Fix verified. Please close. Thanks!