From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: alan@redhat.com, linux-kernel@vger.kernel.org
Subject: 2.2.18pre19 RPC NFS Errors/2.4.0 Lockup
Date: Fri, 03 Nov 2000 13:21:11 -0700 [thread overview]
Message-ID: <3A031E37.4808BF8D@timpanogas.org> (raw)
Alan,
The 2.2.18pre-19 build does not reproduce this problem with NFS RPC
timeouts, and Andre has merged his patches for our next release, and I
am unable to reproduce it. In fact, it's running great. I did have
NDS eDirectory installed on this box when I saw the problem, and without
this software loaded, it seems to be gone. I think it may be related to
eDirectory in some way (top is reporting some busy process in
eDirectory). I held off posting the release to reverify the 2.2.18pre18
problems, and to get Andre's patches into the release. We will go out
with 2.2.18pre-19 at this point.
Also, I am seeing a lockup on 2.4.0-10 with uniprocessor PPro systems
with SMP enabled, but it runs great on a 4xPPro system with SMP (???).
I rebuilt with SMP=N and it also ran great. One for H. Peter Anvin I
think ....
:-)
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-11-03 20:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A031E37.4808BF8D@timpanogas.org \
--to=jmerkey@timpanogas.org \
--cc=alan@redhat.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