Public bug reported:
Binary package hint: adjtimex
The version of adjtimex in hardy universe appears to have a Bug making
it produce wildly inaccurate drift estimates on some mainboards.
For example:
r...@mouldy:/home/as# adjtimex -c=10 -d
--- current --- -- suggested --
cmos time system-cmos error_ppm tick freq tick freq
1236933734 9.688040
1236933744 9.796719 10867.9 10000 5679872
1236933754 9.905411 10869.2 10000 5679872 9892 1142110
1236933764 10.014111 10870.0 10000 5679872 9892 1095235
1236933774 10.122804 10869.3 10000 5679872 9892 1137422
1236933783 10.231498 10869.4 10000 5679872 9892 1134297
where hwclock instead reckons
a...@mouldy:~$ hwclock --show ;date
Fri 13 Mar 2009 09:52:07 CET -0.721038 seconds
Fri Mar 13 09:52:07 CET 2009
The effect is, of course, that the a huge (erroneous) correction for the
systemc clock is recorded causing
massive system clock drift massively after adjtimex installation.
Later revisions of adjtimex appear to include new options to fix this
issue.
See (for example)
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/296ac353aede8ddb?fwc=1
** Affects: adjtimex (Ubuntu)
Importance: Undecided
Status: New
--
adjtimex broken on AMD64 / nForce chipset
https://bugs.launchpad.net/bugs/342166
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
