* Pavel Machek <[EMAIL PROTECTED]> [050119 15:58]: > Hi! > > > > > Thanks for trying it out. I have quite accurate time here on my > > > > systems, and sleep works as it should. I wonder what's happening on > > > > your system? If you have a chance, could you please post the results > > > > from following simple tests? > > > > > > On patched 2.6.11-rc1: > > > > > > [Heh, clock is two times too fast, perhaps that makes ntpdate fail? -- > > > yes. > > > > > > [EMAIL PROTECTED]:~# dmesg | grep -i time; for i in 1 2 3 4 5; do ntpdate > > > -b tak.cesnet.cz && sleep 10; done ; date && sleep 10 && date; while [ 1 > > > ]; do date; done | uniq > > > PCI: Setting latency timer of device 0000:00:11.5 to 64 > > > dyn-tick: Enabling dynamic tick timer > > > dyn-tick: Timer using dynamic tick > > > > Thanks. Looks like you're running on PIT only, I guess my patch > > currently breaks PIT (and possibly HPET) No dmesg message for " > > "Using XXX for high-res timesource". > > This machine definitely has TSC... What do I have to do in .config to > make it do something interesting? My .config is:
I suspect it's the HPET_TIMER, see below. CONFIG_X86_PM_TIMER is optional, otherwise TSC is used. Tony
--- config.orig 2005-01-19 16:05:16.000000000 -0800 +++ config 2005-01-19 16:06:07.000000000 -0800 @@ -103,7 +103,7 @@ CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y -CONFIG_HPET_TIMER=y +# CONFIG_HPET_TIMER is not set CONFIG_NO_IDLE_HZ=y # CONFIG_SMP is not set CONFIG_PREEMPT=y @@ -169,7 +169,7 @@ CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y -# CONFIG_X86_PM_TIMER is not set +CONFIG_X86_PM_TIMER=y # CONFIG_ACPI_CONTAINER is not set #
