From: Kurt Roeckx <Q@ping.be>
To: "Thomas Langås" <tlan@stud.ntnu.no>
Cc: Johan <jo_ni@telia.com>, linux-kernel@vger.kernel.org
Subject: Re: Still having problems with eepro100
Date: Tue, 30 Oct 2001 21:19:12 +0100 [thread overview]
Message-ID: <20011030211912.A192@ping.be> (raw)
In-Reply-To: <20011030123927.74e26501.jo_ni@telia.com> <20011030125720.A469@stud.ntnu.no>
In-Reply-To: <20011030125720.A469@stud.ntnu.no>; from tlan@stud.ntnu.no on Tue, Oct 30, 2001 at 12:57:20PM +0100
On Tue, Oct 30, 2001 at 12:57:20PM +0100, Thomas Langås wrote:
> I'm experiensing the:
> eth0: Card reports no resources
>
> And, then a hang of at least a minute before the network connection is
> restored. All my connections are 100Mbit full duplex, and the error comes
> when doing heavy traffic. (Try bonnie++ over NFS, for instance).
I used to have this problem too. Whenever I downloaded something
at high speed, I got that error.
This was with an older 2.4 kernel (2.4.5 I think), and the
previous harddisk which died on me. Now with 2.4.8 I don't have
the problem anymore. I assumed it had to do with the other disk
being slow, I think it was still doing PIO. Maybe it's some
other thing which causes the kernel not being able to react fast
enough?
Kurt
next prev parent reply other threads:[~2001-10-30 20:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 11:39 Still having problems with eepro100 Johan
2001-10-30 11:57 ` Thomas Langås
2001-10-30 12:05 ` Johan
2001-10-30 12:58 ` Kirill Ratkin
2001-10-30 20:19 ` Kurt Roeckx [this message]
2001-10-30 12:09 ` Alan Cox
2001-10-30 12:20 ` Rafael Martinez
2001-10-30 16:23 ` Lee Packham
2001-10-30 16:51 ` Kirill Ratkin
2001-10-30 17:07 ` Alex Bligh - linux-kernel
2001-10-31 14:40 ` Alex Bligh - linux-kernel
2001-11-01 11:15 ` Andrey Savochkin
2001-11-01 11:33 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-12-01 0:08 Joe Rice
2001-12-01 0:37 ` Mike Fedyk
2001-12-01 0:49 ` Joe Rice
2001-12-01 1:07 ` Mike Fedyk
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=20011030211912.A192@ping.be \
--to=q@ping.be \
--cc=jo_ni@telia.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