[Server-devel] Bonding regression on 2.6.27

[Anna]

On Tue, Dec 9, 2008 at 11:49 AM, Jesper Krogh <jesper at krogh.cc> wrote:

>
> I reverted the systems to the latest 2.6.26.8 kernel and it havent been
> on my priority list since.. unfortunately.


I reinstalled fresh and, after the usual setup stuff, compiled and installed
2.6.26.8 according to these instructions:

http://www.howtoforge.com/kernel_compilation_fedora_p2

So now I've got this:

[root at schoolserver1 ~]# uname -a
Linux schoolserver1 2.6.26.8 #1 SMP Tue Dec 9 15:16:54 CST 2008 i686 i686
i386 GNU/Linux

In the messages, I saw it was complaining it didn't know how to bring up
bonding.  So, per Jerry's earlier suggestion, I edited
/etc/modprobe.d/xs_bonding with this:

options lanbond0 mode=active-backup miimon=100
options mshbond0 mode=active-backup miimon=100
options mshbond1 mode=active-backup miimon=100
options mshbond2 mode=active-backup miimon=100

But after a reboot, this is in /var/log/messages:

Dec  9 16:57:05 schoolserver1 kernel: bonding: MII link monitoring set to
100 ms
Dec  9 16:57:05 schoolserver1 kernel: bonding: lanbond0 is being created...
Dec  9 16:57:05 schoolserver1 kernel: ADDRCONF(NETDEV_UP): lanbond0: link is
not ready
Dec  9 16:57:05 schoolserver1 kernel: bonding: mshbond0 is being created...
Dec  9 16:57:05 schoolserver1 kernel: ADDRCONF(NETDEV_UP): mshbond0: link is
not ready
Dec  9 16:57:05 schoolserver1 kernel: bonding: mshbond1 is being created...
Dec  9 16:57:05 schoolserver1 kernel: ADDRCONF(NETDEV_UP): mshbond1: link is
not ready
Dec  9 16:57:05 schoolserver1 kernel: bonding: mshbond2 is being created...
Dec  9 16:57:05 schoolserver1 kernel: ADDRCONF(NETDEV_UP): mshbond2: link is
not ready

I have an AP set to 172.18.96.5 plugged into eth1, but can't ping it.  The
link is up, though:

[root at schoolserver1 ~]# ethtool eth1
Settings for eth1:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Advertised auto-negotiation: Yes
    Speed: 100Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: on
    Supports Wake-on: umbg
    Wake-on: g
    Current message level: 0x00000007 (7)
    Link detected: yes

So using the older kernel didn't automagically fix things, at least not for
me.

Anna Schoolfield
Birmingham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/server-devel/attachments/20081209/a2fda69c/attachment.htm