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

Bug#445749: marked as done (Kernel assertion failure when using bonding)

Your message dated Tue, 4 Aug 2009 23:28:05 +0200
with message-id <20090804212805.GA26320@inutil.org>
and subject line Re: Kernel assertion failure when using bonding
has caused the Debian Bug report #445749,
regarding Kernel assertion failure 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.)


-- 
445749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445749
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-5-686
Version: 2.6.18.dfsg.1-13etch3

ifenslave version: ifenslave-2.6 1.1.0-6

After setting up bonding for two ethernet devices, the kernel complains
about an assertion failure (viewable with dmesg) in net/ipv4/devinet.c.
Bonding seems to work, but it's hardly comforting.

Configuration:

In /etc/network/interfaces:
auto bond0
iface bond0 inet static
        address 10.0.0.2
        netmask 255.255.255.0
        gateway 10.0.0.1
        broadcast 10.0.0.255
        up ifenslave bond0 eth0 eth1
        down ifenslave -d bond0 eth0 eth1

(IP information has been modified.  Actual address is a 10.* address
with the same netmask, available in private email to a developer on
request).

/etc/modprobe.d/bonding:
alias bond0 bonding
options bond0 mode=balance-alb miimon=100

(this file also symlinked to /etc/modutils/bonding.  have run
update-modules)


Computer is a Hewlett Packard DL380 G5, ethernet devices in lspci:
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)
05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)

lspci -n:
03:00.0 0200: 14e4:164c (rev 12)
05:00.0 0200: 14e4:164c (rev 12)

relevant dmesg output:
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, 100 Mbps full duplex, receive & transmit flow control ON
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
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)
 [<c0261c66>] inetdev_event+0x3e/0x286
 [<c02807fa>] _spin_lock_bh+0xb/0x18
 [<c02807f7>] _spin_lock_bh+0x8/0x18
 [<c023eed0>] rt_run_flush+0x68/0x8f
 [<c01284c3>] notifier_call_chain+0x19/0x32
 [<c0228361>] dev_set_mac_address+0x46/0x4b
 [<f8b8ed7b>] alb_set_slave_mac_addr+0x5a/0x7f [bonding]
 [<f8b8f15f>] alb_swap_mac_addr+0x8a/0x138 [bonding]
 [<f8b8a9f1>] bond_change_active_slave+0x187/0x27f [bonding]
 [<f8b8b411>] bond_select_active_slave+0x8d/0xbb [bonding]
 [<f8b8c6a1>] bond_mii_monitor+0x363/0x3a8 [bonding]
 [<f8b8c33e>] bond_mii_monitor+0x0/0x3a8 [bonding]
 [<c0125607>] run_timer_softirq+0xfb/0x151
 [<c0121838>] __do_softirq+0x5a/0xbb
 [<c01218cf>] do_softirq+0x36/0x3a
 [<c0103747>] apic_timer_interrupt+0x1f/0x24
 [<c0101b91>] mwait_idle+0x25/0x38
 [<c0101b52>] cpu_idle+0x9f/0xb9
 [<c03176fd>] start_kernel+0x379/0x380
RTNL: assertion failed at net/ipv4/devinet.c (985)
 [<c0261c66>] inetdev_event+0x3e/0x286
 [<c02807fa>] _spin_lock_bh+0xb/0x18
 [<c02807f7>] _spin_lock_bh+0x8/0x18
 [<c023eed0>] rt_run_flush+0x68/0x8f
 [<c01284c3>] notifier_call_chain+0x19/0x32
 [<c0228361>] dev_set_mac_address+0x46/0x4b
 [<f8b8ed7b>] alb_set_slave_mac_addr+0x5a/0x7f [bonding]
 [<f8b8f16e>] alb_swap_mac_addr+0x99/0x138 [bonding]
 [<f8b8a9f1>] bond_change_active_slave+0x187/0x27f [bonding]
 [<f8b8b411>] bond_select_active_slave+0x8d/0xbb [bonding]
 [<f8b8c6a1>] bond_mii_monitor+0x363/0x3a8 [bonding]
 [<f8b8c33e>] bond_mii_monitor+0x0/0x3a8 [bonding]
 [<c0125607>] run_timer_softirq+0xfb/0x151
 [<c0121838>] __do_softirq+0x5a/0xbb
 [<c01218cf>] do_softirq+0x36/0x3a
 [<c0103747>] apic_timer_interrupt+0x1f/0x24
 [<c0101b91>] mwait_idle+0x25/0x38
 [<c0101b52>] cpu_idle+0x9f/0xb9
 [<c03176fd>] start_kernel+0x379/0x380
bonding: bond0: first active interface up!
ACPI: Power Button (FF) [PWRF]
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
eth0: no IPv6 routers present
bond0: no IPv6 routers present


Thanks,
Øystein
-- 
Outgoing mail is certified Virus Free.

--- End Message ---
--- Begin Message --- 
On Fri, Dec 26, 2008 at 05:39:41PM +0100, Moritz Muehlenhoff wrote:
> On Mon, Oct 08, 2007 at 09:32:27AM +0200, Oystein Viggen wrote:
> > Package: linux-image-2.6.18-5-686
> > Version: 2.6.18.dfsg.1-13etch3
> > 
> > ifenslave version: ifenslave-2.6 1.1.0-6
> > 
> > After setting up bonding for two ethernet devices, the kernel complains
> > about an assertion failure (viewable with dmesg) in net/ipv4/devinet.c.
> > Bonding seems to work, but it's hardly comforting.
> 
> Does this error still occur with more recent kernel versions?
> 
> If you're running Etch, could you try to reproduce this bug
> with the 2.6.24 based kernel added in 4.0r4?
> http://packages.qa.debian.org/l/linux-2.6.24.html

No further feedback, closing the bug.
 
Cheers,
        Moritz

--- End Message ---
Reply to: