From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Juergen Hasch <Hasch@t-online.de>
Cc: linux-kernel@vger.kernel.org, "Thomas LangЕs" <tlan@stud.ntnu.no>,
"J Sloan" <jjs@pobox.com>
Subject: Re: Intel EEPro 100 with kernel drivers
Date: Thu, 1 Nov 2001 14:11:11 +0300 [thread overview]
Message-ID: <20011101141111.A27180@castle.nmd.msu.ru> (raw)
In-Reply-To: <20011029021339.B23985@stud.ntnu.no> <3BDCD06E.8AF8FF69@pobox.com> <20011031090125.B10751@stud.ntnu.no> <15yzpC-26N6dEC@fwd04.sul.t-online.com>
In-Reply-To: <15yzpC-26N6dEC@fwd04.sul.t-online.com>; from "Juergen Hasch" on Wed, Oct 31, 2001 at 07:10:49PM
On Wed, Oct 31, 2001 at 07:10:49PM +0100, Juergen Hasch wrote:
>
> I had some trouble with an Intel STL 2 board and the onboard EEPRO100.
> Samba worked OK but it always got stuck on NFS transfers.
>
> There was a bug in the older BMC firmware, so the eepro100 detected
> some NFS frames as "TCO" packets.
> (http://support.intel.com/support/motherboards/server/ta_353-1.htm)
>
> If you use the e100 driver, you can look at
> /proc/net/PRO_LAN_ADAPTERS/eth0.info
> If the "Tx_TCO_Packets" entry isn't zero after NFS times out,
> this may be your problem.
> With the eepro100 driver you will only see overruns with ifconfig.
It should be Rx_TCO_Packets, not Tx.
The problem described in Intel's advisory is related to incorrect processing
of receiving packets.
Andrey
next prev parent reply other threads:[~2001-11-01 11:04 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
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 [this message]
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=20011101141111.A27180@castle.nmd.msu.ru \
--to=saw@saw.sw.com.sg \
--cc=Hasch@t-online.de \
--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®