Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SMSC9514 eth0: hw csum failure - NOT Pi3b+ #2712

Closed
6by9 opened this issue Oct 11, 2018 · 2 comments
Closed

SMSC9514 eth0: hw csum failure - NOT Pi3b+ #2712

6by9 opened this issue Oct 11, 2018 · 2 comments

Comments

@6by9
Copy link
Contributor

6by9 commented Oct 11, 2018

Raised to avoid confusion with #2659.

Report from @ricardosalveti of seeing eth0: hw csum failure messages from the kernel on 3B (ie SMSC9514) with 4.18 kernel.

lso started to see this issue lately, but I'm using the 3 model B, which uses smsc95xx.
This is with the latest 4.18 kernel tree (rpi patches + stable).

#2659 (comment)
#2659 (comment)
are the relevant comments.

New issue raised to avoid confusing lan78xx issues vs smsc95xx issues.

@6by9
Copy link
Contributor Author

6by9 commented Oct 11, 2018

Looking at my local network, the service generating this issue was iceccd (running on ubuntu 16.04).
After disabling iceccd on the ubuntu machine I'm not not getting the hw csum errors anymore.
Logs from tcpdump:

21:12:03.771275 IP (tos 0x0, ttl 64, id 57986, offset 0, flags [DF], proto UDP (17), length 29)
    192.168.1.44.58909 > 192.168.1.255.8765: UDP, length 1
E.....@.@......,......"=.       S. ............../..

Unclear if this is really an issue at the sender or if an issue at the receiver side.

A UDP packet of length 29 would fall into the category of the UDP checksum being in the last 4 words of the packet, however the patch that had been posted was for checksum offload failure on transmit, not receive.
I'll see if I can find the relevant reference docs for SMSC9514 as to the details on that offload issue.

6by9 added a commit to 6by9/linux that referenced this issue Oct 15, 2018
This reverts commit 88078d9.

Various people have been reporting seeing "eth0: hw csum failure"
and callstacks dumped in the kernel log on 4.18, and since 4.14.71,
on both SMSC9514 and LAN7800 adapters.
This commit appears to be the reason, but potentially due to an
issue further down the stack. Revert whilst investigating the
trigger.

raspberrypi#2713
raspberrypi#2659
raspberrypi#2712

Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.org>
6by9 added a commit to 6by9/linux that referenced this issue Oct 15, 2018
This reverts commit 6bf32cd.

Various people have been reporting seeing "eth0: hw csum failure"
and callstacks dumped in the kernel log on 4.18, and since 4.14.71,
on both SMSC9514 and LAN7800 adapters.
This commit appears to be the reason, but potentially due to an
issue further down the stack. Revert whilst investigating the
trigger.

raspberrypi#2713
raspberrypi#2659
raspberrypi#2712

Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.org>
@6by9
Copy link
Contributor Author

6by9 commented Oct 15, 2018

Closing as this does seem to be a common issue in the main IP core and not a driver related thing.

There is a check in the SMSC9514 driver that s/w checks buffers under 45 bytes, so I'd expect this to be trapped there.

@6by9 6by9 closed this as completed Oct 15, 2018
pelwell pushed a commit that referenced this issue Oct 15, 2018
This reverts commit 6bf32cd.

Various people have been reporting seeing "eth0: hw csum failure"
and callstacks dumped in the kernel log on 4.18, and since 4.14.71,
on both SMSC9514 and LAN7800 adapters.
This commit appears to be the reason, but potentially due to an
issue further down the stack. Revert whilst investigating the
trigger.

#2713
#2659
#2712

Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.org>
ahmedradaideh pushed a commit to ahmedradaideh/Pi-Kernel that referenced this issue Oct 15, 2018
This reverts commit 6bf32cd.

Various people have been reporting seeing "eth0: hw csum failure"
and callstacks dumped in the kernel log on 4.18, and since 4.14.71,
on both SMSC9514 and LAN7800 adapters.
This commit appears to be the reason, but potentially due to an
issue further down the stack. Revert whilst investigating the
trigger.

raspberrypi/linux#2713
raspberrypi/linux#2659
raspberrypi/linux#2712

Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.org>
Signed-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant