On 12 Jul, Jason Evans wrote:
> On Tue, 11 Jul 2017 18:12:58 -0700 (PDT)
> Don Lewis <truck...@freebsd.org> wrote:
>> I'm trying to stabilize my new-ish Ryzen package build box.  I've run
>> into this error a couple of times:
>>   (<jemalloc>: jemalloc_arena.c:821: Failed assertion:
>> "nstime_compare(&decay->epoc h, &time) <= 0") most recently today
>> when building llvm40. It seems to happen somewhat randomly.  I don't
>> remember seeing it before the jemalloc 5.0.0 import.
>> What does it mean?  Any ideas on how I might mitigate the problem?
> This assertion verifies that a monotonic time source is not going
> backward in time.  jemalloc has code for mitigating the effects of
> non-monotonic time sources, but that code is only used for time source
> APIs that do not promise monotonic time.

Interesting ...

In my case TSC is being used as the timecounter.  I'm not seeing any
problems with ntp, and I'm not seeing any "calcru: runtime went
backwards" errors in the logs.  I should be able to write some test
code that specifically looks for this, but this error is pretty rare
and there are bigger problems at the moment.

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to