mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Savochkin <saw@saw.sw.com.sg>
To: "Thomas LangЕs" <tlan@stud.ntnu.no>
Cc: linux-kernel@vger.kernel.org, J Sloan <jjs@pobox.com>
Subject: Re: Intel EEPro 100 with kernel drivers
Date: Wed, 31 Oct 2001 18:22:13 +0300	[thread overview]
Message-ID: <20011031182212.A21776@castle.nmd.msu.ru> (raw)
In-Reply-To: <20011029021339.B23985@stud.ntnu.no> <3BDCD06E.8AF8FF69@pobox.com> <20011031090125.B10751@stud.ntnu.no>
In-Reply-To: =?koi8-r?Q?=3C20011031090125=2EB10751=40stud=2Entnu=2Eno=3E=3B_from_=22T?= =?koi8-r?Q?homas_Lang=E5s=22_on_Wed=2C_Oct_31=2C_2001_at_09:01:25AM?=

Hi,

On Wed, Oct 31, 2001 at 09:01:25AM +0100, Thomas LangЕs wrote:
> 
> 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

Well, with eepro100 the start may be the following:
1. When the card stalls, start ping from that host.
This way you ensure that you have something in transmit ring.
If it's transmitting that stalls, you'll get a message from netdev watchdog.
2. If ping works, then your problem appear to be pure NFS one, i.e. inability
of NFS to recover from network operation disruption.
3. If ping is able to transmit, but not receive (you may check it by
tcpdump), then we have a receiver problem.
We'll think what to do then.

4. In any case, running eepro100-diag from scyld.com at the moment of the
stall may give some useful information.
5. In any case, searching eepro100 mailing list archive on scyld.com is a
good idea, you may learn what other people observe/do.

	Andrey

> error?  Should I start contacting Dell and tell them that's there's a
> possible error in their PowerEdge 2550-series?

  reply	other threads:[~2001-10-31 15:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29  1:13 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
2001-10-31 15:22     ` Andrey Savochkin [this message]
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=20011031182212.A21776@castle.nmd.msu.ru \
    --to=saw@saw.sw.com.sg \
    --cc=jjs@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tlan@stud.ntnu.no \
    /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®