Bug#577747: linux-image-2.6.32-5-amd64 - same bug, different HW

[Jan Schermer <zviratko@zviratko.net>]

 Hi,
I'm experiencing the same problem. My kernel is
linux-image-2.6.32-5-amd64, fresh squeezy/testing installation.

I just installed a new home server (Core2Duo, 3 ethernets, wireless, 2x
SATA in RAID1)

I needed to copy some backup data to the server, but once I plugged my
laptop directly into the gigabit port and started copying (rsync+ssh),
SSH died with message:

"Corrupted MAC on input. Disconnecting: Packet corrupt"

This was a direct cable between my laptop and server - eth2 - both
gigabit ethernets.

Googling suggested that my hardware is faulty, so because I also have
those data on the internet, I fired scp in the background and went to work.

I logged back to the server and it died again! Same message!

This time it was a different ethernet port, and different remote server.

root@gw:~# ls -l /sys/class/net/*/device/driver
lrwxrwxrwx 1 root root 0 Oct 21 11:35 /sys/class/net/eth0/device/driver
-> ../../../../bus/pci/drivers/e100
lrwxrwxrwx 1 root root 0 Oct 21 11:35 /sys/class/net/eth1/device/driver
-> ../../../../bus/pci/drivers/3c59x
lrwxrwxrwx 1 root root 0 Oct 21 11:35 /sys/class/net/eth2/device/driver
-> ../../../bus/pci/drivers/e1000e
lrwxrwxrwx 1 root root 0 Oct 21 11:35
/sys/class/net/mon.wlan0/device/driver -> ../../../../bus/pci/drivers/ath9k
lrwxrwxrwx 1 root root 0 Oct 21 11:35 /sys/class/net/wlan0/device/driver
-> ../../../../bus/pci/drivers/ath9k
root@gw:~# grep . /sys/class/net/*/features
/sys/class/net/eth0/features:0x0
/sys/class/net/eth1/features:0x803
/sys/class/net/eth2/features:0x1109a9
/sys/class/net/lo/features:0x13865
/sys/class/net/mon.wlan0/features:0x2000
/sys/class/net/wlan0/features:0x2000

For the record, my laptop has "atl1c" gigabit ethernet card, the
internet server is a xen domU on unknown hardware, but there never was a
problem with either.

So, is it hardware? I guess memory could be faulty, but that would
manifest itself sooner and also on other places I guess.

I believe there is a problem either in those drivers (sharing
something?), or in some algorithm.
I switched SSH MACs from
"hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160"
to "hmac-ripemd160" and that doesn't work either. B0rked openssl? B0rked
openssh?

It happens more often on large (4GB) files, but also saw it on a bunch
of 1KB files now, restarting makes it going again...

I'm obviously going to run a memtest once I get home, but for now I
believe this is a software fault.

Jan