From: Bernd Schubert <bernd-schubert@gmx.de>
To: netdev@vger.kernel.org
Subject: e1000: Detected Tx Unit Hang
Date: Fri, 15 Feb 2008 23:52:36 +0100 [thread overview]
Message-ID: <fp553k$9r8$1@ger.gmane.org> (raw)
Hello,
I can't login to one of our servers and just got this in an ipmi sol
session:
[18169.209181] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
[18169.209183] Tx Queue <0>
[18169.209184] TDH <e3>
[18169.209185] TDT <e3>
[18169.209186] next_to_use <e3>
[18169.209187] next_to_clean <bd>
[18169.209188] buffer_info[next_to_clean]
[18169.209189] time_stamp <10043e4d2>
[18169.209190] next_to_watch <be>
[18169.209191] jiffies <10043e6f6>
[18169.209192] next_to_watch.status <1>
[18169.256978] e1000: eth2: e1000_clean_tx_irq: Detected Tx Unit Hang
[18169.256979] Tx Queue <0>
[18169.256980] TDH <de>
[18169.256982] TDT <de>
[18169.256983] next_to_use <de>
[18169.256984] next_to_clean <bc>
[18169.256985] buffer_info[next_to_clean]
[18169.256986] time_stamp <10043e511>
[18169.256987] next_to_watch <bd>
[18169.256988] jiffies <10043e701>
[18169.256989] next_to_watch.status <1>
This is with 2.6.22.18. Is there any chance to recover the system? For some
reasons I would prefer not to reboot now.
Thanks,
Bernd
next reply other threads:[~2008-02-15 22:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 22:52 Bernd Schubert [this message]
2008-02-15 23:29 ` e1000: Detected Tx Unit Hang Kok, Auke
2008-02-16 0:26 ` Bernd Schubert
2008-02-19 16:47 ` Kok, Auke
-- strict thread matches above, loose matches on Subject: below --
2006-09-02 14:39 e1000 " Paul Aviles
2006-09-03 17:45 ` Jesse Brandeburg
2006-09-03 23:37 ` Paul Aviles
2006-09-05 16:09 ` Jesse Brandeburg
2006-09-06 1:33 ` Paul Aviles
2006-09-11 4:03 ` Paul Aviles
2006-09-17 2:05 ` Paul Aviles
[not found] <000f01c6ce49$affd37e0$3224050a@avilespaxp>
2006-09-02 5:45 ` Auke Kok
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fp553k$9r8$1@ger.gmane.org' \
--to=bernd-schubert@gmx.de \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).