From: Ingo Molnar <mingo@elte.hu>
To: Neil Brown <neilb@suse.de>
Cc: Andre Noll <maan@systemlinux.org>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: BUG: soft lockup detected on CPU#0! (linux-2.6.14)
Date: Tue, 8 Nov 2005 13:27:44 +0100 [thread overview]
Message-ID: <20051108122744.GA3045@elte.hu> (raw)
In-Reply-To: <17262.31781.497775.640424@cse.unsw.edu.au>
* Neil Brown <neilb@suse.de> wrote:
> > Nov 4 12:46:44 p133 kernel: BUG: soft lockup detected on CPU#0!
>
> 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?
>
> The following patch might fix it. Please let me know the result.
> try_to_freeze();
> + cond_resched();
and the NFSd thread never considered preemption in any other place? Then
this should be the right fix - the kernel was running under !PREEMPT.
Ingo
prev parent reply other threads:[~2005-11-08 12:27 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
2005-11-07 16:16 ` [NFS] " Andre Noll
2005-11-07 22:13 ` Neil Brown
2005-11-08 12:27 ` Ingo Molnar [this message]
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=20051108122744.GA3045@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maan@systemlinux.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
Powered by JetHome