Bug#699269: IPv6 slow and hangs over failed bonding link

[Jonathan Nieder <jrnieder@gmail.com>]

Hi Gasha,

Gasha wrote:

> Package: linux
> Version: 3.2.0-2-amd64

What version?  The above is part of the package name, not the version
number --- you can see the currently running version of Linux with

	cat /proc/version

(look in the parentheses) or the currently installed version with

	dpkg-query -W linux-image-$(uname -r)

([1] has more details.)

[...]
> Two ethernet interfaces configured in bond0: (/etc/network/interfaces)
[...]
> One ethernet cable was disconnected, before planned reconfiguration
> works: (dmesg)
>
> [21698247.247121] bonding: bond0: link status down for interface eth1, disabling it in 200 ms.
> [21698247.446804] bonding: bond0: link status definitely down for interface eth1, disabling it
>
> ifconfig eth1 still shows it up.
> HP Procurve Gigabit switch configured as multilink trunk.
> Everything worked when both cables were connected.
>
> VirtualBox machine is running using bridged interface br576
>
> I tried to copy large file over NFS4 / IPv6 and it freeze to very
> low speed. cp command hung, and we had to reboot virtual machine, as
> it was hanging. at destination NFS server file was growing but
> slowly.
> tcpdump showed short bursts of data and then again 5-15 seconds nothing.
>
> After reboot i reproduced this behaviour using "scp":
> scp to ipv6 address:

I'll let others more knowledgeable than I am answer about the
substance of your report. :)

Is this a regression (if so, do you remember which upgrade broke
things?) or has this procedure always failed this way?  Are more
recent 3.2.y kernels and 3.7.y from experimental also affected?

Thanks for writing,
Jonathan

[1] http://kernel-handbook.alioth.debian.org/ch-versions.html#s-version-types