All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Krogh <jesper@krogh.cc>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: e1000: eth2: e1000_clean_tx_irq: Detected Tx Unit Hang
Date: Sun, 05 Apr 2009 10:11:42 +0200	[thread overview]
Message-ID: <49D867BE.1010700@krogh.cc> (raw)

I have a 2.6.27.20 system in production, the e1000 drivers seem pretty 
"noisy" allthough everything appears to work excellent.

dmesg here: http://krogh.cc/~jesper/dmesg-ko-2.6.27.20.txt

[476197.380486] e1000: eth3: e1000_clean_tx_irq: Detected Tx Unit Hang
[476197.380488]   Tx Queue             <0>
[476197.380489]   TDH                  <c>
[476197.380490]   TDT                  <63>
[476197.380490]   next_to_use          <63>
[476197.380491]   next_to_clean        <b>
[476197.380491] buffer_info[next_to_clean]
[476197.380492]   time_stamp           <10717579a>
[476197.380492]   next_to_watch        <f>
[476197.380493]   jiffies              <107175a3e>
[476197.380494]   next_to_watch.status <0>

The system has been up for 14 days but the dmesg-buffer has allready 
overflown with these.

Configuratoin is a 4 x 1GbitE bond all with Intel NICs

06:01.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
Controller (Copper) (rev 03)
06:01.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
Controller (Copper) (rev 03)
06:02.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
Controller (Copper) (rev 03)
06:02.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
Controller (Copper) (rev 03)



-- 
Jesper

             reply	other threads:[~2009-04-05  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05  8:11 Jesper Krogh [this message]
2009-04-06 17:36 ` e1000: eth2: e1000_clean_tx_irq: Detected Tx Unit Hang Brandeburg, Jesse
2009-04-06 18:53   ` Jesper Krogh

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=49D867BE.1010700@krogh.cc \
    --to=jesper@krogh.cc \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.