From: Ronny Haryanto <ronny-linux@haryan.to>
To: linux-kernel@vger.kernel.org
Subject: tulip driver broken in 2.4.4?
Date: Tue, 1 May 2001 11:05:12 -0500 [thread overview]
Message-ID: <20010501110512.A8148@haryan.to> (raw)
Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes.
The log says:
Apr 30 10:30:59 fluke kernel: NETDEV WATCHDOG: eth1: transmit timed out
Apr 30 10:30:59 fluke kernel: eth1: Transmit timed out, status fc664010, CSR12 00000000, resetting...
Apr 30 10:31:07 fluke kernel: NETDEV WATCHDOG: eth1: transmit timed out
Apr 30 10:31:07 fluke kernel: eth1: Transmit timed out, status fc664010, CSR12 00000000, resetting...
... and so on repeatedly ...
I had to ifdown-ifup cycle to re-enable it but it's dead again after 5
minutes with the same problem. The card is LinkSys LNE100TX v4.1. It is
currently working fine with 2.2.18. If there's any other info that is needed
please let me know.
Ronny
next reply other threads:[~2001-05-01 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 16:05 Ronny Haryanto [this message]
2001-05-01 16:16 ` tulip driver broken in 2.4.4? Jeff Garzik
2001-05-01 17:57 ` Ronny Haryanto
2001-05-01 18:14 ` 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=20010501110512.A8148@haryan.to \
--to=ronny-linux@haryan.to \
--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