From: Sven Dowideit <svenud@ozemail.com.au>
To: linux-kernel@vger.kernel.org
Subject: kernel: NETDEV WATCHDOG: eth0: transmit timed out
Date: Mon, 23 Feb 2004 00:38:00 +1100 [thread overview]
Message-ID: <1077457080.1208.17.camel@sven> (raw)
I have an IBM thinkpad T21 that has a 3Com ethernet card that has not
been working in a long while (with ACPI turned on).
Recently (the last 2-3 releases or so) it has also been getting the
following messages (until i remember to to an ifconfgi eth0 down)
Feb 23 00:22:00 sven kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 23 00:22:35 sven last message repeated 3 times
Feb 23 00:23:35 sven last message repeated 5 times
Feb 23 00:24:35 sven last message repeated 5 times
Feb 23 00:25:35 sven last message repeated 5 times
Feb 23 00:26:00 sven last message repeated 2 times
the other weird thing, is that my computer pauses every few seconds, for
a second, and it seems like this symptom goes away after the ifconfig
down.
any ideas?
cheers
Sven
------------------------------------------------------------------
00:03.0 Ethernet controller: 3Com Corporation 3c556B Hurricane CardBus
(rev 20)
Subsystem: 3Com Corporation: Unknown device 6356
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 1800 [size=256]
[virtual] Memory at e8101400 (32-bit, non-prefetchable)
[size=128]
[virtual] Memory at e8101000 (32-bit, non-prefetchable)
[size=128]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [50] Power Management version 2
eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:21 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x1800
next reply other threads:[~2004-02-22 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 13:38 Sven Dowideit [this message]
2004-02-22 15:50 ` kernel: NETDEV WATCHDOG: eth0: transmit timed out sven dowideit
2004-02-24 1:09 ` Jeff Garzik
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=1077457080.1208.17.camel@sven \
--to=svenud@ozemail.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