public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Langås" <tlan@stud.ntnu.no>
To: J Sloan <jjs@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel EEPro 100 with kernel drivers
Date: Wed, 31 Oct 2001 09:01:25 +0100	[thread overview]
Message-ID: <20011031090125.B10751@stud.ntnu.no> (raw)
In-Reply-To: <20011029021339.B23985@stud.ntnu.no> <3BDCD06E.8AF8FF69@pobox.com>
In-Reply-To: <3BDCD06E.8AF8FF69@pobox.com>; from jjs@pobox.com on Sun, Oct 28, 2001 at 07:43:42PM -0800

J Sloan:
> We found that using the intel e100 driver
> instead of the eepro100 eliminates these
> errors - YMMV of course -

I've now tried the Intel driver, no help, still get the NFS timeouts (the
intel driver doesn't output anything to dmesg, so it's no way of telling if
the same things occur as in the eepro100 stock-kernel driver). 

This is how I do the test:

NFS share a filesystem
NFS mount it on another box (not running intel e100 nic)
Start bonnie++ on the box that has mounted the nfs share

After 10-20mins, the first NFS timeout comes (which means the card is out of
resources, and "halts" for a bit). When the card becomes out of resources,
it seems like it uses a few minutes before it comes online again, no wonder
why, tho.

Has anyone got any suggestions on how to start tracking down, and maybe
fixing this problem?  Or, is this a hardware error?  Or maybe a firmware
error?  Should I start contacting Dell and tell them that's there's a
possible error in their PowerEdge 2550-series?

-- 
Thomas

  reply	other threads:[~2001-10-31  8:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29  1:13 Intel EEPro 100 with kernel drivers Thomas Langås
2001-10-29  1:57 ` Jim Hull
2001-10-29  3:43 ` J Sloan
2001-10-31  8:01   ` Thomas Langås [this message]
2001-10-31 15:22     ` Andrey Savochkin
2001-10-31 15:52       ` Kirill Ratkin
2001-11-01  7:55       ` Thomas Langås
2001-11-01  9:47         ` Andrey Savochkin
2001-11-01 10:00           ` Thomas Langås
2001-10-31 18:10     ` Juergen Hasch
2001-11-01  8:03       ` Thomas Langås
2001-11-01  8:48         ` Juergen Hasch
2001-11-01  9:06           ` Thomas Langås
2001-11-01  9:43             ` Juergen Hasch
2001-11-01 11:11       ` Andrey Savochkin
2001-11-01 12:00         ` Thomas Langås
2001-11-01 12:15           ` Juergen Hasch
2001-11-01 13:39       ` Henning P. Schmiedehausen
2001-10-29 10:44 ` Alan Cox
2001-10-29 11:40   ` Michael Rozhavsky
2001-10-29 11:49     ` Alan Cox
2001-10-29 11:45       ` Michael Rozhavsky
2001-10-29 13:52   ` Thomas Langås
2001-10-30  8:36 ` Jarmo Järvenpää
2001-10-30  8:54   ` Dead2
2001-10-30  9:02     ` Jarmo Järvenpää

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=20011031090125.B10751@stud.ntnu.no \
    --to=tlan@stud.ntnu.no \
    --cc=jjs@pobox.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