PINE64 - 12.0-CURRENT r324563 - ntpd can't keep time

[Henri Hennebert]

On 10/26/2017 16:57, Ian Lepore wrote:
> On Thu, 2017-10-26 at 01:06 -0700, Mark Millard wrote:
>> On 2017-Oct-26, at 12:40 AM, Henri Hennebert <hlh at 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?
> 
[root at norquay ~]# cat /var/db/ntp.drift
29.760

To create it, after this problem I stop ntpd, remove /var/db/ntp.drift 
and restart ntpd.

Henri