From owner-freebsd-arm@freebsd.org  Thu Oct 26 14:57:59 2017
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9A37E4B7C1
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Thu, 26 Oct 2017 14:57:59 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org
 [54.200.247.200])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9D99980E7C
 for <freebsd-arm@freebsd.org>; Thu, 26 Oct 2017 14:57:59 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-User: 167f99d8-ba5e-11e7-a938-4f970e858fdb
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 73.78.92.27
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [73.78.92.27])
 by outbound1.ore.mailhop.org (Halon) with ESMTPSA
 id 167f99d8-ba5e-11e7-a938-4f970e858fdb;
 Thu, 26 Oct 2017 14:58:13 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id v9QEvp4t001201;
 Thu, 26 Oct 2017 08:57:51 -0600 (MDT) (envelope-from ian@freebsd.org)
Message-ID: <1509029871.56824.49.camel@freebsd.org>
Subject: Re: PINE64 - 12.0-CURRENT r324563 - ntpd can't keep time
From: Ian Lepore <ian@freebsd.org>
To: Mark Millard <markmi@dsl-only.net>, Henri Hennebert <hlh@restart.be>
Cc: freebsd-arm <freebsd-arm@freebsd.org>
Date: Thu, 26 Oct 2017 08:57:51 -0600
In-Reply-To: <4BF75B1E-318C-414A-B5D4-4BA7D6578316@dsl-only.net>
References: <d85f883f-84c2-5051-1996-2a0e73a2c1e7@restart.be>
 <4BF75B1E-318C-414A-B5D4-4BA7D6578316@dsl-only.net>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Oct 2017 14:57:59 -0000

On Thu, 2017-10-26 at 01:06 -0700, Mark Millard wrote:
> On 2017-Oct-26, at 12:40 AM, Henri Hennebert <hlh@restart.be> wrote:
> 
> > 
> > After a upgrade from r320599 to r324563, ntpd can't keep time for long.
> > After one hour, the clock run too fast.
> I'm running:
> 
> # uname -apKU
> FreeBSD pine64 12.0-CURRENT FreeBSD 12.0-CURRENT  r324743M  arm64 aarch64 1200051 1200051
> 
> Top shows:
> 
> /usr/sbin/ntpd -g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntpd.drift
> 
> It has been up for 3 days and date shows
> what I'd expect (local time). Also:
> 
> # ntpq -p 
>      remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
>  0.freebsd.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.000
> +96.226.123.195  128.138.141.172  2 u  486  512  377   53.512   -0.639   0.795
> +clock.xmission. 128.138.141.172  2 u   75  512  377   43.109   -0.005   1.301
> *chl.la          127.67.113.92    2 u  272  512  177   29.258    0.091   1.667
> +mirror1.sjc02.s 162.213.2.253    2 u   44  512  377   28.404   -0.632   2.297
> -mdnworldwide.co 216.218.254.202  2 u   95 1024  377   68.184   -3.070   1.488
> 
> 

What is in your /var/db/ntpd.drift file on that system?

-- Ian