* Pavel Machek <pavel@ucw.cz> wrote:

quoted text
> > and send us the output? (Enabling CONFIG_TIMER_STATS, 
> > CONFIG_SCHED_DEBUG and CONFIG_SCHEDSTATS would maximize the amount 
> > of information.)
> 
> This was w/o hpet=disable . Do you want me to test with hpet=disable?

no, this is fine. You've got a hpet clockevents driver and two lapic 
drivers:

Clock Event Device: hpet
 set_next_event: hpet_legacy_next_event
 set_mode:       hpet_legacy_set_mode
 event_handler:  tick_handle_oneshot_broadcast

Clock Event Device: lapic
 set_next_event: lapic_next_event
 set_mode:       lapic_timer_setup
 event_handler:  hrtimer_interrupt

Clock Event Device: lapic
 set_next_event: lapic_next_event
 set_mode:       lapic_timer_setup
 event_handler:  hrtimer_interrupt

to me this has the feeling of lapic breakage in C2 mode. Does it get any 
better if you boot with 'nolapic'? (but that might in turn turn off 
high-res timers and nohz in essence) Thomas, any ideas?

	Ingo
-
unsubscribe notice
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/