From: Brad Campbell <brad@seme.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: via-rhine problem on EPIAV-1Ghz 2.4.21-pre6
Date: Wed, 02 Apr 2003 12:10:00 +0800 [thread overview]
Message-ID: <3E8A6298.8060600@seme.com.au> (raw)
In-Reply-To: <20030401185258.GC3736@arthur.home>
Erik Mouw wrote:
>
> Here's the 2.5 driver backported to 2.4.20, it solved my timeout
> problems (with thanks to Roger Luethi). Don't know if the "noapic"
> option is still necessary, but it won't hurt anyway.
>
>
> Erik
Yup, Roger sent me the file directly (Many thanks Roger!)
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.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
eth0: Tx descriptor write-back race.
--
Brad....
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2003-04-02 4:02 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 [this message]
2003-04-02 7:01 ` Roger Luethi
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=3E8A6298.8060600@seme.com.au \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox