All of lore.kernel.org
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Phil Oester <kernel@linuxace.com>
Cc: netdev@vger.kernel.org
Subject: Re: e1000 TX unit hang
Date: Wed, 05 Jul 2006 10:13:34 -0700	[thread overview]
Message-ID: <44ABF33E.2020200@intel.com> (raw)
In-Reply-To: <20060705163332.GA17915@linuxace.com>

Phil Oester wrote:
> I saw this error (once) in 2.6.13 a few weeks ago:
> 
> Jun 23 15:19:01 X kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
> Jun 23 15:19:01 X kernel:   TDH                  <7e>
> Jun 23 15:19:01 X kernel:   TDT                  <7f>
> Jun 23 15:19:01 X kernel:   next_to_use          <7f>
> Jun 23 15:19:01 X kernel:   next_to_clean        <7e>
> Jun 23 15:19:01 X kernel: buffer_info[next_to_clean]
> Jun 23 15:19:01 X kernel:   dma                  <16ef9012>
> Jun 23 15:19:01 X kernel:   time_stamp           <423845db>
> Jun 23 15:19:01 X kernel:   next_to_watch        <7e>
> Jun 23 15:19:01 X kernel:   jiffies              <423845db>
> Jun 23 15:19:01 X kernel:   next_to_watch.status <0>
> 
> so upgraded to 2.6.17 and got a slew of them today - shown below.
> E1000 maintainers: any ideas?

The issue is known and worked on, unfortunately no more information yet.

We're tracking the issue and stuff (debug patches, etc) over here (at 
e1000.sf.net):

http://sourceforge.net/tracker/index.php?func=detail&aid=1463045&group_id=42302&atid=447449

For now, try to see if turning off tso using ethtool helps.


Cheers,

Auke

      reply	other threads:[~2006-07-05 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05 16:33 e1000 TX unit hang Phil Oester
2006-07-05 17:13 ` Auke Kok [this message]

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=44ABF33E.2020200@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=kernel@linuxace.com \
    --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.