Subject: Re: [BUG] 2.6.21: Kernel won't boot with either/both
	of	CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS
From: Daniel Walker <dwalker@mvista.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
       Linux Kernel <linux-kernel@vger.kernel.org>, tglx@linutronix.de,
       Linus Torvalds <torvalds@osdl.org>
In-Reply-To: <4636B4F9.6040406@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>
	 <6bffcb0e0704301707w7287f1bdk32be8bc8ce7cda80@mail.gmail.com>
	 <463685BD.8010604@rtr.ca> <1177978391.12796.301.camel@imap.mvista.com>
	 <4636B4F9.6040406@rtr.ca>
Content-Type: text/plain
Date: Mon, 30 Apr 2007 21:34:25 -0700
Message-Id: <1177994065.12796.317.camel@imap.mvista.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 977
Lines: 27

On Mon, 2007-04-30 at 23:33 -0400, Mark Lord wrote:
> Daniel Walker wrote:
> > 
> > I'm interested in which clocksource is getting used, which is in the
> > boot log.
> 
> Well then, send me a patch that dumps that information out just before it locks up.
> We know (first post in this thread) that the lockup occurs just after
> these two messages:
> 
>   "switched to high resolution mode on cpu 1"
>   "switched to high resolution mode on cpu 0"
> 
> So just dump out anything else you need to see at the same time,
> and it'll still be on my screen when the darned thing locks up.
> 
> Simple, eh.  We both get to run around a treadmill this way.  ;)

Forgot it's an SMP system .. So would have to be clocksource=tsc . 

Daniel

-
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/