Begin forwarded message:

Date: Wed, 17 Aug 2005 07:20:36 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 5080] New: bonding related oops on boot


http://bugzilla.kernel.org/show_bug.cgi?id=5080

           Summary: bonding related oops on boot
    Kernel Version: 2.6.13-rc6
            Status: NEW
          Severity: normal
             Owner: [EMAIL PROTECTED]
         Submitter: [EMAIL PROTECTED]


Distribution: debian pure64
Hardware Environment: 4 way x86_64
Software Environment: linux 2.6.12, 2.6.13-rc6 
Problem Description:

I have a bond with two slave interfaces, both connected.

On boot, when the bond gets initialized, I get the following oops:

[  136.773164] Ethernet Channel Bonding Driver: v2.6.3 (June 8, 2005)
[  136.773266] bonding: In ALB mode you might experience client disconnections
upon reconnection of a link if the bonding module updelay parameter (15000 msec)
is incompatible with the forwarding delay time of the switch
[  136.773427] bonding: MII link monitoring set to 100 ms
[  137.122235] bonding: bond0: enslaving eth0 as an active interface with a down
link.
[  137.353781] bonding: bond0: enslaving eth1 as an active interface with a down
link.
[  137.397579] e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex
[  138.823615] NET: Registered protocol family 10
[  138.824319] IPv6 over IPv4 tunneling driver
[  142.995176] tg3: eth0: Link is up at 1000 Mbps, full duplex.
[  142.995238] tg3: eth0: Flow control is on for TX and on for RX.
[  142.995294] bonding: bond0: link status up for interface eth0, enabling it in
15000 ms.
[  144.226482] tg3: eth1: Link is up at 1000 Mbps, full duplex.
[  144.226543] tg3: eth1: Flow control is on for TX and on for RX.
[  144.293858] bonding: bond0: link status up for interface eth1, enabling it in
15000 ms.
[  149.051679] eth0: no IPv6 routers present
[  149.311570] bond0: no IPv6 routers present
[  149.661411] eth1: no IPv6 routers present
[  149.781362] eth2: no IPv6 routers present
[  157.987577] bonding: bond0: link status definitely up for interface eth0.

[  157.987642] bonding: bond0: making interface eth0 the new active one.
[  158.023763] RTNL: assertion failed at net/ipv4/devinet.c (962)
[  158.023819]
[  158.023820] Call Trace: <IRQ> <ffffffff80273c03>{rt_run_flush+48}
<ffffffff8029d6c8>{inetdev_event+116}
[  158.023964]        <ffffffff80273c4e>{rt_run_flush+123}
<ffffffff8013f087>{notifier_call_chain+31}
[  158.024094]        <ffffffff802610f8>{dev_set_mac_address+84}
<ffffffff88035740>{:bonding:alb_set_slave_mac_addr+76}
[  158.024233]        <ffffffff8803580f>{:bonding:alb_swap_mac_addr+170}
<ffffffff8802f0b8>{:bonding:bond_change_active_slave+546}
[  158.024373]        <ffffffff8802f997>{:bonding:bond_mii_monitor+1012}
<ffffffff8802f5a3>{:bonding:bond_mii_monitor+0}
[  158.024507]        <ffffffff8013a86a>{run_timer_softirq+384}
<ffffffff80136d42>{__do_softirq+110}
[  158.024631]        <ffffffff8010ec07>{call_softirq+31}
<ffffffff801106a1>{do_softirq+54}
[  158.024752]        <ffffffff8010e3b6>{apic_timer_interrupt+98}  <EOI>
<ffffffff801f7cbc>{acpi_walk_namespace+117}
[  158.024886]        <ffffffff8010bf4b>{mwait_idle+86}
<ffffffff80207694>{acpi_processor_idle+298}
[  158.025011]        <ffffffff8010bedb>{cpu_idle+76}
<ffffffff803fc708>{start_kernel+372}
[  158.025130]        <ffffffff803fc216>{_sinittext+534}
[  158.061376] RTNL: assertion failed at net/ipv4/devinet.c (962)
[  158.061431]
[  158.061432] Call Trace: <IRQ> <ffffffff80273c32>{rt_run_flush+95}
<ffffffff8029d6c8>{inetdev_event+116}
[  158.061569]        <ffffffff80273c4e>{rt_run_flush+123}
<ffffffff8013f087>{notifier_call_chain+31}
[  158.061693]        <ffffffff802610f8>{dev_set_mac_address+84}
<ffffffff88035740>{:bonding:alb_set_slave_mac_addr+76}
[  158.061826]        <ffffffff88035821>{:bonding:alb_swap_mac_addr+188}
<ffffffff8802f0b8>{:bonding:bond_change_active_slave+546}
[  158.061963]        <ffffffff8802f997>{:bonding:bond_mii_monitor+1012}
<ffffffff8802f5a3>{:bonding:bond_mii_monitor+0}
[  158.062096]        <ffffffff8013a86a>{run_timer_softirq+384}
<ffffffff80136d42>{__do_softirq+110}
[  158.062219]        <ffffffff8010ec07>{call_softirq+31}
<ffffffff801106a1>{do_softirq+54}
[  158.062338]        <ffffffff8010e3b6>{apic_timer_interrupt+98}  <EOI>
<ffffffff801f7cbc>{acpi_walk_namespace+117}
[  158.062470]        <ffffffff8010bf4b>{mwait_idle+86}
<ffffffff80207694>{acpi_processor_idle+298}
[  158.062593]        <ffffffff8010bedb>{cpu_idle+76}
<ffffffff803fc708>{start_kernel+372}
[  158.062711]        <ffffffff803fc216>{_sinittext+534}
[  159.366930] bonding: bond0: link status definitely up for interface eth1.

The bond has the following options:
 options bonding mode=6 miimon=100 updelay=15000 max_bonds=2

I know this doesn't appear with 2.6.11.12, and that it did in a 2.6.12, although
I don't know which precisely :(

I'll attach my .config

Steps to reproduce: just boot :p

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to