From: Stephen Clark <stephen.clark@earthlink.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: transmit timeout problem
Date: Mon, 29 Sep 2003 14:05:15 -0400 [thread overview]
Message-ID: <3F78745B.7000606@earthlink.net> (raw)
Help needed please,
In frequently I start getting the following:
Sep 29 10:32:49 joker kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 29 10:32:49 joker kernel: eth0: Transmit timed out, status fc1e4010,
CSR12 0
0000000, resetting...
Sep 29 10:32:57 joker kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 29 10:32:57 joker kernel: eth0: Transmit timed out, status fc1e4010,
CSR12 0
0000000, resetting...
Sep 29 10:33:05 joker kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 29 10:33:05 joker kernel: eth0: Transmit timed out, status fc1e4010,
CSR12 0
0000000, resetting...
Sep 29 10:33:13 joker kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 29 10:33:13 joker kernel: eth0: Transmit timed out, status fc1e4010,
CSR12 0
0000000, resetting...
Sep 29 10:33:21 joker kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 29 10:33:21 joker kernel: eth0: Transmit timed out, status fc1e4010,
CSR12 0
0000000, resetting...
Sep 29 10:33:29 joker kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 29 10:33:29 joker kernel: eth0: Transmit timed out, status fc1e4010,
CSR12 0
0000000, resetting...
This usally happens while I at work - so I have my wife restart my
system. I have two of these cards
and have seen it happen on both of them. Anybody have an idea on how to
fix this.
Below is the kernel version and info on the cards.
Sep 29 10:35:37 joker kernel: Linux version 2.4.20-20.9custom
(root@joker.seclar
k.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #3 Wed Sep
17 16:28:
06 EDT 2003
Sep 29 10:35:38 joker kernel: Linux Tulip driver version 0.9.15-pre12
(Aug 9, 20
02)
Sep 29 10:35:38 joker kernel: eth0: ADMtek Comet rev 17 at 0xb000,
00:04:5A:6D:D
8:CC, IRQ 5.
Sep 29 10:35:38 joker kernel: eth1: ADMtek Comet rev 17 at 0xb400,
00:04:5A:40:5
1:24, IRQ 11.
Thanks,
Steve
reply other threads:[~2003-09-29 18:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F78745B.7000606@earthlink.net \
--to=stephen.clark@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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