From: "Gabor Z. Papp" <gzp@papp.hu>
To: linux-kernel@vger.kernel.org
Cc: jgarzik@pobox.com
Subject: 2.4.24 eth0: TX underrun, threshold adjusted.
Date: Sat, 10 Jan 2004 09:02:27 +0100 [thread overview]
Message-ID: <x665fkb59o@gzp> (raw)
Replacing 2.4.23 with 2.4.24 went without any error I noticed.
After 8h uptime I have connected the first nfsroot client.
In the server host klog got 12 "eth0: TX underrun, threshold adjusted."
messages while the client started to mount the dirs.
etherwake uses obsolete (PF_INET,SOCK_PACKET)
IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:07:e9:12:49:34:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=20 ID=0 PROTO=UDP SPT=68 DPT=67 LEN=556 IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:07:e9:12:49:34:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=20 ID=1 PROTO=UDP SPT=68 DPT=67 LEN=556
IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:07:e9:12:49:34:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=60 ID=0 PROTO=UDP SPT=68 DPT=67 LEN=556 IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:07:e9:12:49:34:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=68 DPT=67 LEN=556
IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:07:e9:12:49:34:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=68 DPT=67 LEN=556
eth0: TX underrun, threshold adjusted.
[10 times]
eth0: TX underrun, threshold adjusted.
Host bridge: Intel Corp. 82845G/GL [Brookdale-G]
P4-2.4GHz 512MB RAM
eth0 intel eepro100
eth1 onboard b44 (for pppoe)
Never noticed such problem with 2.4.23 or earlier kernels.
Just noticed, on the nfsroot client getting the same message 4 times.
There is only one eepro100:
Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 10)
Subsystem: Intel Corp.: Unknown device 0070
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 14000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at f7800000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at d000 [size=64]
Region 2: Memory at f7000000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
Additional debug infos available on request.
next reply other threads:[~2004-01-10 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 8:02 Gabor Z. Papp [this message]
2004-01-10 14:56 ` 2.4.24 eth0: TX underrun, threshold adjusted Martin Josefsson
2004-01-10 17:39 ` Gabor Z. Papp
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=x665fkb59o@gzp \
--to=gzp@papp.hu \
--cc=jgarzik@pobox.com \
--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