From: "Gabor Z. Papp" <gzp@papp.hu>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com,
Feldman@tux.rsn.bth.se, Scott <scott.feldman@intel.com>
Subject: Re: 2.4.24 eth0: TX underrun, threshold adjusted.
Date: Sat, 10 Jan 2004 18:39:21 +0100 [thread overview]
Message-ID: <x6oetb66uu@gzp> (raw)
In-Reply-To: 1073746559.752.44.camel@tux.rsn.bth.se
* Martin Josefsson <gandalf@wlug.westbo.se>:
| > eth0: TX underrun, threshold adjusted.
| > [10 times]
| > eth0: TX underrun, threshold adjusted.
|
| > eth0 intel eepro100
|
| I think you ran the eepro100 driver in 2.4.23 and now in 2.4.24 you are
| using the e100 driver, am I correct?
No, you aren't.
| This isn't really an error, it's an indicator that the pci-bus doesn't
| really keep up, then the NIC has to increase the threshold (it tries to
| start sending the packet out before it's fully transferred from main
| memory to the NIC, it hopes the rest of the packet will have been
Funny because I have changed the mobo/cpu/ram from P3 to P4. Maybe
its related to that change?
| This happens with the eepro100 driver as well but it doesn't tell you
| about it, it just increases the threshold and goes on.
I'm using Becker's eepro100, I'm sure.
| I hope this helps to explain this message.
Thanks.
next prev parent reply other threads:[~2004-01-10 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 8:02 2.4.24 eth0: TX underrun, threshold adjusted Gabor Z. Papp
2004-01-10 14:56 ` Martin Josefsson
2004-01-10 17:39 ` Gabor Z. Papp [this message]
2004-01-10 17:53 ` Martin Josefsson
2004-01-10 17:58 ` Gabor Z. Papp
2004-01-10 18:23 ` Martin Josefsson
2004-01-10 19:07 ` Gabor Z. Papp
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=x6oetb66uu@gzp \
--to=gzp@papp.hu \
--cc=Feldman@tux.rsn.bth.se \
--cc=gandalf@wlug.westbo.se \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.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.