Date: Fri, 4 Apr 2014 14:53:12 -0600 From: John Hein <john.hein@microsemi.com> To: Alexey Dokuchaev <danfe@nsu.ru> Cc: ppc@freebsd.org Subject: Re: System clock falls behind quickly on Mac mini G4 Message-ID: <21311.7096.419714.506103@gromit.timing.com> In-Reply-To: <20140404144753.GA58190@regency.nsu.ru> References: <20140328071714.GA45961@regency.nsu.ru> <CAFY7cWBCFmtx4Tsg3=mSJyscpk5nCY3S6Sxy52TKEoTmy1sFPA@mail.gmail.com> <CA%2BWntOtEoqG_RJ2D9vSb7mO-UfT13RZbAb04p6rV2mWLBu=H9Q@mail.gmail.com> <20140329100134.GA7863@regency.nsu.ru> <20140404144753.GA58190@regency.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexey Dokuchaev danfe-at-nsu.ru |jh-fbml/fbml| wrote at 21:47 +0700 on Apr 4, 2014: > On Sat, Mar 29, 2014 at 05:01:34PM +0700, Alexey Dokuchaev wrote: > > On Sat, Mar 29, 2014 at 12:28:12AM -0400, Joe Nosay wrote: > > > I'm curious on two things: > > > 1. Is ntpd running/set in /etc/rc.conf? > > > > No, it's off. I guess if I had it running it won't let the clock to > > behave like that. :) > > Running ntpd(8) unfortunately does not make things better (well maybe it > helps a bit, but clock still drifts away pretty fast). I guess my only > option is to run ntpdate(8) periodically. :-( You could try chronyd vs. ntpd - the former works with a larger frequency error. Untested by me. I also don't think we have a port yet. It may be that your mini G4 may have real clock issues - that would require some analysis to determine if that's real or a software bug. But chronyd might be a workaround (if it's not too hard to port) until someone who is motivated can do a more careful analysis.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21311.7096.419714.506103>