e1000_clean_tx_irq: Detected Tx Unit Hang

I have to add that this problem occurs with a AthlonXP box with a VIA KT600 chipset. (I tried also another e1000 card with the same result)
But, when just retrying it with an old PIII with Intel 815 chipset this problem didn't occur.

This is a known bug that hasnt been solved yet with the e1000 drivers. As a workaround we advise people to turn off tso using
ethtool for the device. That should remove the tx hangs.

Text copy from the e1000 website:

82573(V/L/E) TX Unit Hang messages

--------------------------------------------------------------------------------

Several NIC's with the 82573 chipset display "TX unit hang" messages during normal operation with the linux e1000 driver. The issue appears both with TSO enabled and disabled, and is caused by a power management function that is enabled in the EEPROM. Early releases of the chipsets to vendors had the EEPROM bit that enabled the feature. After the issue was discovered newer adapters were released with the feature disabled in the EEPROM.

See : http://e1000.sourceforge.net/wiki/index.php/Issues#82573.28V.2FL.2FE.29_TX_Unit_Hang_messages
Run the script fixeep-82573-dspd.sh in order to fix the problem !

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Please note, there are multiple causes of this symptom.

As posted by Dominique Gallot above, if you have an adapter (on board or standalone) based on the Intel 82573 chipset, this issue may be caused by an improper setting in the adapter's EEPROM. It will occur regardless of TSO setting, and even in the new 2.6.27 kernel shipping with Intrepid Ibex. The following document from Intel has additional information, under the section "82573(V/L/E) TX Unit Hang Messages".
http://downloadmirror.intel.com/9180/eng/README.txt

The script to automatically detect and permanently fix this issue can be downloaded at:
http://e1000.sourceforge.net/files/fixeep-82573-dspd.sh

Note: The link provided in the comment above is now broken.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug report was marked as Confirmed a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

I am experiencing that problem after I've upgraded the machine's RAM...

I got the following error message:
[193931.010165] e1000: eth1: e1000_clean_tx_irq: Detected Tx Unit Hang
[193931.010169] Tx Queue <0>
[193931.010171] TDH <4>
[193931.010173] TDT <4>
[193931.010175] next_to_use <4>
[193931.010177] next_to_clean <0>
[193931.010179] buffer_info[next_to_clean]
[193931.010181] time_stamp <10127736b>
[193931.010183] next_to_watch <0>
[193931.010185] jiffies <10127751d>
[193931.010187] next_to_watch.status <0>

Workaround which worked for me:
sudo rmmod e1000 && sudo modprobe e1000 TxDescriptors=128 RxDescriptors=128

System Details:
Ubuntu 10.10 amd64
Linux 2.6.35-22-server
e1000-8.0.23
Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)

Please file new bugs if you feel you are affected by a similar issue.

~JFo

This bug is still present, you can find this for the solution http://serverfault.com/q/193114/18822

similar bug here: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/890552
the EPROM fix they talk about at serverfault did not work for me (this is e1000 driver, not e1000e)

Christian Leber, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]