From: Dave Jones <davej@suse.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>,
Robert Love <rml@tech9.net>, Luigi Genoni <kernel@Expansa.sns.it>,
Arkadiy Chapkis - Arc <achapkis@mail.dls.net>,
LINUX-KERNEL@vger.kernel.org
Subject: Re: thread_info implementation
Date: Tue, 12 Feb 2002 01:09:11 +0100 [thread overview]
Message-ID: <20020212010911.O4285@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0202112140280.6590-100000@Expansa.sns.it> <1013460534.6784.477.camel@phantasy> <3C6855A2.4721DDD3@mandrakesoft.com> <20020211154917.A19367@are.twiddle.net>
In-Reply-To: <20020211154917.A19367@are.twiddle.net>; from rth@twiddle.net on Mon, Feb 11, 2002 at 03:49:17PM -0800
On Mon, Feb 11, 2002 at 03:49:17PM -0800, Richard Henderson wrote:
> Though I seem to be having some problems with NFS. Mount goes into D
> state for quite some time and the portmapper complains about timeouts
> connecting to localhost. Anyone else see anything like that? I suppose
> I'll build an x86 kernel from the same source and see what I can find...
Yes. I saw this start happening in my tree when I merged 2.5.4pre2
When I tried a 2.5.4pre2 vanilla, the problem was gone, so I put it
down to a problem in my tree. When I rebooted back into it, the problem
was gone. Aren't heisenbugs fun?
Exactly the same symptoms, portmap borken, NIS/NFS subsequently fail.
This was on x86 btw.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-02-12 0:15 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 17:39 Arkadiy Chapkis - Arc
2002-02-11 20:19 ` Robert Love
2002-02-11 20:42 ` Luigi Genoni
2002-02-11 20:48 ` Robert Love
2002-02-11 23:37 ` Jeff Garzik
2002-02-11 23:49 ` Richard Henderson
2002-02-12 0:09 ` Dave Jones [this message]
2002-02-12 0:20 ` Jeff Garzik
2002-02-12 0:24 ` Dave Jones
2002-02-11 21:08 Roman Zippel
2002-02-11 20:50 ` Anton Blanchard
2002-02-12 0:01 ` Roman Zippel
2002-02-12 0:10 ` David Howells
2002-02-12 0:22 ` Roman Zippel
2002-02-12 0:46 ` David S. Miller
2002-02-12 0:57 ` Roman Zippel
2002-02-12 0:57 ` David S. Miller
2002-02-12 1:10 ` Roman Zippel
2002-02-12 13:01 ` Bjorn Wesen
2002-02-12 13:49 ` David S. Miller
2002-02-12 1:01 ` David Mosberger
2002-02-12 1:21 ` David Mosberger
2002-02-12 1:36 ` David Mosberger
2002-02-12 1:53 ` David Mosberger
2002-02-12 2:30 ` David Mosberger
2002-02-12 2:46 ` David Mosberger
2002-02-12 3:01 ` David Mosberger
2002-02-12 3:18 ` David Mosberger
2002-02-12 3:32 ` David Mosberger
2002-02-12 4:16 ` David Mosberger
2002-02-12 4:33 ` David Mosberger
2002-02-12 5:26 ` Richard Henderson
2002-02-12 5:50 ` David Mosberger
2002-02-13 11:18 ` Anton Blanchard
2002-02-12 5:32 ` David S. Miller
2002-02-12 5:57 ` Richard Henderson
2002-02-12 2:49 ` Davide Libenzi
2002-02-12 1:07 ` David S. Miller
2002-02-12 1:32 ` David S. Miller
2002-02-12 1:41 ` David S. Miller
2002-02-12 2:22 ` David S. Miller
2002-02-12 2:36 ` David S. Miller
2002-02-12 2:51 ` David S. Miller
2002-02-12 3:04 ` David S. Miller
2002-02-12 3:23 ` David S. Miller
2002-02-12 3:42 ` David S. Miller
2002-02-12 4:21 ` David S. Miller
2002-02-12 17:14 ` Pavel Machek
2002-02-13 0:46 ` David S. Miller
2002-02-13 1:30 ` Roman Zippel
2002-02-12 9:12 ` Roman Zippel
2002-02-12 9:30 ` Jeff Garzik
2002-02-12 10:14 ` Roman Zippel
2002-02-12 13:21 ` David Howells
2002-02-12 19:15 ` David Mosberger
2002-02-12 19:38 ` David Howells
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=20020212010911.O4285@suse.de \
--to=davej@suse.de \
--cc=LINUX-KERNEL@vger.kernel.org \
--cc=achapkis@mail.dls.net \
--cc=jgarzik@mandrakesoft.com \
--cc=kernel@Expansa.sns.it \
--cc=rml@tech9.net \
/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
all inboxes | Powered by JetHome®