On Tue, 13 Nov 2007, Mark Lord wrote:
Thomas Gleixner wrote:On Tue, 13 Nov 2007, Mark Lord wrote:..
The bug report is bogus. ARM has no CONFIG_HPET_TIMER.Andrew Morton wrote:..On Mon, 12 Nov 2007 22:42:32 -0800 "Natalie Protasevich"
<protasnb@xxxxxxxxx> wrote:
..doesn'twith CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23boot (ARM, Timer)
http://bugzilla.kernel.org/show_bug.cgi?id=9229
Kernel: 2.6.23
No response from developers
Hmm, at which point does the boot stop ?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.
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 ?