From: Shaya Potter <spotter@cs.columbia.edu>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hard lockup on 2.4.20 w/ nfs over frees/wan
Date: 21 Feb 2003 04:05:31 -0500 [thread overview]
Message-ID: <1045818331.21281.20.camel@zaphod> (raw)
In-Reply-To: <20030220164420.GA9800@gtf.org>
On Thu, 2003-02-20 at 11:44, Jeff Garzik wrote:
> On Thu, Feb 20, 2003 at 11:16:13AM -0500, Shaya Potter wrote:
> > moved from the netfinity's onboard pcnet32 adapter to an IBM branded
> > Intel epro/100 w/ the intel driver in 2.4.20 and it appears very
> > stable. Is it possible the pcnet/32 adapter is broken or the driver is
> > buggy?
>
> I have gotten reports the 2.4.20 pcnet32 is buggy.
>
> Can you test 2.4.20 with 2.4.19 version of pcnet32.c?
I'll do it at the beg. of next week, as I'm not going into the Lab
tomorrow.
I'm using 2 basically (as in have gotten serviced and parts replaced)
netfinity's. 1 seems to work perfectly well w/ the pcnet32 driver/card,
while the other one was having serious issue. Strangely enough, I took
about a 10% hit in performance when I went from the "broken" pcnet32
card to the intel eepro 100 on my informal nfs benchmarks (at least for
the ones that would complete w/o hanging the computer)
next prev parent reply other threads:[~2003-02-21 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 5:56 hard lockup on 2.4.20 w/ nfs over frees/wan Shaya Potter
2003-02-19 20:36 ` Shaya Potter
2003-02-20 16:16 ` Shaya Potter
2003-02-20 16:44 ` Jeff Garzik
2003-02-21 9:05 ` Shaya Potter [this message]
2003-02-24 22:10 ` Shaya Potter
2003-02-24 22:51 ` Jeff Garzik
2003-02-21 15:17 ` Bill Davidsen
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=1045818331.21281.20.camel@zaphod \
--to=spotter@cs.columbia.edu \
--cc=jgarzik@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