This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failing network adapter

Hi,

I am having issues with my internal network adapter (eth0 - Intel 82579LM Gbit adapter).

Test case:

  1. Start a speedtest.net session
    1. This will start normally and the fail
  2. The network adapter will stop responding to ping
  3. Found the following in the kernel log:
    1.  
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] TDH <51>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] TDT <87>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] next_to_use <87>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] next_to_clean <51>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] buffer_info[next_to_clean]:
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] time_stamp <1000db0b2>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] next_to_watch <51>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] jiffies <1000db2a9>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] next_to_watch.status <0>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] MAC Status <80083>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] PHY Status <796d>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] PHY 1000BASE-T Status <3c00>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] PHY Extended Status <3000>
      2017:07:27-14:53:59 mail kernel: [ 3890.619865] PCI Status <10>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] TDH <51>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] TDT <87>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] next_to_use <87>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] next_to_clean <51>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] buffer_info[next_to_clean]:
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] time_stamp <1000db0b2>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] next_to_watch <51>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] jiffies <1000db49d>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] next_to_watch.status <0>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] MAC Status <80083>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] PHY Status <796d>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] PHY 1000BASE-T Status <3c00>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] PHY Extended Status <3000>
      2017:07:27-14:54:01 mail kernel: [ 3892.619675] PCI Status <10>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] TDH <51>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] TDT <87>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] next_to_use <87>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] next_to_clean <51>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] buffer_info[next_to_clean]:
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] time_stamp <1000db0b2>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] next_to_watch <51>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] jiffies <1000db691>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] next_to_watch.status <0>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] MAC Status <80083>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] PHY Status <796d>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] PHY 1000BASE-T Status <3c00>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] PHY Extended Status <3000>
      2017:07:27-14:54:03 mail kernel: [ 3894.619777] PCI Status <10>
      2017:07:27-14:54:04 mail kernel: [ 3895.622743] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly
      2017:07:27-14:54:08 mail kernel: [ 3899.583770] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

Any ideas, thoughts or suggestions? Defect hardware or some weird software condition?



This thread was automatically locked due to age.
  • Hi Claus,

    I checked #7.8 in Rulz and found that the 82574 is not good, but I don't know about your adapter.  Is this a new installation, one that you recently upgraded or ???

    Cheers - Bob

  • Hi,

    Well I saw that myself, but since it isn't the same I hoped to be safe.

    The system is newly built on a more powerful pc that should be able to handle my faster internet lines of 300  Mbit. The other adapters are a dual port pcie  ( Intel 82571EB Gbit adapter).

    The configuration was restored from my old system.

    I will try to change the adapter. Thanks