Date: Tue, 21 Mar 2006 18:08:41 -0800 From: Alfred Morgan <alfred.morgan@experclick.com> To: sub02@freeode.co.uk Cc: freebsd-questions@freebsd.org Subject: Re: clock drifts after upgrade from 5.x to 6.x Message-ID: <4420B1A9.2000603@experclick.com> In-Reply-To: <7c61221qt0meet1dudmids5vgcisejjjth@4ax.com> References: <44204E79.4090408@experclick.com> <7c61221qt0meet1dudmids5vgcisejjjth@4ax.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have now enabled ACPI on one machine (making the computer more unstable) and it has stopped drifting. ntpd was disabled for this test. Now that it shows it stopped drifting I have enabled ntpd to see if that causes problems. On another machine I have left ACPI disabled and restarted ntpd (with -g) and exactly 6 hours later I got: Mar 21 16:44:13 ntpd[19918]: time reset +3521.285507 s Mar 21 16:44:13 ntpd[19918]: kernel time sync disabled 6041 I tried looking in timex.h to see what 6041 ment but I could not figure out if 6041 is a mode code or status code. John Murphy wrote: > Interesting. Were all the upgrades from versions less than 5.3 > I wonder? Reason I ask is that many people (including me) seem to > have started having problems with ntp around that time. There was > a thread in the stable mailing list about it here: > http://docs.freebsd.org/cgi/mid.cgi?20050401104508.GJ71384 > > Perhaps the ntp problem is related to what you're seeing and not > an ntp problem at all. Someone raised a bug report at ntp.isc.org > https://ntp.isc.org/bugs/show_bug.cgi?id=452 > but it has had no action. > > Sorry it's only a hunch and not a solution. > > > Versions were 5.3 or 5.4 upgraded to 6.0 or 6.1 -alfred
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4420B1A9.2000603>