Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965701AbXEAPWI (ORCPT ); Tue, 1 May 2007 11:22:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965698AbXEAPWI (ORCPT ); Tue, 1 May 2007 11:22:08 -0400 Received: from www.osadl.org ([213.239.205.134]:36819 "EHLO mail.tglx.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S965695AbXEAPWF (ORCPT ); Tue, 1 May 2007 11:22:05 -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: Daniel Walker , Linux Kernel , Linus Torvalds In-Reply-To: <46374B1D.6050509@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> Content-Type: text/plain Date: Tue, 01 May 2007 17:24:21 +0200 Message-Id: <1178033061.5791.314.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: 1251 Lines: 36 On Tue, 2007-05-01 at 10:13 -0400, Mark Lord wrote: > Thomas Gleixner wrote: > > On Tue, 2007-05-01 at 09:34 -0400, Mark Lord wrote: > >>> now at 3232363876949 nsecs > >> ... > >> > >> Oh, in case it matters any: > >> that /proc/timer_list is from the system with CFS-V7 also patched in. > > > > It should not. What happens when you disable HPET ? > > Booting with clocksource=tsc still hangs in what appears > to be the exact same place. I meant disable HPET via: hpet=disable on the commandline > Screenshots for that are available here: http://rtr.ca/hrtimers/ > > Of possible interest is that the bottom of the 25line screen capture > differs somewhat from the 50line capture.. see for yourself. > This is 100% consistent from boot to boot. > > Using CONFIG_DETECT_SOFTLOCKUP=y eliminates the problem, > so that's really got to be a huge clue, somehow ? Unfortunately not. Other than it runs the watchdog task once a second it does not affect the time/clockevent... mechanisms at all 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/