From: Stefan Kuhne <stefan.kuhne@gmx.net>
To: xen-devel@lists.xensource.com
Subject: [pv_ops] e1000e: "Detected Tx Unit Hang"
Date: Thu, 20 May 2010 23:45:59 +0200 [thread overview]
Message-ID: <4BF5AD97.4000907@access.denied> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 216 bytes --]
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
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-05-20 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 21:45 Stefan Kuhne [this message]
2010-05-20 22:18 ` [pv_ops] e1000e: "Detected Tx Unit Hang" Jeremy Fitzhardinge
2010-05-20 22:58 ` Stefan Kuhne
2010-05-20 23:01 ` Jeremy Fitzhardinge
2010-05-20 23:21 ` AW: " Heiko Wundram
2010-05-23 0:16 ` Stefan Kuhne
2010-05-20 23:22 ` Stefan Kuhne
2010-05-22 15:32 ` Thomas Goirand
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=4BF5AD97.4000907@access.denied \
--to=stefan.kuhne@gmx.net \
--cc=xen-devel@lists.xensource.com \
/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).