I just installed 3.8 on a Soekris net4801 that's been laying around for a while (unused, unpowered). I noticed after install that time was off by like 5 months, so I set it to within a few minutes of current time/date from the wall clock.
I've been checking the logs, and this is what I'm seeing... this has been going on for about 8 hours now. Why is ntpd having to make 60+ second adjustments every 3-5 minutes? It would appear the clock on the Soekris is really BFU. I researched this a bit, and found out there were (are) some issues with timekeeping on the net4801's processor, but the other platforms (Linux, FreeBSD) seemed to have solved the problem by using a different clock. I saw nothing that would suggest any current problems with OpenBSD. WTF, O? Thanks, Jay Nov 14 06:30:10 opie ntpd[4133]: adjusting local clock by -91.931803s Nov 14 06:34:22 opie ntpd[4133]: adjusting local clock by -90.983786s Nov 14 06:37:42 opie ntpd[4133]: adjusting local clock by -90.136183s Nov 14 06:38:01 opie ntpd[14058]: peer 213.61.224.44 now valid Nov 14 06:41:25 opie ntpd[4133]: adjusting local clock by -88.969563s Nov 14 06:44:33 opie ntpd[4133]: adjusting local clock by -88.039023s Nov 14 06:45:45 opie ntpd[14058]: peer 65.102.104.139 now valid Nov 14 06:48:48 opie ntpd[4133]: adjusting local clock by -87.275355s Nov 14 06:52:15 opie ntpd[4133]: adjusting local clock by -86.527847s Nov 14 06:55:43 opie ntpd[4133]: adjusting local clock by -85.775024s Nov 14 06:57:38 opie ntpd[14058]: peer 65.102.104.139 now invalid Nov 14 06:58:19 opie ntpd[4133]: adjusting local clock by -85.221285s Nov 14 07:01:38 opie ntpd[4133]: adjusting local clock by -84.338437s Nov 14 07:04:48 opie ntpd[4133]: adjusting local clock by -83.437080s Nov 14 07:08:18 opie ntpd[14058]: peer 65.102.104.139 now valid Nov 14 07:08:40 opie ntpd[14058]: peer 65.102.104.139 now invalid Nov 14 07:08:44 opie ntpd[4133]: adjusting local clock by -82.500680s Nov 14 07:12:15 opie ntpd[4133]: adjusting local clock by -81.562691s Nov 14 07:15:44 opie ntpd[4133]: adjusting local clock by -80.871930s Nov 14 07:19:24 opie ntpd[4133]: adjusting local clock by -80.103985s Nov 14 07:19:55 opie ntpd[14058]: peer 65.102.104.139 now valid Nov 14 07:22:17 opie ntpd[4133]: adjusting local clock by -79.112030s Nov 14 07:26:17 opie ntpd[4133]: adjusting local clock by -78.507867s Nov 14 07:27:26 opie ntpd[14058]: peer 65.102.104.139 now invalid Nov 14 07:30:31 opie ntpd[4133]: adjusting local clock by -77.137970s Nov 14 07:34:31 opie ntpd[4133]: adjusting local clock by -76.275602s Nov 14 07:38:22 opie ntpd[14058]: peer 65.102.104.139 now valid Nov 14 07:38:44 opie ntpd[4133]: adjusting local clock by -75.556709s Nov 14 07:41:22 opie ntpd[4133]: adjusting local clock by -74.659299s Nov 14 07:41:38 opie ntpd[14058]: peer 65.102.104.139 now invalid Nov 14 07:44:40 opie ntpd[4133]: adjusting local clock by -73.778046s Nov 14 07:47:49 opie ntpd[4133]: adjusting local clock by -73.123884s Nov 14 07:52:09 opie ntpd[4133]: adjusting local clock by -72.233839s Nov 14 07:56:05 opie ntpd[4133]: adjusting local clock by -71.240807s Nov 14 07:59:08 opie ntpd[4133]: adjusting local clock by -70.277551s Nov 14 08:02:27 opie ntpd[4133]: adjusting local clock by -69.496544s Nov 14 08:06:30 opie ntpd[4133]: adjusting local clock by -68.464538s Nov 14 08:10:36 opie ntpd[4133]: adjusting local clock by -67.807755s Nov 14 08:14:14 opie ntpd[4133]: adjusting local clock by -66.636277s Nov 14 08:14:23 opie ntpd[14058]: peer 65.102.104.139 now valid Nov 14 08:17:56 opie ntpd[4133]: adjusting local clock by -66.035356s Nov 14 08:20:36 opie ntpd[4133]: adjusting local clock by -65.174887s Nov 14 08:24:20 opie ntpd[4133]: adjusting local clock by -64.294286s Nov 14 08:27:59 opie ntpd[4133]: adjusting local clock by -63.612736s
