My Oracle Support Banner

OVM 3.3: Network Connection Lost with Error " ixgbe: Detected Tx Unit Hang" (Doc ID 2019641.1)

Last updated on AUGUST 20, 2018

Applies to:

Oracle VM - Version 3.3.1 to 3.3.3 [Release OVM33]
Linux x86-64

Symptoms

Oracle VM Server lost network connection on ixgbe network card. The following logs are visible:

Jun 4 06:39:22 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: Detected Tx Unit Hang
Jun 4 06:39:22 oserv1 kernel: Tx Queue <15>
Jun 4 06:39:22 oserv1 kernel: TDH, TDT <0>, <3>
Jun 4 06:39:22 oserv1 kernel: next_to_use <3>
Jun 4 06:39:22 oserv1 kernel: next_to_clean <0>
Jun 4 06:39:22 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: tx_buffer_info[next_to_clean]
Jun 4 06:39:22 oserv1 kernel: time_stamp <108178b10>
Jun 4 06:39:22 oserv1 kernel: jiffies <10817947f>
Jun 4 06:39:22 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: tx hang 2134 detected on queue 15, resetting adapter
Jun 4 06:39:22 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: Reset adapter
Jun 4 06:39:22 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 0 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 1 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 2 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 3 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 4 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 5 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 6 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 7 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 8 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 9 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 10 not cleared within the polling period
Jun 4 06:39:23 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 11 not cleared within the polling period
Jun 4 06:39:24 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 12 not cleared within the polling period
Jun 4 06:39:24 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 13 not cleared within the polling period
Jun 4 06:39:24 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 14 not cleared within the polling period
Jun 4 06:39:24 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 15 not cleared within the polling period
Jun 4 06:39:24 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 16 not cleared within the polling period
Jun 4 06:39:24 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 17 not cleared within the polling period
Jun 4 06:39:24 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 18 not cleared within the polling period
Jun 4 06:39:24 oserv1 kernel: ixgbe 0000:3a:00.0 eth0: RXDCTL.ENABLE on Rx queue 19 not cleared within the polling period
Jun 4 06:39:27 oserv1 kernel: bonding: bond0: link status down for active interface eth0, disabling it in 500 ms.
Jun 4 06:39:27 oserv1 kernel: ixgbe 0000:3a:00.0: master disable timed out

  

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.