From: "Thomas Langås" <tlan@stud.ntnu.no>
To: Johan <jo_ni@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Still having problems with eepro100
Date: Tue, 30 Oct 2001 12:57:20 +0100 [thread overview]
Message-ID: <20011030125720.A469@stud.ntnu.no> (raw)
In-Reply-To: <20011030123927.74e26501.jo_ni@telia.com>
In-Reply-To: <20011030123927.74e26501.jo_ni@telia.com>; from jo_ni@telia.com on Tue, Oct 30, 2001 at 12:39:27PM +0100
Johan:
> Does anyone except me still having problems with the eepro100 drivers ?
Yes, as I've mentioned in a earlier thread on this list, we have problems,
but trying the e100-driver from intel doesn't seem to help either (I'm
running tests now, and so far, they don't look very promising).
> The network connection stalls and I'll get this message:
> eepro100: wait_for_cmd_done timeout!
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).
--
Thomas
next prev parent reply other threads:[~2001-10-30 11:57 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 [this message]
2001-10-30 12:05 ` Johan
2001-10-30 12:58 ` Kirill Ratkin
2001-10-30 20:19 ` Kurt Roeckx
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=20011030125720.A469@stud.ntnu.no \
--to=tlan@stud.ntnu.no \
--cc=jo_ni@telia.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