Here [1] is the dmesg output for the manual restart of networking (running "sudo /etc/init.d/networking restart").
Triggering the bonding driver to load earlier in boot did not fix things. I added "bonding" to /etc/modules, and restarted the system. Networking still failed to initialize correctly. The bonding-related dmesg output is listed below [2]. Regarding your second test, I'm not sure exactly what change to make to /etc/modprobe.d, if you let me know I can run that test too. Yes, testing with the backport Maverick kernel does fix the bonding issue. I'm not familiar enough with Ubuntu to know how to test the kernels you produced; you could let me know what commands to run to install the kernels? Also, just looking at the filenames, I'm not sure which ones to test against each other. Should each .deb file be applied and tested individually, or do certain ones need to be applied together? --------------------------------------------------- [1] [ 150.452703] bonding: bond0: doing slave updates when interface is down. [ 150.452706] bonding: bond0: Removing slave eth0 [ 150.452709] bonding: bond0: Warning: the permanent HWaddr of eth0 - f4:ce:46:af:58:40 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts. [ 150.452711] bonding: bond0: releasing active interface eth0 [ 150.452714] bonding: bond0: making interface eth1 the new active one. [ 150.607703] bonding: bond0: doing slave updates when interface is down. [ 150.607706] bonding: bond0: Removing slave eth1 [ 150.607708] bonding: bond0: releasing active interface eth1 [ 150.772167] bonding: bond0: doing slave updates when interface is down. [ 150.772170] bonding: bond0: Adding slave eth0. [ 150.772171] bonding bond0: master_dev is not up in bond_enslave [ 151.133971] bonding: bond0: making interface eth0 the new active one. [ 151.133976] bonding: bond0: first active interface up! [ 151.133983] bonding: bond0: enslaving eth0 as an active interface with an up link. [ 151.136220] bonding: bond0: doing slave updates when interface is down. [ 151.136223] bonding: bond0: Adding slave eth1. [ 151.136224] bonding bond0: master_dev is not up in bond_enslave [ 151.632833] bonding: bond0: enslaving eth1 as a backup interface with an up link. [ 151.633323] bonding: bond0: setting mode to active-backup (1). [ 151.633343] bonding: bond0: Setting MII monitoring interval to 100. [2] [ 6.149943] bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. [ 6.442893] bonding: bond0: doing slave updates when interface is down. [ 6.442896] bonding: bond0: Adding slave eth0. [ 6.442898] bonding bond0: master_dev is not up in bond_enslave [ 7.176017] bonding: bond0: enslaving eth0 as an active interface with an up link. [ 7.177578] bonding: bond0: doing slave updates when interface is down. [ 7.177581] bonding: bond0: Adding slave eth1. [ 7.177582] bonding bond0: master_dev is not up in bond_enslave [ 7.572679] bonding: bond0: enslaving eth1 as an active interface with an up link. [ 7.573204] bonding: bond0: setting mode to active-backup (1). [ 7.573222] bonding: bond0: Setting MII monitoring interval to 100. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688703 Title: [lucid] netxen_nic driver and ethernet bonding broken at boot time -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
