Tim Durack [EMAIL PROTECTED] :
[snip]
Can you try 2.6.22-rc5 +
http://www.fr.zoreil.com/people/francois/misc/20070619-2.6.22-rc5-r8169-test.patch
It does not seem to work too bad here (tested with 2.6.22-rc5 + patch):
# grep bonding /etc/modprobe.conf
alias bond0 bonding
options bonding
Yup. Works fine. The randomly changing interface order is proving to
be a challenge!
udev should be your friend to do a BUS/ID based rename.
True, but so far I have to force link addrs, force promisc mode, and
now add a udev work-around ;-|
Strange thing is, when the interfaces get
On 5/2/07, Tim Durack [EMAIL PROTECTED] wrote:
Yup. Works fine. The randomly changing interface order is proving to
be a challenge!
udev should be your friend to do a BUS/ID based rename.
Okay, the udev workaround isn't too painful.
Would be great if I could do something like
A tcpdump trace 1) before promiscuous mode 2) after promiscuous mode 3)
after link failure (i.e. failover does not work) would be welcome.
Okay, after fixing STP forwarding delays on the switch, bonding
failover now works, as long as member links are forced to promisc
mode.
Still Have a
Tim Durack [EMAIL PROTECTED] :
[...]
Still Have a problem with links randomly failing to achieve link on
boot. This then requires a modprobe -r r8169; modprobe r8169 cycle
to get link. Side effect is the mac address corruption I have
described previously.
Can you try to set the MAC address by
Can you try to set the MAC address by hand with the completely patched
kernel (i.e. including the mac-address-change patch) ?
Yup. Works fine. The randomly changing interface order is proving to
be a challenge!
Given the last report in http://bugzilla.kernel.org/show_bug.cgi?id=6032,
it
Tim Durack [EMAIL PROTECTED] :
Can you try to set the MAC address by hand with the completely patched
kernel (i.e. including the mac-address-change patch) ?
Yup. Works fine. The randomly changing interface order is proving to
be a challenge!
udev should be your friend to do a BUS/ID based
Can you revert patch #0012 and see if it changes this part of the problem ?
Reverted. mac is still wrong - I assume the eprom got corrupted somehow.
~# modprobe r8169
r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
ACPI: PCI Interrupt :00:09.0[A] - GSI 18 (level, low) - IRQ 16
eth1:
A tcpdump trace 1) before promiscuous mode 2) after promiscuous mode 3)
after link failure (i.e. failover does not work) would be welcome.
See attached. Captures performed on bond0. Let me know if you prefer
captures against the physical member interfaces.
Tim:
promisc-off.pcap
Description:
On 4/30/07, Tim Durack [EMAIL PROTECTED] wrote:
A tcpdump trace 1) before promiscuous mode 2) after promiscuous mode 3)
after link failure (i.e. failover does not work) would be welcome.
See attached. Captures performed on bond0. Let me know if you prefer
captures against the physical member
See:
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.21-rc7/
Please Cc: netdev on success/failure.
Applied suggested patchset to vanilla 2.6.21.
Compiled using .config from linux-image-2.6.21-rc7 pulled down from
http://kernel-archive.buildserver.net/debian-kernel
Compiles, boots.
Bonding
Tim Durack [EMAIL PROTECTED] wrote:
[...]
Bond comes up, cannot ping unless I manually force promisc on both member
links:
ip link set dev eth1 promisc on
ip link set dev eth2 promisc off
From looking at the source code for r8169, but it appears that
the r8169 driver only reads the
ip link set dev eth1 promisc on
ip link set dev eth2 promisc off
typo, ip link set dev eth2 promisc on of course
From looking at the source code for r8169, but it appears that
the r8169 driver only reads the device MAC address at probe time, and
doesn't propogate changes to the MAC
Tim Durack [EMAIL PROTECTED] :
[...]
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
Francois Romieu [EMAIL PROTECTED] :
[...]
A tcpdump trace 1) before promiscuous mode 2) after promiscuous mode 3)
after link failure (i.e. failover does not work) would be welcome.
A 'lspci -vx' will be needed too. There are different kinds of 8169.
--
Ueimor
Anybody got a battery for my
15 matches
Mail list logo
