From: Dave Jones <davej@suse.de>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: portmap problems with 2.5.4-pre5
Date: Wed, 13 Feb 2002 19:28:51 +0100 [thread overview]
Message-ID: <20020213192851.C925@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0202130818430.15774-100000@netfinity.realnet.co.sz>
In-Reply-To: <Pine.LNX.4.44.0202130818430.15774-100000@netfinity.realnet.co.sz>; from zwane@linux.realnet.co.sz on Wed, Feb 13, 2002 at 08:20:34AM +0200
On Wed, Feb 13, 2002 at 08:20:34AM +0200, Zwane Mwaikambo wrote:
> I tried to mount an NFS filesystem and had mount stuck in the D state for
> quite a while (minutes), this was also in my logs.
>
> Jan 1 02:06:00 mondecino kernel: portmap: server localhost not responding, timed out
> Jan 1 02:06:00 mondecino kernel: lockd_up: makesock failed, error=-5
> Jan 1 02:07:40 mondecino kernel: portmap: server localhost not responding, timed out
>
> Eventually it did mount, but i've never had this error before on that box
> (i use the box daily and do that mount more than 5 times a day). I've been
> using 2.5 on that box since 2.5.0. I seem to be able to reproduce it, so
> i'll leave the box running in case anyone wants to try anything.
Richard Henderson mentioned it yesterday in the Re: thread_info implementation
thread. (msgid: 20020211154917.A19367@are.twiddle.net). I've also seen
it recently (circa .4pre3), then it went away, and now I have a box thats also
doing it repeatedly.
afaik, no-one else has looked at it in detail yet (or seen it?)
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-02-13 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 6:20 portmap problems with 2.5.4-pre5 Zwane Mwaikambo
2002-02-13 18:28 ` Dave Jones [this message]
2002-02-14 6:53 ` Zwane Mwaikambo
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=20020213192851.C925@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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