Date: Thu, 26 Oct 2017 01:06:38 -0700 From: Mark Millard <markmi@dsl-only.net> To: Henri Hennebert <hlh@restart.be> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: PINE64 - 12.0-CURRENT r324563 - ntpd can't keep time Message-ID: <4BF75B1E-318C-414A-B5D4-4BA7D6578316@dsl-only.net> In-Reply-To: <d85f883f-84c2-5051-1996-2a0e73a2c1e7@restart.be> References: <d85f883f-84c2-5051-1996-2a0e73a2c1e7@restart.be>
next in thread | previous in thread | raw e-mail | index | archive | help
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=20
remote refid st t when poll reach delay offset =
jitter
=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
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
=3D=3D=3D
Mark Millard
markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BF75B1E-318C-414A-B5D4-4BA7D6578316>