[Bug 482419] Re: 802.3ad interface bonding fails if started too early

Martin Pitt martin.pitt at ubuntu.com
Sun Oct 10 09:27:13 BST 2010


Bhavani,

this patch looks a bit weird. It not just changes the order of the
function calls, it also introduces a new function call "setup_slaves",
without any further changes. However, in the original Debian patch
(still visible at
http://launchpadlibrarian.net/49642996/ifenslave-2.6_1.1.0-14ubuntu2_1.1.0-15ubuntu1.diff.gz)
that new function is introduced (by splitting the original one). So can
you please confirm that our version already has the new function, but
not the call to it?

-- 
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “ifenslave-2.6” package in Ubuntu: Fix Released
Status in “ifenslave-2.6” source package in Lucid: Triaged
Status in “ifenslave-2.6” package in Debian: Unknown

Bug description:
Impact: see original report below
How the patch fixes it: pre-up sets up master before attempting to enslave and setup slaves
Patch: https://bugs.edge.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/482419/+attachment/1455658/+files/ifenslave-2.6-sru.diff
Reproducing: http://ubuntuforums.org/showpost.php?p=8285696&postcount=3
Regression potential: none known

== Original report ==
802.3ad bonding configurations that formerly worked on jaunty are now failing on startup under karmic. After the system has started, restarting networking will bring the bond up correctly. This only applies to bond_mode 4 / 802.3ad, I've tested that switching to bond_mode 0 corrects the issue, and other users experiencing this bug all were using bond_mode 4 as well.

dmesg output fills with "bonding: bond0: Warning: Found an uninitialized port", even after the system starts up and the port should be "initialized"

It appears to occur on multiple drivers (bnx2, e1000 confirmed).

One initially wants to blame the startup ordering due to the switch to upstart, but I believe it is an edge case that hasn't been seen before because we haven't been starting up so quickly that the hardware hasn't had time to fully initialized.

Configuration and output from multiple users is in this thread:
http://ubuntuforums.org/showthread.php?p=8311572







More information about the Ubuntu-sponsors mailing list