Comment 0 for bug 482419

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.