acpi-cpufreq / time offset

[hand]

# ntpdate-debian
 1 Nov 16:56:02 ntpdate[28631]: step time server 192.43.244.18 offset 57.335479 sec
# ntpdate-debian
 1 Nov 16:57:29 ntpdate[28777]: step time server 192.43.244.18 offset 6.157663 sec

       6 seconds offset after 1 minute and 27 seconds at cpu MHz : 2400.000

# ntpdate-debian
 1 Nov 16:58:48 ntpdate[28819]: adjust time server 192.43.244.18 offset -0.000783 sec
# ntpdate-debian
 1 Nov 17:01:20 ntpdate[29085]: adjust time server 192.43.244.18 offset -0.006104 sec

       and 0 seconds offset in 1 minute and 48 sec at cpu MHz : 3000.000

  Problem: When the system is under load (CPU reaches max frequency) there is no so big time offset, but when idle
system clock just "stops". I think that is something wrong in frequency scaling layer, in cause what time slows.

kernel 2.6.31-14-server #48-Ubuntu SMP Fri Oct 16 15:07:34 UTC 2009 x86_64
CPU Intel P4 631, freqscaling with cpufrequtils(acpi-cpufreq).

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Till Ulen (tillulen)]

I experience a very similar issue using Ubuntu 10.04 final running the default desktop kernel on Asus Eee PC 1101HA (single-core 32-bit Atom Z520 CPU with HyperThreading enabled).

Did you find out anything interesting about this problem? Did you try to report it elsewhere?

[hand (burdeiny)]

for me i solved with help of ntpdate running every minute by cron.
nothing else to do from my side.
tnx for mail.

_____________________________________________________________
Are you a Techie? Get Your Free Tech Email Address Now! Visit http://www.TechEmail.com

[hand (burdeiny)]

2.6.31-21-server x86_64 - fixed.
after more than 24 hours running without ntpdate sync time offset is about 0.014696 seconds.
i think, with the future kernels result will be the same.

_____________________________________________________________
Are you a Techie? Get Your Free Tech Email Address Now! Visit http://www.TechEmail.com

[Mohamed Amine Ilidrissi (ilidrissi.amine)]

Marking as Fix Released per last comment