[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070427220918.GB24358@electric-eye.fr.zoreil.com>
Date: Sat, 28 Apr 2007 00:09:18 +0200
From: Francois Romieu <romieu@...zoreil.com>
To: Tim Durack <tdurack@...il.com>
Cc: netdev@...r.kernel.org
Subject: Re: r8169 ethernet bonding problems
Tim Durack <tdurack@...il.com> :
[...]
> Link failover does not work reliably. Carrier-detect appears to be
> working, so I don't think that is an issue.
>
>
> A disturbing problem is mac corruption after "modprobe -r r8169; modprobe
> r8169"
>
> ip link sh:
>
> 2: eth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
> link/ether 00:00:00:00:68:93 brd ff:ff:ff:ff:ff:ff
> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:30:18:ab:68:94 brd ff:ff:ff:ff:ff:ff
> 4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
> link/ether 00:30:18:ab:68:95 brd ff:ff:ff:ff:ff:ff
>
> eth5 mac was 00:30:18:ab:68:93 before the modprobe.
Can you revert patch #0012 and see if it changes this part of the problem ?
A tcpdump trace 1) before promiscuous mode 2) after promiscuous mode 3)
after link failure (i.e. failover does not work) would be welcome.
> Not sure what's going on here, but I'm starting to think these
> interfaces aren't the best in the world...
The maintainer/driver/hardware combination is a bit quirky at times
but it does not work too bad. :o)
--
Ueimor
Anybody got a battery for my Ultra 10 ?
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists