public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Caleb Epstein <cae@bklyn.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NETDEV WATCHDOG: eth0: transmit timed out
Date: Thu, 01 Mar 2001 23:01:44 +0000	[thread overview]
Message-ID: <3A9ED4D8.B3465722@uow.edu.au> (raw)
In-Reply-To: <20010301115938.A8178@tela.bklyn.org>

Caleb Epstein wrote:
> 
>         I am seeing the following error after my machine has been up
>         for a while.  My eth0 is connected to a switched, local
>         subnet.  There is not a lot of traffic on the interface, maybe
>         a few 100 Mbytes or so.  Taking the interface down and then up
>         again fixes the problem (until it happens again :)
> 
>         Here is the relevant section from my kernel log
> 
> Mar  1 10:48:44 tela kernel: NETDEV WATCHDOG: eth0: transmit timed out

My guess would be that the driver has decided there's no
link beat on the 10baseT interface and has flopped over
to using 10base2.  A fix for this exists in 2.4.2-ac5+,
in the zerocopy patch and in

	http://www.uow.edu.au/~andrewm/linux/3c59x.c-2.4.2-pre4.gz

but not in 2.4.2.

You'll need to use

	options 3c59x options=0

in /etc/modules.conf to pin the driver down to using a 
particular physical interface - disable autoselection.


So could you please upgrade the driver?  If problems
remain, please send me a report, as described in the
final section of Documentation/networking/vortex.txt.

Thanks.

-

  reply	other threads:[~2001-03-01 23:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01 16:59 NETDEV WATCHDOG: eth0: transmit timed out Caleb Epstein
2001-03-01 23:01 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-13  2:24 Darryl Miles
2000-12-28 11:26 Manfred
2000-12-28 11:36 ` David Ford
2000-12-29  0:30 ` idalton
2000-12-28 10:43 David Ford

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=3A9ED4D8.B3465722@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=cae@bklyn.org \
    --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