All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Leber <christian@leber.de>
To: xen-devel@lists.xensource.com
Subject: Re: x86_64 eth0 e1000_clean_tx_irq tx hang
Date: Thu, 9 Feb 2006 16:02:58 +0100	[thread overview]
Message-ID: <20060209150258.GA19671@core> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D40A609@liverpoolst.ad.cl.cam.ac.uk>

On Wed, Feb 08, 2006 at 11:36:06PM -0000, Ian Pratt wrote:

> For this bug it might actually be helpful to start collecting
> information about the hardware it's observed on.
> 
> For us, the bug is hard to repro, despite us having tried on several
> different machines (2 and 4 way SMP, Opteron and Xeon, tg3 and e1000
> NICs).

It's not on Xen, but i get something similar with scp:
(and this Tx Unit Hang seems to be a seldom problem)
(2.6.15)

[4294726.019000] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
[4294726.019000] TDH <cb>
[4294726.019000] TDT <cb>
[4294726.019000] next_to_use <cb>
[4294726.019000] next_to_clean <df>
[4294726.019000] buffer_info[next_to_clean]
[4294726.019000] dma <1aa25cce>
[4294726.019000] time_stamp <fffc40e7>
[4294726.019000] next_to_watch <df>
[4294726.019000] jiffies <fffc5183>
[4294726.019000] next_to_watch.status <0>

That happens on AthlonXP+ViaKT600 but not on Intel PIII with Intel 815
chipset.
https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/30476


Christian Leber

-- 
  "Omnis enim res, quae dando non deficit, dum habetur et non datur,
   nondum habetur, quomodo habenda est."       (Aurelius Augustinus)
  Translation: <http://gnuhh.org/work/fsf-europe/augustinus.html>

  parent reply	other threads:[~2006-02-09 15:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 23:36 x86_64 eth0 e1000_clean_tx_irq tx hang Ian Pratt
2006-02-09  1:27 ` Chris Wright
2006-02-09 15:02 ` Christian Leber [this message]
2006-02-09 17:24   ` Chris Wright
2006-02-09 23:29     ` Christian Leber
  -- strict thread matches above, loose matches on Subject: below --
2006-02-09 23:55 Kamble, Nitin A
2006-02-10 11:20 ` Keir Fraser
2006-02-10 11:33   ` Muli Ben-Yehuda
2006-02-16  3:07 ` Chris Wright
2006-02-16 11:36   ` Keir Fraser
2006-02-16 11:45     ` Jan Beulich
2006-02-16 13:54       ` Keir Fraser
2006-02-16 13:10   ` Guillaume Thouvenin
2006-02-16 13:55     ` Keir Fraser
2006-02-17  7:26       ` Guillaume Thouvenin
2006-02-09  2:29 Ian Pratt
2006-02-09  1:50 Ian Pratt
2006-02-09  1:59 ` Chris Wright
2006-02-09  2:29 ` Chris Wright
2006-02-09  1:29 Ian Pratt
2006-02-09  1:38 ` Chris Wright
2006-02-09  1:49 ` Chris Wright
2006-02-08 20:01 Ian Pratt
2006-02-08 20:11 ` Chris Wright
2006-02-08 15:06 Adam Wendt
2006-02-07 20:47 Chris Wright

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=20060209150258.GA19671@core \
    --to=christian@leber.de \
    --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 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.