clock problem at PINE64

[Henri Hennebert]

I'm running

FreeBSD norquay.restart.bel 12.0-CURRENT FreeBSD 12.0-CURRENT #0 
r320599M: Sat Jul  8 18:24:19 CEST 2017 
root at norquay.restart.bel:/usr/obj/usr/src/sys/NORQUAY  arm64

and with:

lrwxr-xr-x  1 root  wheel  12 Jun  7 17:58 /etc/malloc.conf -> tcache:false

I encounter no problem to build world and kernel.

Henri

PS I'm running with root on a zpool:


Filesystem                   Size    Used   Avail Capacity  Mounted on
rpool/ROOT/default           292G    1.3G    291G     0%    /
devfs                        1.0K    1.0K      0B   100%    /dev
fdescfs                      1.0K    1.0K      0B   100%    /dev/fd
rpool/home                   297G    6.0G    291G     2%    /home
rpool/tmp                    291G    1.5M    291G     0%    /tmp
rpool/usr/local              295G    3.4G    291G     1%    /usr/local
rpool/usr/obj                300G    8.5G    291G     3%    /usr/obj
rpool/usr/ports              292G    1.4G    291G     0%    /usr/ports
rpool/usr/ports/distfiles    292G    839M    291G     0% 
/usr/ports/distfiles
rpool/usr/src                293G    1.4G    291G     0%    /usr/src
rpool/var/audit              291G    1.3M    291G     0%    /var/audit
rpool/var/db                 291G    216M    291G     0%    /var/db
rpool/var/imap               291G     25M    291G     0%    /var/imap
rpool/var/log                291G     44M    291G     0%    /var/log
rpool/var/spool              305G     14G    291G     4%    /var/spool
rpool/ftp                    291G     92K    291G     0%    /var/spool/ftp
rpool/var/spool/imap         292G    974M    291G     0%    /var/spool/imap
rpool/var/spool/postgres     291G    324M    291G     0% /var/spool/postgres
rpool/squid                  292G    671M    291G     0%    /var/spool/squid
rpool/svn-FreeBSD            317G     26G    291G     8% 
/var/spool/svn-FreeBSD
rpool/var/tmp                291G     88K    291G     0%    /var/tmp
devfs                        1.0K    1.0K      0B   100% 
/usr/local/var/named/dev
devfs                        1.0K    1.0K      0B   100% /var/db/dhcpd/dev


On 09/22/2017 13:59, 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
> 
> 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?
> 
> Thanks,
> ---
> YAMAMOTO Shigeru <shigeru at os-hackers.jp>
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
>