r8169 driver received packet corruption

[Gregory P Smith]

After upgrading an i386 ubuntu server from 8.10 to 9.04 I started getting these errors any time I tried to transfer a useful amount of data -to- the system via ssh:

Received disconnect from X.X.X.X: 2: Corrupted MAC on input.
lost connection

The problem only went away after I used the following command to disable rx-checksumming on the ethernet interface:

sudo ethtool -K eth1 rx off

I have also seen corruption in .deb packages downloaded during apt-get upgrade which I -had- been assuming was a problem in the packages on the update mirror my system happened to contact but which would be more consistent with this being a problem with the r8169 driver locally.

Linux dealer 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:48:10 UTC 2009 i686 GNU/Linux

/proc/version_signature: Ubuntu 2.6.28-11.42-server

lspci -vnvn of the ethernet controller:

02:09.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: I/O ports at a000 [size=256]
        Region 1: Memory at e0201000 (32-bit, non-prefetchable) [size=256]
        [virtual] Expansion ROM at 40000000 [disabled] [size=64K]
        Capabilities: <access denied>
        Kernel driver in use: r8169
        Kernel modules: r8169

Interestingly, despite using that ethernet interface the kernel module has a use count of 0 as seen in lsmod.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=27a338e2-8d16-42e6-8228-a32b2a65de8d
MachineType: Transmeta Corporation efficeon Pasofino Reference Platform
Package: linux-image-2.6.28-11-server 2.6.28-11.42
ProcCmdLine: root=/dev/mapper/hostname-root ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcVersionSignature: Ubuntu 2.6.28-11.42-server
SourcePackage: linux

[Jeremy Foshee (jeremyfoshee)]

Hi Gregory,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 384584

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Gregory P Smith (gpshead)]

Unfortunately I no longer have a r8169 PCI card in a machine that I
can test this on to see if recent kernels still have the issue.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]