From owner-freebsd-ppc@FreeBSD.ORG  Fri Apr  4 21:22:31 2014
Return-Path: <owner-freebsd-ppc@FreeBSD.ORG>
Delivered-To: ppc@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 37EC1A85
 for <ppc@freebsd.org>; Fri,  4 Apr 2014 21:22:31 +0000 (UTC)
Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214])
 by mx1.freebsd.org (Postfix) with ESMTP id E1C8E306
 for <ppc@freebsd.org>; Fri,  4 Apr 2014 21:22:18 +0000 (UTC)
Received: from gromit.timing.com (gromit.timing.com [206.168.13.209])
 by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id s34KrgW8013772;
 Fri, 4 Apr 2014 14:53:54 -0600 (MDT)
 (envelope-from jhein@symmetricom.com)
Received: from gromit.timing.com (localhost [127.0.0.1])
 by gromit.timing.com (8.14.7/8.14.5) with ESMTP id s34KrIg3065485;
 Fri, 4 Apr 2014 14:53:18 -0600 (MDT)
 (envelope-from jhein@gromit.timing.com)
Received: (from jhein@localhost)
 by gromit.timing.com (8.14.7/8.14.7/Submit) id s34KrCpQ065484;
 Fri, 4 Apr 2014 14:53:12 -0600 (MDT) (envelope-from jhein)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <21311.7096.419714.506103@gromit.timing.com>
Date: Fri, 4 Apr 2014 14:53:12 -0600
From: John Hein <john.hein@microsemi.com>
To: Alexey Dokuchaev <danfe@nsu.ru>
Subject: Re: System clock falls behind quickly on Mac mini G4
In-Reply-To: <20140404144753.GA58190@regency.nsu.ru>
References: <20140328071714.GA45961@regency.nsu.ru>
 <CAFY7cWBCFmtx4Tsg3=mSJyscpk5nCY3S6Sxy52TKEoTmy1sFPA@mail.gmail.com>
 <CA+WntOtEoqG_RJ2D9vSb7mO-UfT13RZbAb04p6rV2mWLBu=H9Q@mail.gmail.com>
 <20140329100134.GA7863@regency.nsu.ru>
 <20140404144753.GA58190@regency.nsu.ru>
X-Mailer: VM 8.2.0b-trunk-1484 under 24.3.1 (i386-portbld-freebsd8.3)
Cc: ppc@freebsd.org
X-BeenThere: freebsd-ppc@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting FreeBSD to the PowerPC <freebsd-ppc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ppc/>
List-Post: <mailto:freebsd-ppc@freebsd.org>
List-Help: <mailto:freebsd-ppc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 21:22:31 -0000

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.