that debug output looks the same, so i'd say yes. 2010/1/26 Scott Call <[email protected]>: > Is this possible same/related as Debian bug 588097 related to ifenslave-2.6? > http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/9f05eea3b27339a6 > > -- > 802.3ad interface bonding fails if started too early > https://bugs.launchpad.net/bugs/482419 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” package in Ubuntu: Confirmed > > Bug description: > 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 > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482419/+subscribe >
-- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
