Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1767097AbXEBWiz (ORCPT ); Wed, 2 May 2007 18:38:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1767121AbXEBWiy (ORCPT ); Wed, 2 May 2007 18:38:54 -0400 Received: from www.osadl.org ([213.239.205.134]:37017 "EHLO mail.tglx.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1767117AbXEBWix (ORCPT ); Wed, 2 May 2007 18:38:53 -0400 Subject: Re: [BUG] 2.6.21: Kernel won't boot with either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS From: Thomas Gleixner Reply-To: tglx@linutronix.de To: Mark Lord Cc: Andrew Morton , Daniel Walker , Linux Kernel , Linus Torvalds In-Reply-To: <463910BF.9050103@rtr.ca> References: <46364EBC.5050804@rtr.ca> <46364F5A.2030208@rtr.ca> <463653A3.5040606@rtr.ca> <46367D7E.6060502@rtr.ca> <1177976798.12796.286.camel@imap.mvista.com> <463683A6.4010505@rtr.ca> <1178026458.5791.305.camel@localhost.localdomain> <4637419D.8010303@rtr.ca> <463741F1.7050706@rtr.ca> <1178027285.5791.307.camel@localhost.localdomain> <46374B1D.6050509@rtr.ca> <1178035058.5791.333.camel@localhost.localdomain> <46377055.2060605@rtr.ca> <1178092035.5791.349.camel@localhost.localdomain> <20070502010527.e64dcce9.akpm@linux-foundation.org> <1178120457.25504.17.camel@localhost.localdomain> <463910BF.9050103@rtr.ca> Content-Type: text/plain Date: Thu, 03 May 2007 00:41:15 +0200 Message-Id: <1178145675.2340.28.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1133 Lines: 33 On Wed, 2007-05-02 at 18:29 -0400, Mark Lord wrote: > Oh crap. It's back. > > I don't know what's different from before, > but the system now locks up again exactly the same way, > even with the lock contention fix applied. Which is less surprising and confusing than the previous result. It points to some subtle race condition somewhere, which got affected by the slightly timing change. > With or without CONFIG_PROVE_LOCKING=y in the config. Ok. > I've gotta get some work done here (this is my primary development machine), > so it's back to CONFIG_DETECT_SOFTLOCKUP=y for a while. > > If anyone has a patch to dump out state/whatever just before that > last message that preceeds all lockups, then pass it along and > I'll queue it up for testing as soon as I can. I try to come up with something, but I'm travelling tomorrow, so it might be not before end of week. tglx - 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/