> [ rc.conf and ntp.conf snipped ] > > Thank you for the suggestions. Unfortunately, I've been through all > that, including the rude values of minpoll and maxpoll, using multiple > servers, and starting with a fresh drift file. I'm pretty sure ntpd > isn't the problem. In addition, the hardware clock itself appears to be > plenty accurate, as it is always correct within a second or two when I > check it directly in BIOS ... and two other 5.3-STABLE hosts on the same > network, with the same ntpd configuration, but on different hardware, do > not have this problem, which began when I updated (reinstalled) to > 5.3-STABLE from 5.2. > > - -- > David Talkington > [EMAIL PROTECTED]
I apparently misposted this earlier, my apologies. Have you tried all possible values for kern.timecounter.hardware? #sysctl kern.timecounter.choice My most recent encounter with this issue, a K6-2/500 on an Asus P5A mobo, needed "i8254". HTH, Kevin Kinsey _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
