ntpd struggling to keep up - how to fix?

Torfinn Ingolfsen torfinn.ingolfsen at broadpark.no
Sat Feb 13 18:50:35 UTC 2010


On Fri, 12 Feb 2010 11:46:04 -0800
Jeremy Chadwick <freebsd at jdc.parodius.com> wrote:

> override this though!  :-) ), which -- assuming it works -- should
> solve your problem.

We'll see. The box rebooted again last night (see another thread on this
mailing list), so now I have added kern.timecounter.hardware=ACPI-safe
to /etc/sysctl.conf, just in case it reboots again.

> Technical footnote: I wish I understood 1) the difference between
> ACPI-safe and ACPI-fast, and 2) how the system or OS "ranks" the

I'm still wondering why this machine doesn't have ACPI-fast:
oot at kg-f2# sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) dummy(-1000000)

While my workstation do:
tingo at kg-v2$ sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0) dummy(-1000000)
and anaother machine:
root at kg-quiet# sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(800) ACPI-fast(1000) i8254(0) dummy(-1000000)
and another:
root at kg-vm# sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) dummy(-1000000)

Probably a BIOS / acpi problem.
-- 
Torfinn



More information about the freebsd-stable mailing list