Intel NUC - Network Unit Hang

Issues related to hardware problems
Post Reply
toffe
Posts: 4
Joined: 2019/02/01 10:59:39

Intel NUC - Network Unit Hang

Post by toffe » 2019/02/01 11:53:26

Hello.

I've discovered a problem after upgrading to 3.10.0-957.1.3 kernel. We have a DHCP server up and running on our Intel NUC any a Wireless AP connected.

As soon as I connect with my PC it works perfectly. But if i start streaming NETFLIX i do get a "eno1: Detected Hardware Unit Hang"

Code: Select all

[  626.296220] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <18>
  TDT                  <28>
  next_to_use          <28>
  next_to_clean        <13>
buffer_info[next_to_clean]:
  time_stamp           <10004f258>
  next_to_watch        <18>
  jiffies              <10004fc30>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <3800>
PHY Extended Status    <3000>
PCI Status             <10>
***** **********************************
** MULTIPLE messages like above snipped away for shorter log
***** *********************************'
[ 1994.278250] e1000e 0000:00:1f.6 eno1: Reset adapter unexpectedly
[ 1998.243373] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
My discoveries is that the following apps on my phone makes this error occur:
Netflix, NRK (Norwegian TV), Ookla speedtest


Youtube works perfectly fine, doing iPerf3 to another DHCP unit on the network gets about 700-800 throughoutput both ways (on cable). Also local speedtest works superb. But if i use a ethernet connected Chromecast device and start netflix it crashes. Youtube still works .

So seems like heavy load as a "client" on this DHCP server makes it die. But not youtube :P

Any idea on what might be "f...d"? Happend during the latest firmware upgrade.

I can do

toffe
Posts: 4
Joined: 2019/02/01 10:59:39

Re: Intel NUC - Network Unit Hang

Post by toffe » 2019/02/01 14:26:52

An update.

As long as we have TSO disabled on all 3 interfaces (main interface, and both vlan interfaces which dhcp is on). Then it works flawless.

So "ethtool -K eno1 tso off" (then the same for both vlan interfaces)

But still wondering what have changed that introduced this in the newer kernel?

Post Reply