From: Roger Luethi <rl@hellgate.ch>
To: Brad Campbell <brad@seme.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: via-rhine problem on EPIAV-1Ghz 2.4.21-pre6
Date: Wed, 2 Apr 2003 09:01:15 +0200 [thread overview]
Message-ID: <20030402070115.GA2667@k3.hellgate.ch> (raw)
In-Reply-To: <3E8A6298.8060600@seme.com.au>
On Wed, 02 Apr 2003 12:10:00 +0800, Brad Campbell wrote:
> It solved the timeout propblems, I do get these however.
>
> Not that they cause any hiccups in throughput.
>
> eth0: Tx descriptor write-back race.
> eth0: Tx descriptor write-back race.
> eth0: Tx descriptor write-back race.
> eth0: Transmit error, Tx status 00008800.
> eth0: Transmitter underrun, Tx threshold now 40.
> eth0: Tx descriptor write-back race.
> eth0: Transmit error, Tx status 00008800.
> eth0: Transmitter underrun, Tx threshold now 60.
> eth0: Tx descriptor write-back race.
These are only informational messages on errors handled by the new code.
You won't see them at the default debug level. I made a few observations
leading me to believe that the number of those errors can be further
reduced, but that will take quite a bit of work.
And there is still a Tx pause of up to a couple of seconds (net watchdog
kicking in) on every GB or so, especially under high load.
Roger
prev parent reply other threads:[~2003-04-02 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 2:32 via-rhine problem on EPIAV-1Ghz 2.4.21-pre6 Brad Campbell
2003-04-01 2:50 ` Brad Campbell
2003-04-01 4:27 ` Jeff Garzik
2003-04-01 4:35 ` Brad Campbell
2003-04-01 6:38 ` Josh McKinney
2003-04-01 14:05 ` Henrik Persson
2003-04-01 18:52 ` Erik Mouw
2003-04-02 4:10 ` Brad Campbell
2003-04-02 7:01 ` Roger Luethi [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=20030402070115.GA2667@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=brad@seme.com.au \
--cc=linux-kernel@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.