From: "Thomas Langås" <tlan@stud.ntnu.no>
To: Juergen Hasch <Hasch@t-online.de>
Cc: linux-kernel@vger.kernel.org, J Sloan <jjs@pobox.com>
Subject: Re: Intel EEPro 100 with kernel drivers
Date: Thu, 1 Nov 2001 10:06:37 +0100 [thread overview]
Message-ID: <20011101100637.B20259@stud.ntnu.no> (raw)
In-Reply-To: <20011029021339.B23985@stud.ntnu.no> <15yzpC-26N6dEC@fwd04.sul.t-online.com> <20011101090348.E2102@stud.ntnu.no> <15zDX1-1svMLQC@fwd03.sul.t-online.com>
In-Reply-To: <15zDX1-1svMLQC@fwd03.sul.t-online.com>; from Hasch@t-online.de on Thu, Nov 01, 2001 at 09:48:56AM +0100
Juergen Hasch:
> But your Rx_TCO_Packets counter is 1, so this may be related
> (I also got Rx overrun errors). It may be that your BMC receives the packet
> and simply chooses to ignore it because it is no valid server management
> packet.
> Could you make another test and take a look at the eth0.info ?
> I could reproduce the problem when copying a large file over NFS, but not
> when transferring it via ftp. Try this a few times.
> If you can reproduce you network card being stuck only when using NFS and
> having Rx_TCO_Packets > 0 after it is stuck, this is it.
> Then you either need tu upgrade your BMC firmware or add another network card,
> which doesn't eat NFS packets.
I'm testing now, however, running eepro100-diag gave me some interessting
output:
Sleep mode is enabled. This is not recommended. Under high load the card
may not respond to PCI requests, and thus cause a master abort.
How do I disable sleepmode? I've never even enabled it.
--
Thomas
next prev parent reply other threads:[~2001-11-01 9:07 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
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 [this message]
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=20011101100637.B20259@stud.ntnu.no \
--to=tlan@stud.ntnu.no \
--cc=Hasch@t-online.de \
--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