clock problem at PINE64

[Mark Millard]

On 2017-Sep-22, at 4:59 AM, YAMAMOTO Shigeru <shigeru at os-hackers.jp> 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
> 
> make[4]: stopped in /usr/src/lib/clang/libllvm
> 1 error
> 
> make[4]: stopped in /usr/src/lib/clang/libllvm
> *** [all_subdir_lib/clang/libllvm] Error code 2
> 
> make[3]: stopped in /usr/src/lib/clang
> 1 error
> 
> make[3]: stopped in /usr/src/lib/clang
> *** [cross-tools] Error code 2
> 
> make[2]: stopped in /usr/src
> 1 error
> 
> make[2]: stopped in /usr/src
> *** [_cross-tools] Error code 2
> 
> make[1]: stopped in /usr/src
> 1 error
> 
> make[1]: stopped in /usr/src
> *** [buildworld] Error code 2
> 
> make: stopped in /usr/src
> 1 error
> 
> make: stopped in /usr/src
> ----------------------------------------------------------------------------
> 
> 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?

It would help folks help you if you reported
what version of the system is running on the
Pine64. For example: on the one I have access
to it currently has:

# uname -apKU
FreeBSD pine64 12.0-CURRENT FreeBSD 12.0-CURRENT  r323676M  arm64 aarch64 1200044 1200044

(Note: It has been a long time since I've done a
buildworld or buildkernel on it. I'm not likely
to until ECHI USB is again working and can be the
place for the root file system. Mostly I do cross
builds from amd64 these days, even for ports.)


One thought is that having ntpd running might force
time to jump backwards periodically. Stopping ntpd
before the build and letting the clock progress on
its own until the build is done might keep the
time well ordered. (I'm only guessing that the
time jemalloc_arena.c is checking is tied to the
time that ntpd adjusts.)


===
Mark Millard
markmi at dsl-only.net