Date: Tue, 8 Nov 2005 13:27:44 +0100
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)
Message-ID: <20051108122744.GA3045@elte.hu>
References: <20051106193142.GD26862@skl-net.de> <17262.31781.497775.640424@cse.unsw.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <17262.31781.497775.640424@cse.unsw.edu.au>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 829
Lines: 23


* 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/