mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Fannin <jhf@rivenstone.net>
To: Anders Linden <anli@perceptive.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Network card timeouts
Date: Wed, 21 Nov 2001 15:48:36 -0500	[thread overview]
Message-ID: <20011121154836.A9016@gibraltar.rivenstone.net> (raw)
In-Reply-To: <71C83C8929F73A40BBD0C137232DD1972ED4@piff.i.perceptive.se>
In-Reply-To: <71C83C8929F73A40BBD0C137232DD1972ED4@piff.i.perceptive.se>

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

On Wed, Nov 21, 2001 at 07:16:23PM +0100, Anders Linden wrote:
> Symptom:
> Network cards that stops working if they are sent enough data.
> 
> The cards I have got problem with this far:
> Intel Etherexpress Pro 100+ (some kernels ago).
> Davicom Semiconductor, Inc. Ethernet 100/10

    I have seen very similar symptoms in two ISA eepro cards.  I found that,
if I kept a `ping` process running on the machine with an eepro installed,
the card would work okay, but somewhat slowly.  Otherwise it would just
hang, and had to be restarted to work again.

    (Note: this was a few weeks ago, and I'm not using any of my eepro cards
because of it anymore.  I haven't tried the new(ly maintained) driver.)

    It would be interesting to find that this is a more general problem; a
good bit of the reason why I've never reported it is because my eepro cards
are old and suspect themselves.


> 
> Occasion 1:
> The kernel version on the computers were 2.4.3. Every person in a single
> classroom had problem with Intel cards. They could not even fetch
> webpages before their consoles were spammed with a message like: network
> card timeout. All computers were Compaq. I dont know which hardware they
> had in addition to that. I have also had problems with Intel cards even
> after this occasion on other computers.
> 
> Occasion 2:
> The later card, Davicom, is probably not a well-known card, but
> nevertheless, it works like shit in Linux. I am using Redhat 7.1 and the
> kernel 2.4.2-2. If I send more than 10M to such a card in an interval of
> a second, it just quits working for 5 seconds. The card has no problems
> at all in other, third party operating systems, like Windows.
> 
> 
> Is it the newest kernels that has theese problems? The first occasion
> was exactly after a kernel 2.4.3 has been released, and people I talked
> to said that 2.4.2 and network cards were better friends.
> 
> 
> Thanks for your attension
> 
> /Anders Lind?n
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Joseph Fannin
jhf@rivenstone.net

"Bull in pure form is rare; there is usually some contamination by data."
    -- William Graves Perry Jr.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-11-21 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 18:16 Anders Linden
2001-11-21 20:48 ` Joseph Fannin [this message]
2001-11-21 23:24   ` Jeff Garzik
2001-11-22 13:12 ` Tobias Ringstrom
2001-11-26 20:26 ` Alan Cox
2001-11-26 20:32   ` Jeff Garzik

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=20011121154836.A9016@gibraltar.rivenstone.net \
    --to=jhf@rivenstone.net \
    --cc=anli@perceptive.se \
    --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

all inboxes | Powered by JetHome®