On Jan 26, 2009, at 5:17 PM, Patrick Domack wrote: > Sounds like the same issue I had with one of my servers, everything > ran fine, I moved it to a datacenter, and ntp couldn't keep the time > in sync at all, moved it back, and it was fine again. It was a dual > cpu computer, and the default timing method used in the kernel on > freebsd that I was using, kept changing depending on what cpu that > thread ran on at any given time, giving me the same log messages > your getting: > >> Jan 22 07:15:48 dobby ntpd[51979]: kernel time sync status change >> 6001 >> Jan 22 07:50:10 dobby ntpd[51979]: kernel time sync status change >> 2001 >> Jan 22 11:00:35 dobby ntpd[51979]: kernel time sync status change >> 6001 >> Jan 22 11:49:04 dobby ntpd[51979]: kernel time sync status change >> 2001
My system is a single processor, but it as FreeBSD. > I found that for freebsd atleast, there where 3 different clock > source options you can configure, and when I changed it, everything > behaved correctly. > > I added this into /etc/sysctl.conf > > kern.timecounter.hardware=TSC I will look into that. Killing off bittorrent helped a bit, but didn't fully resolve the problem. Though things improved greatly after I reset state on my firewall/router. Still there are some odd hiccoughs, and you may have identified the problem. Thank you. -j -- Jeffrey Goldberg http://www.goldmark.org/jeff/ _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
