ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Fri, 12 Feb 2010 17:44:52 +0100
Torfinn Ingolfsen <torfinn.ingolfsen at broadpark.no> wrote:

> On Fri, 12 Feb 2010 05:11:17 -0800
> Jeremy Chadwick <freebsd at jdc.parodius.com> wrote:
> 
> > Please try doing this:
> > 
> > - stop ntpd
> > - rm /var/db/ntpd.drift
> > - sysctl kern.timecounter.hardware=ACPI-safe
> > - start ntpd
> 
> Thanks, I'm currently testing that. Results in 72 hours (or less) :-)

Well, using ACPI-safe only get a small improvement,
here are the lines from /var/log/messages:
Feb 17 17:16:47 kg-f2 ntpd[912]: time reset +1.785920 s
Feb 17 17:32:39 kg-f2 ntpd[912]: time reset +1.836376 s
Feb 17 17:48:18 kg-f2 ntpd[912]: time reset +1.811593 s
Feb 17 18:04:12 kg-f2 ntpd[912]: time reset +1.840545 s
Feb 17 18:19:19 kg-f2 ntpd[912]: time reset +1.751837 s
Feb 17 18:35:19 kg-f2 ntpd[912]: time reset +1.852328 s
Feb 17 18:51:18 kg-f2 ntpd[912]: time reset +1.850928 s
Feb 17 19:06:50 kg-f2 ntpd[912]: time reset +1.798706 s
Feb 17 19:22:35 kg-f2 ntpd[912]: time reset +1.823697 s
Feb 17 19:37:56 kg-f2 ntpd[912]: time reset +1.777376 s

Unfortunately, it isn't enough to keep the machine in sync all the time.
But it is better than HPET so I'll keep it.
-- 
Torfinn