Bug#558097: ifenslave-2.6: bond interface is not starting during system startup
Łukasz Piątkowski
Version: 1.1.0-14
Severity: important
When the system is tarted, my bond interface is not started and it writes syslog like this:
Nov 25 18:23:14 typhoon kernel: [ 660.204167] Ethernet Channel Bonding Driver: v3.2.5 (March 21, 2008)
Nov 25 18:23:14 typhoon kernel: [ 660.218272] 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.
Nov 25 18:23:14 typhoon kernel: [ 660.325208] bonding: bond0: doing slave updates when interface is down.
Nov 25 18:23:14 typhoon kernel: [ 660.339231] bonding: bond0: Adding slave eth0.
Nov 25 18:23:14 typhoon kernel: [ 660.355223] bonding bond0: master_dev is not up in bond_enslave
Nov 25 18:23:14 typhoon kernel: [ 660.467269] bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Nov 25 18:23:14 typhoon kernel: [ 660.494099] bonding: bond0: enslaving eth0 as an active interface with an up link.
Nov 25 18:23:14 typhoon kernel: [ 660.529184] bonding: bond0: doing slave updates when interface is down.
Nov 25 18:23:14 typhoon kernel: [ 660.541486] bonding: bond0: Adding slave eth1.
Nov 25 18:23:14 typhoon kernel: [ 660.557487] bonding bond0: master_dev is not up in bond_enslave
Nov 25 18:23:15 typhoon kernel: [ 660.642335] bonding: bond0: Warning: failed to get speed and duplex from eth1, assumed to be 100Mb/sec and Full.
Nov 25 18:23:15 typhoon kernel: [ 660.666092] bonding: bond0: enslaving eth1 as an active interface with an up link.
Nov 25 18:23:15 typhoon kernel: [ 660.685936] bonding: bond0: setting mode to 802.3ad (4).
Nov 25 18:23:15 typhoon kernel: [ 660.696066] bonding: bond0: Setting MII monitoring interval to 100.
Nov 25 18:23:15 typhoon kernel: [ 660.726049] bonding: bond0: Setting up delay to 200.
Nov 25 18:23:15 typhoon kernel: [ 660.745152] bonding: bond0: Setting down delay to 200.
Nov 25 18:23:15 typhoon kernel: [ 660.859744] 802.1Q VLAN Support v1.8 Ben Greear <gre...@candelatech.com>
Nov 25 18:23:15 typhoon kernel: [ 660.874809] All bugs added by David S. Miller <da...@redhat.com>
Nov 25 18:23:15 typhoon kernel: [ 660.914426] bonding: bond0: link status down for idle interface eth0, disabling it in 200 ms.
Nov 25 18:23:15 typhoon kernel: [ 660.934442] bonding: bond0: link status down for idle interface eth1, disabling it in 200 ms.
Nov 25 18:23:15 typhoon kernel: [ 660.958932] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:15 typhoon kernel: [ 661.074838] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:15 typhoon kernel: [ 661.157465] bonding: bond0: link status definitely down for interface eth0, disabling it
Nov 25 18:23:15 typhoon kernel: [ 661.174852] bonding: Warning: bond0: link status changed for uninitialized port on eth0
Nov 25 18:23:15 typhoon kernel: [ 661.206835] bonding: bond0: link status definitely down for interface eth1, disabling it
Nov 25 18:23:15 typhoon kernel: [ 661.226839] bonding: Warning: bond0: link status changed for uninitialized port on eth1
Nov 25 18:23:15 typhoon kernel: [ 661.250843] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:15 typhoon kernel: [ 661.363972] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:15 typhoon kernel: [ 661.642545] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:15 typhoon kernel: [ 661.752000] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:15 typhoon kernel: [ 661.865307] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:16 typhoon kernel: [ 661.977297] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:16 typhoon kernel: [ 662.089290] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:16 typhoon kernel: [ 662.201283] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:16 typhoon kernel: [ 662.313290] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:16 typhoon kernel: [ 662.425339] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:16 typhoon kernel: [ 662.537281] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:16 typhoon kernel: [ 662.649339] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:16 typhoon kernel: [ 663.585328] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:16 typhoon kernel: [ 663.697327] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:17 typhoon kernel: [ 663.809385] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:17 typhoon kernel: [ 663.921327] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:17 typhoon kernel: [ 664.033385] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:17 typhoon kernel: [ 665.509363] tg3: eth1: Link is up at 1000 Mbps, full duplex.
Nov 25 18:23:17 typhoon kernel: [ 665.509380] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:17 typhoon kernel: [ 665.509383] bonding: bond0: link status up for interface eth1, enabling it in 200 ms.
Nov 25 18:23:17 typhoon kernel: [ 665.509385] bonding: Warning: bond0: speed changed for uninitialized port on eth1
Nov 25 18:23:17 typhoon kernel: [ 665.509363] tg3: eth1: Flow control is on for TX and on for RX.
Nov 25 18:23:17 typhoon kernel: [ 665.608084] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:17 typhoon kernel: [ 665.790285] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:17 typhoon kernel: [ 666.217860] bonding: bond0: link status definitely up for interface eth1.
Nov 25 18:23:17 typhoon kernel: [ 666.232912] bonding: Warning: bond0: link status changed for uninitialized port on eth1
Nov 25 18:23:17 typhoon kernel: [ 666.317357] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:17 typhoon kernel: [ 666.427194] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:17 typhoon kernel: [ 666.540477] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:18 typhoon kernel: [ 666.588499] tg3: eth0: Link is up at 1000 Mbps, full duplex.
Nov 25 18:23:18 typhoon kernel: [ 666.588499] tg3: eth0: Flow control is on for TX and on for RX.
Nov 25 18:23:18 typhoon kernel: [ 666.721006] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:18 typhoon kernel: [ 666.734330] bonding: bond0: link status up for interface eth0, enabling it in 200 ms.
Nov 25 18:23:18 typhoon kernel: [ 667.099318] bonding: Warning: bond0: speed changed for uninitialized port on eth0
Nov 25 18:23:18 typhoon kernel: [ 667.182617] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:18 typhoon kernel: [ 667.293892] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:18 typhoon kernel: [ 667.313883] bonding: bond0: link status definitely up for interface eth0.
Nov 25 18:23:18 typhoon kernel: [ 667.327292] bonding: Warning: bond0: link status changed for uninitialized port on eth0
Nov 25 18:23:18 typhoon kernel: [ 667.498398] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:18 typhoon kernel: [ 667.610335] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:18 typhoon kernel: [ 667.722273] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:18 typhoon kernel: [ 667.834211] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:18 typhoon kernel: [ 668.533697] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:18 typhoon kernel: [ 668.645634] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:19 typhoon kernel: [ 668.757573] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:19 typhoon kernel: [ 668.869509] bonding: bond0: Warning: Found an uninitialized port
Nov 25 18:23:19 typhoon kernel: [ 668.981448] bonding: bond0: Warning: Found an uninitialized port
And it keeps going, the network is not bringed up. But, after the system is up and I run
/etc/init.d/networking restart
everything seems to work and the bond is up and working
syslog says then this:
Nov 26 14:15:28 typhoon kernel: [ 255.320035] bonding: bond0: Warning: Found an uninitialized port
Nov 26 14:15:28 typhoon postfix/master[1287]: reload -- version 2.6.5, configuration /etc/postfix
Nov 26 14:15:28 typhoon kernel: [ 255.409602] bonding: bond0: Removing slave eth0
Nov 26 14:15:28 typhoon kernel: [ 255.409610] bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:40:d0:ac:1c:da - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Nov 26 14:15:28 typhoon kernel: [ 255.409616] bonding: Warning: bond0: Trying to unbind an uninitialized port on eth0
Nov 26 14:15:28 typhoon kernel: [ 255.409619] bonding: bond0: releasing backup interface eth0
Nov 26 14:15:28 typhoon kernel: [ 255.409643] device eth0 left promiscuous mode
Nov 26 14:15:28 typhoon kernel: [ 255.425022] bonding: bond0: Warning: Found an uninitialized port
Nov 26 14:15:28 typhoon kernel: [ 255.501718] tg3 0000:11:04.0: PME# enabled
Nov 26 14:15:28 typhoon kernel: [ 255.519708] bonding: bond0: Removing slave eth1
Nov 26 14:15:28 typhoon kernel: [ 255.519714] bonding: Warning: bond0: Trying to unbind an uninitialized port on eth1
Nov 26 14:15:28 typhoon kernel: [ 255.519717] bonding: bond0: releasing backup interface eth1
Nov 26 14:15:28 typhoon kernel: [ 255.519738] device eth1 left promiscuous mode
Nov 26 14:15:28 typhoon kernel: [ 255.599988] tg3 0000:11:04.1: PME# enabled
Nov 26 14:15:28 typhoon postfix/master[1287]: reload -- version 2.6.5, configuration /etc/postfix
Nov 26 14:15:28 typhoon kernel: [ 255.746525] device bond0 left promiscuous mode
Nov 26 14:15:28 typhoon kernel: [ 255.746530] vmbr0: port 1(bond0) entering disabled state
Nov 26 14:15:28 typhoon kernel: [ 255.794195] bonding: bond0: doing slave updates when interface is down.
Nov 26 14:15:28 typhoon kernel: [ 255.794203] bonding: bond0: Adding slave eth0.
Nov 26 14:15:28 typhoon kernel: [ 255.794206] bonding bond0: master_dev is not up in bond_enslave
Nov 26 14:15:28 typhoon kernel: [ 255.808039] tg3 0000:11:04.0: PME# disabled
Nov 26 14:15:28 typhoon kernel: [ 255.824113] tg3 0000:11:04.0: irq 53 for MSI/MSI-X
Nov 26 14:15:28 typhoon kernel: [ 255.888803] bonding: bond0: enslaving eth0 as a backup interface with a down link.
Nov 26 14:15:28 typhoon kernel: [ 255.892737] bonding: bond0: doing slave updates when interface is down.
Nov 26 14:15:28 typhoon kernel: [ 255.892747] bonding: bond0: Adding slave eth1.
Nov 26 14:15:28 typhoon kernel: [ 255.892751] bonding bond0: master_dev is not up in bond_enslave
Nov 26 14:15:28 typhoon kernel: [ 255.909561] tg3 0000:11:04.1: PME# disabled
Nov 26 14:15:28 typhoon kernel: [ 255.925637] tg3 0000:11:04.1: irq 54 for MSI/MSI-X
Nov 26 14:15:28 typhoon kernel: [ 255.977369] bonding: bond0: enslaving eth1 as a backup interface with a down link.
Nov 26 14:15:28 typhoon kernel: [ 255.978652] bonding: bond0: setting mode to 802.3ad (4).
Nov 26 14:15:28 typhoon kernel: [ 255.978690] bonding: bond0: Setting MII monitoring interval to 100.
Nov 26 14:15:28 typhoon kernel: [ 255.978693] bonding: bond0: Note: Updating updelay (to 200) since it is a multiple of the miimon value.
Nov 26 14:15:28 typhoon kernel: [ 255.978697] bonding: bond0: Note: Updating downdelay (to 200) since it is a multiple of the miimon value.
Nov 26 14:15:28 typhoon kernel: [ 255.978733] bonding: bond0: Setting up delay to 200.
Nov 26 14:15:28 typhoon kernel: [ 255.978762] bonding: bond0: Setting down delay to 200.
Nov 26 14:15:29 typhoon postfix/master[1287]: reload -- version 2.6.5, configuration /etc/postfix
Nov 26 14:15:29 typhoon kernel: [ 256.267428] device bond0 entered promiscuous mode
Nov 26 14:15:29 typhoon kernel: [ 256.269252] ADDRCONF(NETDEV_UP): bond0: link is not ready
Nov 26 14:15:31 typhoon kernel: [ 258.721574] tg3: eth0: Link is up at 1000 Mbps, full duplex.
Nov 26 14:15:31 typhoon kernel: [ 258.721580] tg3: eth0: Flow control is on for TX and on for RX.
Nov 26 14:15:31 typhoon kernel: [ 258.728595] tg3: eth1: Link is up at 1000 Mbps, full duplex.
Nov 26 14:15:31 typhoon kernel: [ 258.728599] tg3: eth1: Flow control is on for TX and on for RX.
Nov 26 14:15:31 typhoon kernel: [ 258.764023] bonding: bond0: link status up for interface eth0, enabling it in 0 ms.
Nov 26 14:15:31 typhoon kernel: [ 258.764029] bonding: bond0: link status up for interface eth1, enabling it in 200 ms.
Nov 26 14:15:31 typhoon kernel: [ 258.764032] bonding: bond0: link status definitely up for interface eth0.
Nov 26 14:15:31 typhoon kernel: [ 258.764908] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Nov 26 14:15:31 typhoon kernel: [ 258.764998] vmbr0: port 1(bond0) entering learning state
Nov 26 14:15:31 typhoon kernel: [ 258.964014] bonding: bond0: link status definitely up for interface eth1.
Nov 26 14:15:39 typhoon kernel: [ 266.960010] vmbr0: no IPv6 routers present
Nov 26 14:15:42 typhoon kernel: [ 269.288012] bond0: no IPv6 routers present
Nov 26 14:15:46 typhoon kernel: [ 273.764012] vmbr0: port 1(bond0) entering forwarding state
My /etc/network/interfaces file:
auto lo
iface lo inet loopback
auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_mode 4
bond_miimon 100
bond_downdelay 200
bond_updelay 200
auto vmbr0
iface vmbr0 inet static
bridge_ports bond0
address x.x.x.x
netmask 255.255.255.240
gateway x.x.x.x
It was the same, when there was no bridge.
This bug occures on both of my Fujitsu-Siemens RX330S1 servers with tg3 netowrk card and it renders
auto system restart to not work anymore!
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ifenslave-2.6 depends on:
ii iproute 20090324-1 networking and traffic control too
ii libc6 2.10.2-2 GNU C Library: Shared libraries
Versions of packages ifenslave-2.6 recommends:
ii net-tools 1.60-23 The NET-3 networking toolkit
ifenslave-2.6 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Guus Sliepen
> When the system is tarted, my bond interface is not started and [...] the network is not bringed up. But, after the system is up and I run
> /etc/init.d/networking restart
> everything seems to work and the bond is up and working
[...]
> It was the same, when there was no bridge.
> This bug occures on both of my Fujitsu-Siemens RX330S1 servers with tg3 netowrk card and it renders
> auto system restart to not work anymore!
I don't know why this doesn't work for. Can you try, each time after rebooting, the following things:
1. ifdown bond0; ifup bond0
2. ifconfig bond0 down; ifconfig bond0 up
3. ifconfig eth0 down; ifconfig eth0 up
4. ifconfig eth1 down; ifconfig eth1 up
Also, after rebooting, what is the output of ifconfig -a and brctl show? Maybe
this information helps narrowing down when and why it goes wrong.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <gu...@debian.org>