* Frank Sorenson <[EMAIL PROTECTED]> [050408 01:49]: > Tony Lindgren wrote: > | * Tony Lindgren <[EMAIL PROTECTED]> [050407 23:28]: > | > |>I think I have an idea on what's going on; Your system does not wake to > |>APIC interrupt, and the system timer updates time only on other > interrupts. > |>I'm experiencing the same on a loaner ThinkPad T30. > |> > |>I'll try to do another patch today. Meanwhile it now should work > |>without lapic in cmdline. > | > | > | Following is an updated patch. Anybody having trouble, please try > | disabling CONFIG_DYN_TICK_USE_APIC Kconfig option. > | > | I'm hoping this might work on Pavel's machine too? > | > | Tony > > This updated patch seems to work just fine on my machine with lapic on > the cmdline and CONFIG_DYN_TICK_USE_APIC disabled. > > Also, you were correct that removing lapic from the cmdline allowed the > previous version to run at full speed.
Cool. > Now, how can I tell if the patch is doing its thing? What should I be > seeing? :) Download pmstats from http://www.muru.com/linux/dyntick/, you may need to edit it a bit for correct ACPI battery values. But it should show you HZ during idle and load. I believe idle still does not go to ACPI C3 with dyn-tick though... Then you might as well run timetest from same location too to make sure your clock keeps correct time. > Functionally, it looks like it's working. There were a number of > compiler warnings you might wish to fix before calling it good. Such as > "initialization from incompatible pointer type" several times in > dyn-tick-timer.c and a "too many arguments for format" in > dyn_tick_late_init. Yeah, I'll fix those... Tony - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/