public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [bug] NETDEV WATCHDOG: eth0: transmit timed out
Date: Thu, 02 Nov 2000 22:06:04 -0800	[thread overview]
Message-ID: <3A0255CC.BC1441AE@linux.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 629 bytes --]

Ok, something happend to the tulip driver in the recent testN kernels.
I haven't found a reason why it happens and I can't easily reproduce it
but what happens is noted on the subject line.

I have three machines now that do this.  It's unfixable until reboot (I
don't have these as modules).

I have a suspicion that it's triggered by large amounts of traffic.  My
brother feels he is able to trigger it repeatedly by doing big transfers
between a w9x box and a linux box.

-d

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."



[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 239 bytes --]

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
org:<img src="http://www.kalifornia.com/images/paradise.jpg">
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;-12480
fn:David Ford
end:vcard

             reply	other threads:[~2000-11-03  6:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-03  6:06 David Ford [this message]
     [not found] <Pine.LNX.4.21.0011022211350.30435-100000@anime.net>
2000-11-03  6:19 ` [bug] NETDEV WATCHDOG: eth0: transmit timed out David Ford
2000-11-03  6:20   ` Dan Hollis

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=3A0255CC.BC1441AE@linux.com \
    --to=david@linux.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