public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: NETDEV timeout on tulips [was: Re: 2.4.1-test10]
Date: Tue, 23 Jan 2001 11:13:48 +0000	[thread overview]
Message-ID: <3A6D676C.2F6D5236@linux.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101221711560.1309-100000@penguin.transmeta.com> <3A6CF5B7.57DEDA11@linux.com> <3A6D2D54.619AFA7E@mandrakesoft.com> <3A6D616F.63EB34A6@linux.com> <20010123125636.I25659@mea-ext.zmailer.org>

Matti Aarnio wrote:

> On Tue, Jan 23, 2001 at 10:48:16AM +0000, David Ford wrote:
> > The three cardbus cards are slightly different in numerous ways.  For
> > them they normally fault with an APM event, an eject/insert cycle via
> > software will reset hem and a link down/up won't fix it.  For the PCI
> > cards most times a link down/up cycle will fix them.  It's a 2.4 v.s. 2.2
> > issue, the 2.2 kernels aren't exhibiting this error.
>
>         I see that with my AT2800TX cardbus card as well.
>         (Using Tulip driver, no less.)
>
> > The PCI cards are hard to get into this state, sometimes they'll run
> > millions of packets for months on end before they'll burp.  Sometimes
> > it'll happen three times a night.  The amount of traffic doesn't seem
> > to matter, nor does the type of traffic.
>
>         Sounds like timing issue.

Hmm, should we class these as two similar but different bugs?  I suspect they
are both timing but there is another stimulus operating differently.

-d

--
  There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
  The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum



-
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:[~2001-01-23 11:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-23  1:13 2.4.1-test10 Linus Torvalds
2001-01-23  3:08 ` 2.4.1-test10 David Ford
2001-01-23  5:04   ` 2.4.1-test10 Derek Wildstar
2001-01-23  7:05   ` 2.4.1-test10 Jeff Garzik
2001-01-23 10:42     ` 2.4.1-test10 Ben Ford
2001-01-23 10:48     ` NETDEV timeout on tulips [was: Re: 2.4.1-test10] David Ford
2001-01-23 10:56       ` Matti Aarnio
2001-01-23 11:13         ` David Ford [this message]
2001-01-23 12:25           ` Matti Aarnio
2001-01-23 12:36             ` David Ford
2001-01-23 17:57       ` Jeff Garzik
2001-01-23  4:37 ` 2.4.1-test10 Marcelo Tosatti
2001-01-23 19:03   ` 2.4.1-test10 Linus Torvalds
2001-01-23 19:27     ` 2.4.1-test10 Andre Hedrick
2001-01-23 17:48       ` 2.4.1-test10 Marcelo Tosatti
2001-01-23 19:38       ` Under 2.4.0 I can mount same partition twice Dan Graham
2001-01-23 20:13         ` Andreas Dilger

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=3A6D676C.2F6D5236@linux.com \
    --to=david@linux.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.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