It seems that something recently toasted the quasi-magic i8254 timecounter
code to the point of unusability.
On my laptop I run a ntpdate every minute, and the result looks like this:
Nov 13 23:37:00 [...] step time server 212.242.40.181 offset -2.862805 sec
Nov 13 23:38:00 [...] step time server 212.242.40.181 offset -6.109507 sec
Nov 13 23:39:00 [...] step time server 212.242.40.181 offset -5.299533 sec
Nov 13 23:40:01 [...] step time server 212.242.40.181 offset -11.220085 sec
Nov 13 23:41:00 [...] step time server 212.242.40.181 offset -6.449271 sec
Nov 13 23:42:00 [...] step time server 212.242.40.181 offset -5.190362 sec
Nov 13 23:43:00 [...] step time server 212.242.40.181 offset -5.438783 sec
Nov 13 23:45:00 [...] step time server 212.242.40.181 offset -4.535331 sec
Nov 13 23:46:00 [...] step time server 212.242.40.181 offset -6.052685 sec
Nov 13 23:47:01 [...] step time server 212.242.40.181 offset -3.289484 sec
Nov 13 23:48:00 [...] step time server 212.242.40.181 offset -2.659785 sec
Nov 13 23:49:00 [...] step time server 212.242.40.181 offset -3.276033 sec
Nov 13 23:50:00 [...] step time server 212.242.40.181 offset -0.919082 sec
Nov 13 23:51:00 [...] step time server 212.242.40.181 offset -4.163177 sec
Nov 13 23:52:00 [...] step time server 212.242.40.181 offset -7.449300 sec
This is on a laptop with APM enabled btw.
You should be able to force the use of the i8254 timecounter by
sysctl -w kern.timecounter.hardware=i8254
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
