From: Andre Noll <maan@systemlinux.org>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: BUG: soft lockup detected on CPU#0! (linux-2.6.14)
Date: Sun, 6 Nov 2005 23:51:38 +0100 [thread overview]
Message-ID: <20051106225138.GF26862@skl-net.de> (raw)
In-Reply-To: <17262.31781.497775.640424@cse.unsw.edu.au>
On 08:56, Neil Brown wrote:
> This seems to suggest that the nfsd thread is always runnable, which
> implies a read-only load with everything in cache - at least for the
> 10 seconds leading up to each of these errors. Is that likely?
Hm, not sure. I was compiling glibc and simultanously running a big
"cvs update" on the nfs server when one of these BUGs happened.
glibc source and the cvs tree live somewhere in /home and /home is
exported rw to a bunch of clients. But no client should have accessed
those two subdirs at that time.
> The following patch might fix it. Please let me know the result.
Patch applied and rebooted. The box currently compiles glibc and
firefox in parallel. No problems so far.
Thanks a lot
Andre
--
Jesus not only saves, he also frequently makes backups
next prev parent reply other threads:[~2005-11-06 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 19:31 Andre Noll
2005-11-06 21:56 ` Neil Brown
2005-11-06 22:51 ` Andre Noll [this message]
2005-11-07 16:16 ` [NFS] " Andre Noll
2005-11-07 22:13 ` Neil Brown
2005-11-08 12:27 ` Ingo Molnar
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=20051106225138.GF26862@skl-net.de \
--to=maan@systemlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.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®