Created attachment 283527 [details]
Created attachment 283529 [details]
Created attachment 283531 [details]
Thanks for the logs.
Per , this issue doesn't occur on the out-of-tree e1000e driver, presumably from Intel:
Same behavior can be observed on both mainline kernel and on your
dev-queue branch. OTOH, the same issue can’t be observed on
Is there any plan to close the gap between upstream and out-of-tree
So somebody needs to figure out the difference between the two and get the fix upstream. This is just a heads-up that the solution is there, waiting to be discovered, so there's no need to try to debug it from scratch.
Fixed by e5e9a2ecfe780975820e157b922edee715710b66 e1000e: add workaround for possible stalled packet