From: "Thomas Langås" <tlan@stud.ntnu.no>
To: Andrey Savochkin <saw@saw.sw.com.sg>
Cc: linux-kernel@vger.kernel.org, J Sloan <jjs@pobox.com>
Subject: Re: Intel EEPro 100 with kernel drivers
Date: Thu, 1 Nov 2001 08:55:23 +0100 [thread overview]
Message-ID: <20011101085523.D2102@stud.ntnu.no> (raw)
In-Reply-To: <20011029021339.B23985@stud.ntnu.no> <3BDCD06E.8AF8FF69@pobox.com> <20011031090125.B10751@stud.ntnu.no> <20011031182212.A21776@castle.nmd.msu.ru>
In-Reply-To: <20011031182212.A21776@castle.nmd.msu.ru>; from saw@saw.sw.com.sg on Wed, Oct 31, 2001 at 06:22:13PM +0300
Andrey Savochkin:
> 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.
>From the server, or the client? I've already tried pinging from the server
when I get the error-message in dmesg, but it's unresponsive to anything.
And, I mean anything, network-wise. There seems to be a timeout somewhere,
because after some time, everything resumes back to normal again.
> 4. In any case, running eepro100-diag from scyld.com at the moment of the
> stall may give some useful information.
OK, I'll do the test again, and run the eepro100-diag. Any special options
you want me to specify?
> 5. In any case, searching eepro100 mailing list archive on scyld.com is a
> good idea, you may learn what other people observe/do.
OK, I'll search... :)
--
Thomas
next prev parent reply other threads:[~2001-11-01 7:56 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
2001-10-31 15:22 ` Andrey Savochkin
2001-10-31 15:52 ` Kirill Ratkin
2001-11-01 7:55 ` Thomas Langås [this message]
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=20011101085523.D2102@stud.ntnu.no \
--to=tlan@stud.ntnu.no \
--cc=jjs@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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