Ethernet Products
Determine ramifications of Intel® Ethernet products and technologies
5374 Discussions

Frequent Hardware Unit Hangs with I218-V (Linux, e1000e Module)

cloudthomas
Beginner
464 Views

Hello,

we are experiencing frequent hardware unit hangs in with I218-V (rev 05) NICs on Linux systems running Ubuntu 22.04.4 LTS with a pretty recent Kernel version: 5.15.0-101-generic #111-Ubuntu SMP Tue Mar 5 20:16:58 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

The I218 is the active interface in an active-backup bonding with a X552/X557-AT configured as the backup interface, which has been set to 1 GBit/s maximum link speed. The backup interface doesn't experience any problems at all.

Any ideas?

 

The kernel log shows:

Jun 17 00:02:04 node01 kernel: [106404.978062] e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:
Jun 17 00:02:04 node01 kernel: [106404.978062] TDH <0>
Jun 17 00:02:04 node01 kernel: [106404.978062] TDT <ea>
Jun 17 00:02:04 node01 kernel: [106404.978062] next_to_use <ea>
Jun 17 00:02:04 node01 kernel: [106404.978062] next_to_clean <0>
Jun 17 00:02:04 node01 kernel: [106404.978062] buffer_info[next_to_clean]:
Jun 17 00:02:04 node01 kernel: [106404.978062] time_stamp <10194b4f0>
Jun 17 00:02:04 node01 kernel: [106404.978062] next_to_watch <0>
Jun 17 00:02:04 node01 kernel: [106404.978062] jiffies <10194bd18>
Jun 17 00:02:04 node01 kernel: [106404.978062] next_to_watch.status <0>
Jun 17 00:02:04 node01 kernel: [106404.978062] MAC Status <40080083>
Jun 17 00:02:04 node01 kernel: [106404.978062] PHY Status <796d>
Jun 17 00:02:04 node01 kernel: [106404.978062] PHY 1000BASE-T Status <3800>
Jun 17 00:02:04 node01 kernel: [106404.978062] PHY Extended Status <3000>
Jun 17 00:02:04 node01 kernel: [106404.978062] PCI Status <10>
Jun 17 00:02:06 node01 kernel: [106406.962170] e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:
Jun 17 00:02:06 node01 kernel: [106406.962170] TDH <0>
Jun 17 00:02:06 node01 kernel: [106406.962170] TDT <ea>
Jun 17 00:02:06 node01 kernel: [106406.962170] next_to_use <ea>
Jun 17 00:02:06 node01 kernel: [106406.962170] next_to_clean <0>
Jun 17 00:02:06 node01 kernel: [106406.962170] buffer_info[next_to_clean]:
Jun 17 00:02:06 node01 kernel: [106406.962170] time_stamp <10194b4f0>
Jun 17 00:02:06 node01 kernel: [106406.962170] next_to_watch <0>
Jun 17 00:02:06 node01 kernel: [106406.962170] jiffies <10194bf08>
Jun 17 00:02:06 node01 kernel: [106406.962170] next_to_watch.status <0>
Jun 17 00:02:06 node01 kernel: [106406.962170] MAC Status <40080083>
Jun 17 00:02:06 node01 kernel: [106406.962170] PHY Status <796d>
Jun 17 00:02:06 node01 kernel: [106406.962170] PHY 1000BASE-T Status <3800>
Jun 17 00:02:06 node01 kernel: [106406.962170] PHY Extended Status <3000>
Jun 17 00:02:06 node01 kernel: [106406.962170] PCI Status <10>
Jun 17 00:02:06 node01 kernel: [106407.185683] e1000e 0000:00:19.0 eno1: Reset adapter unexpectedly
Jun 17 00:02:07 node01 kernel: [106407.449791] bondbb: (slave eno1): link status definitely down, disabling slave
Jun 17 00:02:07 node01 kernel: [106407.449803] bondbb: (slave enp7s0f0): making interface the new active one
Jun 17 00:02:07 node01 kernel: [106407.449808] device eno1 left promiscuous mode
Jun 17 00:02:07 node01 kernel: [106407.449893] device enp7s0f0 entered promiscuous mode

Labels (1)
0 Kudos
0 Replies
Reply