Thomas Gleixner wrote:

On Tue, 13 Nov 2007, Mark Lord wrote:

quoted

Thomas Gleixner wrote:

quoted

On Tue, 13 Nov 2007, Mark Lord wrote:

quoted

quoted

Andrew Morton wrote:

quoted

quoted

On Mon, 12 Nov 2007 22:42:32 -0800 "Natalie Protasevich"
[off-list ref] wrote:

..

quoted

quoted

quoted

quoted

with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23

doesn't

quoted

quoted

quoted

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.  

quoted

quoted

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).

quoted

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 ?

Yeah.  No magic sysrq key or anything.
There's gotta be a race somewhere that's causing it,
but it's not obvious where to look for it.

My regular 2-core notebook no longer suffers from it,
and subtle .config changes used to make it come and go
back when it first appeared.

The quad-core has only done it twice on me thus far.

Tracking this one down looks tricky.  It might require some early lockup
detection code to be tailor made or something.

Cheers