[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4739E4E5.2010602@rtr.ca>
Date: Tue, 13 Nov 2007 12:54:45 -0500
From: Mark Lord <liml@....ca>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Natalie Protasevich <protasnb@...il.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
alsa-devel@...a-project.org, linux-ide@...r.kernel.org,
linux-pcmcia@...ts.infradead.org,
linux-input@...ey.karlin.mff.cuni.cz,
bugme-daemon@...zilla.kernel.org
Subject: Re: [BUG] New Kernel Bugs
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"
>>> > > <protasnb@...il.com> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists