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

[Andreas Schwarz]

On 14.11.17, Henri Hennebert wrote:
> On 11/13/2017 21:03, Mark Millard wrote:
>> 
>> So it looks like you are getting bad times from at
>> least 2 servers. Note that the other servers seem
>> fine as far as your e-mailed material goes.
>
> I believe that the clock of the Pine64+ is going too fast and that the 2 
> servers where polled and so show this offset/jitter. In an other 
> occurrence of this problem, if I wait long enough, all servers display 
> huge offset.

But they step not simultaneous to this offset (which is ~300s), why should some 
servers have such offset and others not?.

Can you provide your "ntpq -c rl" output?

If you disable the ntpd, what time drift do you measure per day?

> In a old version of Freebsd12, when dev.cpu.0.freq was accessible, the 
> problem appear when I force the frequency to 1200.


The dev.cpu.0.freq is already there in head/current.

root at pinelot:~ # sysctl dev.cpu.0
dev.cpu.0.freq_levels: 1200/-1 1008/-1 816/-1 648/-1 408/-1
dev.cpu.0.freq: 408
dev.cpu.0.%parent: cpulist0
dev.cpu.0.%pnpinfo: name=cpu at 0 compat=arm,cortex-a53
dev.cpu.0.%location:
dev.cpu.0.%driver: cpu
dev.cpu.0.%desc: Open Firmware CPU

root at pinelot:~ # uname -v
FreeBSD 12.0-CURRENT #0 r325561: Thu Nov  9 11:24:55 CET 2017     root at pinelot.schwarzes.net:/usr/obj/usr/src/arm64.aarch64/sys/PINE64-ASC


-asc