* tulip driver broken in 2.4.4?
@ 2001-05-01 16:05 Ronny Haryanto
2001-05-01 16:16 ` Jeff Garzik
0 siblings, 1 reply; 4+ messages in thread
From: Ronny Haryanto @ 2001-05-01 16:05 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: tulip driver broken in 2.4.4?
2001-05-01 16:05 tulip driver broken in 2.4.4? Ronny Haryanto
@ 2001-05-01 16:16 ` Jeff Garzik
2001-05-01 17:57 ` Ronny Haryanto
0 siblings, 1 reply; 4+ messages in thread
From: Jeff Garzik @ 2001-05-01 16:16 UTC (permalink / raw)
To: Ronny Haryanto; +Cc: linux-kernel
Ronny Haryanto wrote:
>
> Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes.
Does 2.4.3 work for you?
--
Jeff Garzik | Game called on account of naked chick
Building 1024 |
MandrakeSoft |
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: tulip driver broken in 2.4.4?
2001-05-01 16:16 ` Jeff Garzik
@ 2001-05-01 17:57 ` Ronny Haryanto
2001-05-01 18:14 ` Jacob Luna Lundberg
0 siblings, 1 reply; 4+ messages in thread
From: Ronny Haryanto @ 2001-05-01 17:57 UTC (permalink / raw)
To: Jeff Garzik; +Cc: linux-kernel
On 01-May-2001, Jeff Garzik wrote:
> Ronny Haryanto wrote:
> >
> > Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes.
>
> Does 2.4.3 work for you?
Yes. I just tried 2.4.3, and it works fine. So it looks like there's a bug
introduced between 2.4.3 and 2.4.4. Too bad I can't use 2.4.3; I need 2.4.4
due to the VIA chipset bug. Is there any other info that I could provide
from here to help debugging?
Ronny
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: tulip driver broken in 2.4.4?
2001-05-01 17:57 ` Ronny Haryanto
@ 2001-05-01 18:14 ` Jacob Luna Lundberg
0 siblings, 0 replies; 4+ messages in thread
From: Jacob Luna Lundberg @ 2001-05-01 18:14 UTC (permalink / raw)
To: Ronny Haryanto; +Cc: Jeff Garzik, linux-kernel
Well, I guess I should chip in here with the rather amusing fact that
2.4.4 is the first kernel *not* to do this to me... ;-)
I am, of course, glad to help out testing stuff if needed. My card is
also a LinkSys LNE100TX v4.1, which the tulip driver identifies as an
ADMtek Comet rev 17 (although somebody told me it's really a Centaur).
-Jacob
On Tue, 1 May 2001, Ronny Haryanto wrote:
> On 01-May-2001, Jeff Garzik wrote:
> > Ronny Haryanto wrote:
> > >
> > > Just tried 2.4.4 yesterday and found that my eth1 was dead after 5 minutes.
> >
> > Does 2.4.3 work for you?
>
> Yes. I just tried 2.4.3, and it works fine. So it looks like there's a bug
> introduced between 2.4.3 and 2.4.4. Too bad I can't use 2.4.3; I need 2.4.4
> due to the VIA chipset bug. Is there any other info that I could provide
> from here to help debugging?
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-05-01 18:14 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-05-01 16:05 tulip driver broken in 2.4.4? Ronny Haryanto
2001-05-01 16:16 ` Jeff Garzik
2001-05-01 17:57 ` Ronny Haryanto
2001-05-01 18:14 ` Jacob Luna Lundberg
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.