[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#466404: marked as done (RTNL: assertion failed at net/ipv4/devinet.c when using bonding)

Your message dated Mon, 28 Apr 2008 16:57:43 -0600
with message-id <20080428225743.GE31568@colo.lackof.org>
and subject line Re: Bug#466404: RTNL: assertion failed at net/ipv4/devinet.c when using bonding
has caused the Debian Bug report #466404,
regarding RTNL: assertion failed at net/ipv4/devinet.c when using bonding
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
466404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466404
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-5-amd64
Version: 2.6.18.dfsg.1-17
Severity: important


When booting the system with bonding activated, we get this type of trace with dmesg:

Ethernet Channel Bonding Driver: v3.0.3 (March 23, 2006)
bonding: In ALB mode you might experience client disconnections upon reconnection of a link if the bonding mod
ule updelay parameter (200 msec) is incompatible with the forwarding delay time of the switch
bonding: MII link monitoring set to 100 ms
bonding: bond0: enslaving eth0 as an active interface with a down link.
bonding: bond0: enslaving eth1 as an active interface with a down link.
e1000: eth2: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
e1000: eth3: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_UP): bond0: link is not ready
IPv6 over IPv4 tunneling driver
bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
bonding: bond0: link status up for interface eth0, enabling it in 200 ms.
bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex
bonding: bond0: link status up for interface eth1, enabling it in 200 ms.
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
RTNL: assertion failed at net/ipv4/devinet.c (985)

Call Trace:
 <IRQ> [<ffffffff803dea81>] inetdev_event+0x48/0x283
 [<ffffffff80264196>] notifier_call_chain+0x20/0x32
 [<ffffffff80290da3>] raw_notifier_call_chain+0x9/0xb
 [<ffffffff8808b9f3>] :bnx2:bnx2_change_mac_addr+0x4d/0x59
 [<ffffffff803ab85f>] dev_set_mac_address+0x52/0x58
 [<ffffffff881a2a73>] :bonding:alb_set_slave_mac_addr+0x41/0x6c
 [<ffffffff881a2eec>] :bonding:alb_swap_mac_addr+0x95/0x169
 [<ffffffff881a3289>] :bonding:bond_alb_handle_active_change+0xac/0xe1
 [<ffffffff8819e053>] :bonding:bond_change_active_slave+0x1fd/0x318
 [<ffffffff8819ff49>] :bonding:bond_mii_monitor+0x3b8/0x40e
 [<ffffffff8819fb91>] :bonding:bond_mii_monitor+0x0/0x40e
 [<ffffffff8028de5d>] run_timer_softirq+0x13b/0x1be
 [<ffffffff8020ffa8>] __do_softirq+0x52/0xcb
 [<ffffffff8025c31c>] call_softirq+0x1c/0x28
 [<ffffffff802698f7>] do_softirq+0x2c/0x7d
 [<ffffffff8028a782>] irq_exit+0x3f/0x4c
 [<ffffffff80272cfb>] smp_apic_timer_interrupt+0x3d/0x3f
 [<ffffffff80255a14>] mwait_idle+0x0/0x4a
 [<ffffffff8025bcba>] apic_timer_interrupt+0x66/0x6c
 <EOI> [<ffffffff80255a4a>] mwait_idle+0x36/0x4a
 [<ffffffff80247ad5>] cpu_idle+0x92/0xc9
 [<ffffffff80272440>] start_secondary+0x440/0x44f

RTNL: assertion failed at net/ipv4/devinet.c (985)

Call Trace:
 <IRQ> [<ffffffff803dea81>] inetdev_event+0x48/0x283
 [<ffffffff80264196>] notifier_call_chain+0x20/0x32
 [<ffffffff80290da3>] raw_notifier_call_chain+0x9/0xb
 [<ffffffff8808b9f3>] :bnx2:bnx2_change_mac_addr+0x4d/0x59
 [<ffffffff803ab85f>] dev_set_mac_address+0x52/0x58
 [<ffffffff881a2a73>] :bonding:alb_set_slave_mac_addr+0x41/0x6c
 [<ffffffff881a2efe>] :bonding:alb_swap_mac_addr+0xa7/0x169
 [<ffffffff881a3289>] :bonding:bond_alb_handle_active_change+0xac/0xe1
 [<ffffffff8819e053>] :bonding:bond_change_active_slave+0x1fd/0x318
 [<ffffffff8819eb7d>] :bonding:bond_select_active_slave+0xa5/0xd9
 [<ffffffff8819ff49>] :bonding:bond_mii_monitor+0x3b8/0x40e
 [<ffffffff8819fb91>] :bonding:bond_mii_monitor+0x0/0x40e
 [<ffffffff8028de5d>] run_timer_softirq+0x13b/0x1be
 [<ffffffff8020ffa8>] __do_softirq+0x52/0xcb
 [<ffffffff8025c31c>] call_softirq+0x1c/0x28
 [<ffffffff802698f7>] do_softirq+0x2c/0x7d
 [<ffffffff8028a782>] irq_exit+0x3f/0x4c
 [<ffffffff80272cfb>] smp_apic_timer_interrupt+0x3d/0x3f
 [<ffffffff80255a14>] mwait_idle+0x0/0x4a
 [<ffffffff8025bcba>] apic_timer_interrupt+0x66/0x6c
 <EOI> [<ffffffff80255a4a>] mwait_idle+0x36/0x4a
 [<ffffffff80247ad5>] cpu_idle+0x92/0xc9
 [<ffffffff80272440>] start_secondary+0x440/0x44f

