Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761236AbXKMWrU (ORCPT ); Tue, 13 Nov 2007 17:47:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756068AbXKMWrE (ORCPT ); Tue, 13 Nov 2007 17:47:04 -0500 Received: from www.tglx.de ([62.245.132.106]:51020 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754312AbXKMWrB (ORCPT ); Tue, 13 Nov 2007 17:47:01 -0500 Date: Tue, 13 Nov 2007 23:46:19 +0100 (CET) From: Thomas Gleixner To: Mark Lord cc: Andrew Morton , Natalie Protasevich , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, alsa-devel@alsa-project.org, linux-ide@vger.kernel.org, linux-pcmcia@lists.infradead.org, linux-input@atrey.karlin.mff.cuni.cz, bugme-daemon@bugzilla.kernel.org Subject: Re: [BUG] New Kernel Bugs In-Reply-To: <4739E4E5.2010602@rtr.ca> Message-ID: References: <32209efe0711122242m3a5f081asf1c11a38b24db10c@mail.gmail.com> <20071113031553.3c7b5c16.akpm@linux-foundation.org> <4739ADA2.4060604@rtr.ca> <4739E4E5.2010602@rtr.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1501 Lines: 41 On Tue, 13 Nov 2007, Mark Lord wrote: > Thomas Gleixner wrote: > > On Tue, 13 Nov 2007, Mark Lord wrote: > > > > > > Andrew Morton wrote: > > > > > > On Mon, 12 Nov 2007 22:42:32 -0800 "Natalie Protasevich" > > > > > > wrote: > > > > .. > > > > > > > > with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23 > > > > > doesn't > > > > > > > > boot (ARM, Timer) > > > > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=9229 > > > > > > > > Kernel: 2.6.23 > > > > > > > > No response from developers > > > > .. > > > > The bug report is bogus. ARM has no CONFIG_HPET_TIMER. > > > > Note: that same bug exists/existed on i386 back when NO_HZ was > > > > introduced (2.6.21?). I still see it from time to time on my Quad core > > > > system (very rare), but not any more on my Duo notebook where it used > > > > to happen about 1 in n boots (n < 10). > > > > > AFAICT no fix was ever released for it. > > > > Hmm, at which point does the boot stop ? > .. > > Just as it prints out these messages, sometimes one of them, > sometimes both (or all four on the quad core): > > kernel: switched to high resolution mode on cpu 1 > kernel: switched to high resolution mode on cpu 0 It's completely dead afterwards ? 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/