Setting this as invalid. If you still see problems, I suggest you use
"ntpdate time.nist.gov" as a cron job. :)
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
time drifting, jumps ahead, with/without ntp server
https://bugs.launchpad.net/bugs/104091
You received this bug no
Update: I disabled spread spectrum and some overclocking options in
BIOS. Now the clock skew / time difference is only minimal!
Please read comments #11 and #12 from another bug:
https://bugs.launchpad.net/ubuntu/+source/adjtimex/+bug/553237/comments/11
https://bugs.launchpad.net/ubuntu/+source/ad
woohoo! adjtimex was the answer to my problems!
** Description changed:
No matter which ntp server I choose, the time jumps ahead after a day or so
for 10 to 20 minutes. It looks as if the timer is not correct when counting.
I'll try without the ntp synchronizing, just to see if this relies
Hm... I just installed adjtimex, I think this package is the answer:
$ sudo apt-get install adjtimex
[...]
Unpacking adjtimex (from .../adjtimex_1.27.1-3_amd64.deb) ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Setting up
This problem is called "systematic time drift", it seems to happen a lot and it
is explained in the manual page:
http://manpages.ubuntu.com/hwclock
http://bugs.archlinux.org/task/13684
[quote]
Automatic Hardware Clock Synchronization By the Kernel
You should be aware of another way that the Hard
** Summary changed:
- time jumps ahead 10-20 minutes no matter the ntp server
+ time drifting, jumps ahead, with/without ntp server
--
time drifting, jumps ahead, with/without ntp server
https://bugs.launchpad.net/bugs/104091
You received this bug notification because you are a member of Ubuntu
