I've got problem with balancing-alb mode in kernel 2.6.23.9. After configuring bonding I receive such kind of messages in logs:
-----begin-------- 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 (1053) [<c046f69c>] inetdev_event+0x19c/0x1b0 [<c044607c>] rt_run_flush+0x6c/0x90 [<c01303db>] notifier_call_chain+0x1b/0x40 [<c0435281>] dev_set_mac_address+0x61/0x70 [<f8aaa5b7>] alb_set_slave_mac_addr+0x77/0xa0 [bonding] [<f8aab262>] bond_alb_handle_active_change+0xf2/0x160 [bonding] [<f8aa2099>] bond_change_active_slave+0xf9/0x240 [bonding] [<f8aa21fc>] bond_select_active_slave+0x1c/0x70 [bonding] [<f8aa3420>] bond_mii_monitor+0x170/0x480 [bonding] [<f8aa32b0>] bond_mii_monitor+0x0/0x480 [bonding] [<c012c931>] run_timer_softirq+0xd1/0x1a0 [<c011d0de>] rebalance_tick+0xee/0x110 [<c0127aa9>] __do_softirq+0xc9/0xe0 [<c0127af5>] do_softirq+0x35/0x40 [<c0111cef>] smp_apic_timer_interrupt+0x8f/0xb0 [<c010385f>] apic_timer_interrupt+0x1f/0x24 [<c0100fef>] mwait_idle_with_hints+0x3f/0x50 [<c0101027>] mwait_idle+0x27/0x30 [<c0100e81>] cpu_idle+0x81/0x90 [<c05fb94c>] start_kernel+0x19c/0x1f0 [<c05fb310>] unknown_bootoption+0x0/0x1c0 ======================= -----end------
Is there any patch available to fix this problem? It seems like there is some problem with netlink locking.
Log in to post a comment.
I've got problem with balancing-alb mode in kernel 2.6.23.9. After configuring bonding
I receive such kind of messages in logs:
-----begin--------
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 (1053)
[<c046f69c>] inetdev_event+0x19c/0x1b0
[<c044607c>] rt_run_flush+0x6c/0x90
[<c01303db>] notifier_call_chain+0x1b/0x40
[<c0435281>] dev_set_mac_address+0x61/0x70
[<f8aaa5b7>] alb_set_slave_mac_addr+0x77/0xa0 [bonding]
[<f8aab262>] bond_alb_handle_active_change+0xf2/0x160 [bonding]
[<f8aa2099>] bond_change_active_slave+0xf9/0x240 [bonding]
[<f8aa21fc>] bond_select_active_slave+0x1c/0x70 [bonding]
[<f8aa3420>] bond_mii_monitor+0x170/0x480 [bonding]
[<f8aa32b0>] bond_mii_monitor+0x0/0x480 [bonding]
[<c012c931>] run_timer_softirq+0xd1/0x1a0
[<c011d0de>] rebalance_tick+0xee/0x110
[<c0127aa9>] __do_softirq+0xc9/0xe0
[<c0127af5>] do_softirq+0x35/0x40
[<c0111cef>] smp_apic_timer_interrupt+0x8f/0xb0
[<c010385f>] apic_timer_interrupt+0x1f/0x24
[<c0100fef>] mwait_idle_with_hints+0x3f/0x50
[<c0101027>] mwait_idle+0x27/0x30
[<c0100e81>] cpu_idle+0x81/0x90
[<c05fb94c>] start_kernel+0x19c/0x1f0
[<c05fb310>] unknown_bootoption+0x0/0x1c0
=======================
-----end------
Is there any patch available to fix this problem?
It seems like there is some problem with netlink locking.