From: Lukasz Trabinski <lukasz@lt.wsisiz.edu.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: test-10 tulip "eth0 timed out" (smp, heavy IDE use)
Date: Tue, 28 Nov 2000 10:52:46 +0100 [thread overview]
Message-ID: <200011280952.eAS9qkb01700@lt.wsisiz.edu.pl> (raw)
In-Reply-To: <20001128042134.A1041@twoey>
In article <20001128042134.A1041@twoey> you wrote:
> Using 2.4-test10 I got a series of timeout errors on my tulip network
> card (Linksys LNE version 4, 00:0d.0 Ethernet controller: Bridgecom,
> Inc: Unknown device 0985 (rev 11)). Networking then completely stopped
> working. Restarting the interface with ifconfig fixed the problem.
> I am using an SMP kernel, compiled with gcc 2.95.2 on an ABit BP6 (dual
> celeron 500s, 128mb, PIIX4 using DMA).
> [log extract]
> Nov 28 04:04:52 twoey kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Nov 28 04:04:52 twoey kernel: eth0: Transmit timed out, status fc664010,
> CSR12 00000000, resetting...
I have the same problem with SMSC EPIC/100 83c170 Ethernet controller:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout using MII device, Tx status 0003.
eth0: Restarting the EPIC chip, Rx 4568454/4568454 Tx 6262613/6262623.
eth0: epic_restart() done, cmd status 000a, ctl 0512 interrupt 240000.
kernel 2.4.0-test11
--
*[ Łukasz Trąbiński ]*
SysAdmin @wsisiz.edu.pl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-28 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 4:21 Toby Jaffey
2000-11-28 4:38 ` Andre Hedrick
2000-11-28 9:52 ` Lukasz Trabinski [this message]
2000-11-28 16:33 ` Francois romieu
2000-11-28 16:22 ` Lukasz Trabinski
2000-11-28 5:48 Jacob Luna Lundberg
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=200011280952.eAS9qkb01700@lt.wsisiz.edu.pl \
--to=lukasz@lt.wsisiz.edu.pl \
--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®