Summary: | if_em: "Off by 8" error in network streams under -CURRENT as of roughly Feb 1 | ||
---|---|---|---|
Product: | Base System | Reporter: | Jeffrey Baitis <jeff> |
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed Not A Bug | ||
Severity: | Affects Only Me | CC: | erj, grahamperrin, jeff, jeffrey.e.pieper, kbowling, sbruno, shurd |
Priority: | --- | Keywords: | IntelNetworking, iflib, regression |
Version: | CURRENT | ||
Hardware: | amd64 | ||
OS: | Any | ||
URL: | https://github.com/trueos/trueos-core/issues/327 |
Description
Jeffrey Baitis
2017-02-22 05:43:28 UTC
Upon further inspection, the WORKING kernel was built on Wed Jan 18: $ uname -a FreeBSD raid.baitis.home 12.0-CURRENT FreeBSD 12.0-CURRENT #18 4f888bf(drm-next): Wed Jan 18 14:31:26 UTC 2017 root@gauntlet:/usr/obj/usr/src/sys/GENERIC amd64 So, changes in -CURRENT made after Jan 18 and before Feb 1 were likely to have precipitated this problem. Have you tried a non-i217 em device, or turning off TSO and/or TXCSUM? Getting random bits inserted sounds like it might be the hardware trying to do an offload, but doing some part of it incorrectly. I don't really see anything that affects i217 devices in the commits between Jan 18 and Feb 1, except for this: https://svnweb.freebsd.org/base/head/sys/dev/e1000/e1000_ich8lan.c?r1=312426&r2=312427& Want to try reverting the hunk starting at line 1720? I think lpt is i217/i218. I've attempted the following: * Disabling the rx and txcsum has no effect on the problem * Disabling the hwtso has no effect on the problem * I am unable to disable vlanhwcsum as the command seems to have no effect * Removing the virtual box network drivers has no effect I will next attempt to cherry-pick It turns out that this bug is either due to an interaction between my wireless router and my FreeBSD system, or was masked by TrueOS' default network configuration that may have undone some of my own customization. More likely is that after upgrading the wireless router from OpenWrt to the latest version of LEDE, I was no longer able to reproduce this issue. I'm therefore closing this and very much enjoying 12.0-CURRENT. |