bonding: bond0: first active interface up!
bonding: bond0: link status definitely up for interface eth1.
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready

# cat /etc/modprobe.d/arch/i386
[...]
alias bond0 bonding
options bonding mode=6 miimon=100 downdelay=200 updelay=200

Using 2 Broadcom cards:

03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)
        Subsystem: Hewlett-Packard Company NC373i Integrated Multifunction Gigabit Server Adapter
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 185
        Memory at f8000000 (64-bit, non-prefetchable) [size=32M]
        [virtual] Expansion ROM at d1200000 [disabled] [size=2K]
        Capabilities: [40] PCI-X non-bridge device
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)
        Subsystem: Hewlett-Packard Company NC373i Integrated Multifunction Gigabit Server Adapter
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 98
        Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
        [virtual] Expansion ROM at d1300000 [disabled] [size=2K]
        Capabilities: [40] PCI-X non-bridge device
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

# cat /etc/network/interfaces
[...]
auto bond0
# Bonding of the 2 Gigabit interfaces
iface bond0 inet static
        name VLAN 6 Room 3.0
        address 192.168.100.2
        netmask 255.255.240.0
        broadcast 192.168.111.255
        network 192.168.96.0
        up /sbin/ifenslave bond0 eth0
        up /sbin/ifenslave bond0 eth1
[...]

The bonding seems however to work but no stress test has been done yet.

TIA,
Bruno


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-telco-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-5-amd64 depends on:
ii  cor 5.97-5.3                             The GNU core utilities
ii  deb 1.5.11etch1                          Debian configuration management sy
ii  e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib
ii  ini 0.85h                                tools for generating an initramfs
ii  mod 3.3-pre4-2                           tools for managing Linux kernel mo

linux-image-2.6.18-5-amd64 recommends no packages.

-- debconf information:
  linux-image-2.6.18-5-amd64/postinst/create-kimage-link-2.6.18-5-amd64: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-5-amd64/postinst/old-system-map-link-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/initrd-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/preinst/elilo-initrd-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/postinst/depmod-error-2.6.18-5-amd64: false
  linux-image-2.6.18-5-amd64/preinst/bootloader-initrd-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/prerm/removing-running-kernel-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/already-running-this-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/preinst/lilo-initrd-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/abort-overwrite-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/preinst/failed-to-move-modules-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/prerm/would-invalidate-boot-loader-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/postinst/bootloader-error-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/postinst/old-initrd-link-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/overwriting-modules-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/postinst/old-dir-initrd-link-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-5-amd64/postinst/depmod-error-initrd-2.6.18-5-amd64: false
  linux-image-2.6.18-5-amd64/postinst/bootloader-test-error-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/postinst/kimage-is-a-directory:
  linux-image-2.6.18-5-amd64/preinst/abort-install-2.6.18-5-amd64:

--- End Message ---
--- Begin Message --- 
Version: 2.6.23-1

On Sat, Apr 26, 2008 at 01:34:44PM +0100, Duncan Gibb wrote:
> We can reproduce this bug - or something remarkably similar - in a
> running (as opposed to newly booting) system of a different architecture
> to the original reporter.

Thanks Duncan.
git-bisect points to this change as a fix:
  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0b0eef66419e9abe6fd62bc958ab7cd0a18f858e

This change first appeared in 2.6.23.

Since this is a non-trivial fix (lots of rewriting) and its not known
to cause any "real" problems, I don't think it would be a candidate
for etch's 2.6.18.

Using mode 5 maybe a workaround for this issue, if it meets your
requirements.

-- 
dann frazier

--- End Message ---
Reply to: