From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: tulip-users@lists.sourceforge.net,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: 21041 transmit timed out
Date: Fri, 13 Jun 2003 12:55:54 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.21.0306131251420.11546-100000@vervain.sonytel.be> (raw)
In-Reply-To: <Pine.LNX.4.44.0305111148460.19415-100000@callisto>
On Sun, 11 May 2003, Geert Uytterhoeven wrote:
> On Sun, 20 Apr 2003, Geert Uytterhoeven wrote:
> > Under heavy network activity (e.g. downloading ISOs), my Tulip card (D-Link
> > DE-530+ with DECchip 21041) still goes down with 2.4.20.
> >
> > Suddenly I start getting messages of the form:
> > | NETDEV WATCHDOG: eth0: transmit timed out
> > | eth0: 21041 transmit timed out, status fc660000, CSR12 000051c8, CSR13 ffffef01, CSR14 ffffffff, resetting...
> > | eth0: 21143 100baseTx sensed media.
> >
> > and the network no longer works. Sometimes it automatically recovers after a
> > while (without printing additional messages), but usually I need to do a manual
> > ifconfig down/up sequence to revive the network.
[...]
> It still takes a few minutes to recover, but at least it recovers
> automatically, and within the TCP timeout limit, so no connections are lost.
>
> I tested this by transfering several gigabytes across the network using netcat,
> and it always recovered without needing manual intervention.
>
> So I suggest the following patch:
>
> --- linux-2.4.20/drivers/net/tulip/tulip_core.c.orig Tue Oct 29 18:41:48 2002
> +++ linux-2.4.20/drivers/net/tulip/tulip_core.c Sun May 11 11:31:29 2003
> @@ -575,7 +575,7 @@
> dev->if_port = 2 - dev->if_port;
> } else
> dev->if_port = 0;
> - else
> + else if (dev->if_port != 0 || (csr12 & 0x0004) != 0)
> dev->if_port = 1;
> tulip_select_media(dev, 0);
> }
>
> Any comments?
I can confirm that this patch fixed my problem. Sometimes transmission still
times out, but the driver recovers automatically within 3 minutes. The machine
has been up for more than one month.
Still no comments?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2003-06-13 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 11:12 21041 transmit timed out Geert Uytterhoeven
2003-05-11 9:53 ` Geert Uytterhoeven
2003-06-13 10:55 ` Geert Uytterhoeven [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-29 14:37 Geert Uytterhoeven
[not found] <Pine.LNX.4.05.10012201318030.1508-100000@callisto.of.borg>
2001-03-12 13:19 ` Geert Uytterhoeven
2001-03-12 17:34 ` Geert Uytterhoeven
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=Pine.GSO.4.21.0306131251420.11546-100000@vervain.sonytel.be \
--to=geert@linux-m68k.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tulip-users@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).