From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.17.13: eth2: TX underrun, threshold adjusted.
Date: Mon, 25 Dec 2006 19:38:29 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612251933120.12104@p34.internal.lan> (raw)
I am using a dual port Intel NIC on an A-Bit IC7-G; any reason why I get
these?
[4298634.444000] eth2: TX underrun, threshold adjusted.
[4299146.645000] eth2: TX underrun, threshold adjusted.
[4299146.645000] eth2: TX underrun, threshold adjusted.
[4299147.437000] eth2: TX underrun, threshold adjusted.
[4299147.454000] eth2: TX underrun, threshold adjusted.
[4299149.442000] eth2: TX underrun, threshold adjusted.
[4299155.247000] eth2: TX underrun, threshold adjusted.
[4299159.271000] eth2: TX underrun, threshold adjusted.
[4299165.291000] eth2: TX underrun, threshold adjusted.
I see in the mailing list archives this error was most prevalent in 2.4.
However, it also shows up in 2.6:
http://lkml.org/lkml/2005/6/7/49
http://lkml.org/lkml/2004/5/19/20
http://www.ussg.iu.edu/hypermail/linux/kernel/0506.0/1512.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0405.2/0535.html
I am using the e100 driver, MAC addr commented out with **.
[4294675.208000] eth2: 0000:04:04.0, 00:**:**:**:**:**, IRQ 18.
[4294675.209000] Receiver lock-up bug exists -- enabling work-around.
[4294675.209000] Board assembly 711269-003, Physical connectors present:
RJ45
[4294675.209000] Primary interface chip i82555 PHY #1.
[4294675.209000] General self-test: passed.
[4294675.209000] Serial sub-system self-test: passed.
[4294675.209000] Internal registers self-test: passed.
[4294675.209000] ROM checksum self-test: passed (0x24c9f043).
[4294675.211000] Receiver lock-up workaround activated.
[4294675.211000] ACPI: PCI Interrupt 0000:04:05.0[A] -> GSI 23 (level,
low) -> IRQ 17
[4294675.221000] eth3: 0000:04:05.0, 00:**:**:**:**:**, IRQ 17.
[4294675.222000] Receiver lock-up bug exists -- enabling work-around.
[4294675.222000] Board assembly 711269-003, Physical connectors present:
RJ45
[4294675.222000] Primary interface chip i82555 PHY #1.
[4294675.222000] General self-test: passed.
[4294675.222000] Serial sub-system self-test: passed.
[4294675.222000] Internal registers self-test: passed.
[4294675.222000] ROM checksum self-test: passed (0x24c9f043).
[4294675.222000] Receiver lock-up workaround activated.
I have other boards and I do not recall seeing the message about the
Receiver lock-up bug, could this be part of the reason for the TX
underrun?
Does it matter which PCI slot I place this card in? It is currently right
next to a PCI 3com 509 (thinnet).
$ cat /proc/interrupts
CPU0 CPU1
0: 6938534 0 IO-APIC-edge timer
1: 205 0 IO-APIC-edge i8042
4: 75106 0 IO-APIC-edge serial
8: 1 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
12: 9106 0 IO-APIC-edge i8042
14: 157428 2 IO-APIC-edge ide0
15: 63295 2 IO-APIC-edge ide1
16: 1224358 0 IO-APIC-level eth0
17: 171170 0 IO-APIC-level eth2, eth3
18: 4017 0 IO-APIC-level eth1
19: 68950 0 IO-APIC-level ide2, ide3
20: 6090 0 IO-APIC-level Intel ICH5
NMI: 0 0
LOC: 6938508 6938562
ERR: 0
MIS: 0
Would increasing the txqueuelen fix this issue? Or should I replace the
NIC to get rid of these messages?
Any help would be much appreciated.
Thanks,
Justin.
next reply other threads:[~2006-12-26 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 0:38 Justin Piszcz [this message]
[not found] <fa.8x7CSG3Vz8/rASmsmG0lScp7gAc@ifi.uio.no>
2006-12-26 2:57 ` Robert Hancock
2006-12-26 12:57 ` Justin Piszcz
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=Pine.LNX.4.64.0612251933120.12104@p34.internal.lan \
--to=jpiszcz@lucidpixels.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
all inboxes | Powered by JetHome®