Date: Fri, 22 Sep 2017 11:04:22 -0600 From: Ian Lepore <ian@freebsd.org> To: YAMAMOTO Shigeru <shigeru@os-hackers.jp>, freebsd-arm@freebsd.org Subject: Re: clock problem at PINE64 Message-ID: <1506099862.73082.84.camel@freebsd.org> In-Reply-To: <20170922.205941.1509653942908658214.shigeru@os-hackers.jp> References: <20170922.205941.1509653942908658214.shigeru@os-hackers.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1506099862.73082.84.camel>