I realize this is closed. Just adding a few notes from my own experience since the discussion here has been useful to me. In my case the error shows up in running "ssh -Y" to a second system, and then starting "dosemu" on the remote system (which will tunnel to my desktop). The remote system has an Intel e1000e PCI-E NIC. The local system has a Marvell PCI-E card.
"sudo ethtool -K eth1 rx off tx off" on the local (Marvell) box avoids the error, but leaves me wondering if I'm just tolerating corruption. Does OpenSSH have its own error correction protocol for safety here? The remote box had had some problems that seemed associated with a different NIC (an old LinkSys tulip), but that had been a second card on a different interface, seemingly fixed by swapping in an Intel card. The remote system has tested find in memtest86 and other stress tests. But memtest86 doesn't hit 100% of RAM. Makes me wonder if there's RAM going bad in the range assigned to PCI cards that's simply outside of the range memtest86 can see - and that's certainly outside the range that can be tested while booted into Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/60764 Title: Large file transfer gives error: Corrupted MAC on input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/60764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
