public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Joseph Cheek <joseph@cheek.com>,
	linux-kernel@vger.kernel.org, Donald Becker <becker@scyld.com>
Subject: Re: test12: eth0 trasmit timed out after one hour uptime
Date: Sat, 16 Dec 2000 01:50:59 +1100	[thread overview]
Message-ID: <3A3A2FD3.88FAA330@uow.edu.au> (raw)
In-Reply-To: <3A37FFC9.19F05305@cheek.com>, <3A37FFC9.19F05305@cheek.com>; from joseph@cheek.com on Wed, Dec 13, 2000 at 03:01:29PM -0800 <20001215161926.D829@nightmaster.csn.tu-chemnitz.de>

Ingo Oeser wrote:
> 
> On Wed, Dec 13, 2000 at 03:01:29PM -0800, Joseph Cheek wrote:
> > Dec 13 14:51:46 sanfrancisco kernel: NETDEV WATCHDOG: eth0: transmit
> > timed out
> ...
> I have this too since testX-Kernels are released.
> 
> I use a "3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24)"
> (actually two of them ;-)).
> 
> > after reboot it works fine again [i'll give it an hour...]  test12-pre8
> > and before worked fine.  any ideas?
> 
> This seems to be code to debug these timeouts.
> 
> It didn't cause any harm AFICS, but I CC'ed the Author of this
> code anyway.

Ingo,

Donald wrote just about all the Linux netdrivers, but he
now concentrates upon the drivers which he maintains at
http://www.scyld.com.  Other people try to help out with the
drivers which come from kernel.org.

This particular problem does still occur occasionally.

It's way too infrequent to pin down.  It can certainly
be caused by a very high collision rate on a hubbed LAN.
If that were the only cause I would take all the diagnostics
out, because that's simply ethernet.

Other possible causes are lost interrupts in the kernel
or hardware, cabling problems, power supply problems or,
indeed, a driver bug.

If you are able to reproduce this then I'd be very interested
in working with you on it.  First step is to read the final
section of Documentation/networking/vortex.txt, then send
me a long email.

Thanks.
-
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/

      reply	other threads:[~2000-12-15 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13 23:01 test12: eth0 trasmit timed out after one hour uptime Joseph Cheek
2000-12-13 23:11 ` Mohammad A. Haque
2000-12-13 23:13   ` Joseph Cheek
2000-12-13 23:25     ` Mohammad A. Haque
2000-12-14  2:03       ` James Stevenson
2000-12-14  2:37     ` Michael Peddemors
2000-12-14  1:41       ` Joseph Cheek
2000-12-14  2:34 ` Michael Peddemors
2000-12-15 15:19 ` Ingo Oeser
2000-12-15 14:50   ` Andrew Morton [this message]

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=3A3A2FD3.88FAA330@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=becker@scyld.com \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=joseph@cheek.com \
    --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