search for: next_to_us

...network/interfaces. Any attempt to use the NIC (eth2), such as a ping command, results in the following errors: root@gateway1:~# [ 98.816957] e1000: eth2: e1000_clean_tx_irq: Detected Tx Unit Hang [ 98.816963] Tx Queue <0> [ 98.816965] TDH <3> [ 98.816967] TDT <3> [ 98.816969] next_to_use <3> [ 98.816971] next_to_clean <0> [ 98.816973] buffer_info[next_to_clean] [ 98.816975] time_stamp <ffff398a> [ 98.816977] next_to_watch <0> [ 98.816979] jiffies <ffff3b88> [ 98.816981] next_to_watch.status <0> [ 100.816231] e1000: eth2: e1000_clean_tx_irq: Dete...

Hello, my server has massive problems with my NIC. I got: "Detected Tx Unit Hang". At the moment I use 2.6.31 from Jeremy, does anyone know if it''s fixed in 2.6.32 or newer tree? Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...0] Receiver Error (First) This spams to the console continuously until hard booting. - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB igb 0000:82:00.0: Detected Tx Unit Hang Tx Queue <1> TDH <43> TDT <50> next_to_use <50> next_to_clean <43> buffer_info[next_to_clean] time_stamp <12e6bc0b6> next_to_watch <ffff880006aa7440> jiffies <12e6bc8dc> desc.status <1c8210> This spams to the console continuously until hard boot...

...0] Receiver Error (First) This spams to the console continuously until hard booting. - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB igb 0000:82:00.0: Detected Tx Unit Hang Tx Queue <1> TDH <43> TDT <50> next_to_use <50> next_to_clean <43> buffer_info[next_to_clean] time_stamp <12e6bc0b6> next_to_watch <ffff880006aa7440> jiffies <12e6bc8dc> desc.status <1c8210> This spams to the console continuously until hard boot...

...spams to the console continuously until hard booting. > > - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB > > igb 0000:82:00.0: Detected Tx Unit Hang > Tx Queue <1> > TDH <43> > TDT <50> > next_to_use <50> > next_to_clean <43> > buffer_info[next_to_clean] > time_stamp <12e6bc0b6> next_to_watch <ffff880006aa7440> > jiffies <12e6bc8dc> > desc.status <1c8210> > > This spams to the c...

...:10.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0037 address=0x7b657064 flags=0x0000] > [ 5963.353429] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang > Tx Queue <0> > TDH, TDT <93>, <9d> > next_to_use <9d> > next_to_clean <93> > tx_buffer_info[next_to_clean] > time_stamp <10019e800> > jiffies <10019ec80> > ... > > I retested on v6.5 vanilla (gues...

...:10.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0037 address=0x7b657064 flags=0x0000] > [ 5963.353429] ixgbe 0000:03:00.0 enp3s0: Detected Tx Unit Hang > Tx Queue <0> > TDH, TDT <93>, <9d> > next_to_use <9d> > next_to_clean <93> > tx_buffer_info[next_to_clean] > time_stamp <10019e800> > jiffies <10019ec80> > ... > > I retested on v6.5 vanilla (gues...

...sly until hard booting. >> >> - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB >> >> igb 0000:82:00.0: Detected Tx Unit Hang >> Tx Queue <1> >> TDH <43> >> TDT <50> >> next_to_use <50> >> next_to_clean <43> >> buffer_info[next_to_clean] >> time_stamp <12e6bc0b6> next_to_watch <ffff880006aa7440> >> jiffies <12e6bc8dc> >> desc.status <1c8210> >> &...

...spams to the console continuously until hard booting. > > - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB > > igb 0000:82:00.0: Detected Tx Unit Hang > Tx Queue <1> > TDH <43> > TDT <50> > next_to_use <50> > next_to_clean <43> > buffer_info[next_to_clean] > time_stamp <12e6bc0b6> next_to_watch <ffff880006aa7440> > jiffies <12e6bc8dc> > desc.status <1c8210> > > This spams to the c...

...here? In our environment we're randomly seeing: Jan 17 23:40:14 xen01 kernel: ixgbe 0000:04:00.1 eth6: Detected Tx Unit Hang Jan 17 23:40:14 xen01 kernel: Tx Queue <0> Jan 17 23:40:14 xen01 kernel: TDH, TDT <9a>, <127> Jan 17 23:40:14 xen01 kernel: next_to_use <127> Jan 17 23:40:14 xen01 kernel: next_to_clean <98> Jan 17 23:40:14 xen01 kernel: ixgbe 0000:04:00.1 eth6: tx_buffer_info[next_to_clean] Jan 17 23:40:14 xen01 kernel: time_stamp <218443db3> Jan 17 23:40:14 xen01 kernel: jiffies <21...

On 01/27/2017 06:08 AM, Karel Hendrych wrote: > Have you tried to eliminate all power management features all over? I've been trying to find and disable all power management features but having relatively little luck with that solving the problems. Stabbing the the dark I've tried different ACPI settings, including completely disabling it, disabling CPU frequency scaling, and setting

...at's not encouraging... > Jan 17 23:40:14 xen01 kernel: ixgbe 0000:04:00.1 eth6: Detected Tx Unit > Hang > Jan 17 23:40:14 xen01 kernel: Tx Queue <0> > Jan 17 23:40:14 xen01 kernel: TDH, TDT <9a>, <127> > Jan 17 23:40:14 xen01 kernel: next_to_use <127> > Jan 17 23:40:14 xen01 kernel: next_to_clean <98> > Jan 17 23:40:14 xen01 kernel: ixgbe 0000:04:00.1 eth6: > tx_buffer_info[next_to_clean] > Jan 17 23:40:14 xen01 kernel: time_stamp <218443db3> > Jan 17 23:40:14 xen01 kernel: jif...