clock problem at PINE64

[Ian Lepore]

On Fri, 2017-09-22 at 20:59 +0900, YAMAMOTO Shigeru wrote:
> Hi, all,
> 
> Now I test 'make buildworld' on PINE64.
> 
> It is not success following error,
> 
> -------------------------------------------------------------------
> ---------
> --- Transforms/ObjCARC/ObjCARCAPElim.o ---
> <jemalloc>: jemalloc_arena.c:824: Failed assertion:
> "nstime_compare(&decay->epoch, &time) <= 0"
> c++: error: unable to execute command: Abort trap
> c++: error: clang frontend command failed due to signal (use -v to
> see invocation)
> FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 312559) (based on
> LLVM 5.0.0svn)
> Target: aarch64-unknown-freebsd12.0
> Thread model: posix
> InstalledDir: /usr/bin
> c++: note: diagnostic msg: PLEASE submit a bug report to https://bugs
> .freebsd.org/submit/ and include the crash backtrace, preprocessed
> source, and associated run script.
> c++: note: diagnostic msg: 
> ********************
> 
> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
> Preprocessed source(s) and associated run script(s) are located at:
> c++: note: diagnostic msg: /tmp/ObjCARCAPElim-2ca7c8.cpp
> c++: note: diagnostic msg: /tmp/ObjCARCAPElim-2ca7c8.sh
> c++: note: diagnostic msg: 
> 
> ********************
> *** [Transforms/ObjCARC/ObjCARCAPElim.o] Error code 254
> [...]
> -------------------------------------------------------------------
> ---------
> 
> It is caused by clock syncronization error.
> I use ntpd, but I cannot syncronize PINE64 clock.
> PINE64 clock shifts a few minutes.
> There is no problem at RaspberryPi 3 (arm64).
> 
> Does anyone know same problem?
> 
> Thanks,
> ---
> YAMAMOTO Shigeru <shigeru at os-hackers.jp>

If ntpd cannot keep the clock synchronized, there is something wrong
with the timecounter driver.  I don't have a pine64 to experiment with.
 Could you show the output of "sysctl kern.timecounter" and the output
of "ntptime" while ntpd is running and failing to keep the system on-
time.

-- Ian