Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Oct 2021 22:39:48 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        imb@protected-networks.net
Cc:        freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: intermittent bsdtar/jemalloc failures
Message-ID:  <YV9NBCZOnpefRNXP@kib.kiev.ua>
In-Reply-To: <2908d747-8606-84d6-60b5-249c0d396b6b@protected-networks.net>
References:  <2908d747-8606-84d6-60b5-249c0d396b6b@protected-networks.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 07, 2021 at 03:28:44PM -0400, Michael Butler via freebsd-current wrote:
> While building a local release bundle, I sometimes get bsdtar failing (and
> dumping core) as follows below. Worse, as can be seen below, it doesn't stop
> the build unless I happen to notice and it yields an incomplete package.
> 
> a usr/src/sys/netgraph/ng_checksum.h
> a usr/src/sys/netgraph/ng_message.h
> a usr/src/sys/netgraph/ng_echo.c
> a usr/src/sys/netgraph/ng_gif.h
> <jemalloc>: jemalloc_arena.c:747: Failed assertion:
> "nstime_compare(&decay->epoch, &time) <= 0"
> Abort trap (core dumped)
> sh /usr/src/release/scripts/make-manifest.sh *.txz > MANIFEST
> 
> What causes this? Build machine is a 2x4-core Intel box with ZFS
> file-systems all around. I tried stopping NTPD temporarily but the failures
> persist .. sometimes :-(
> 
> I've seen this at different points in the archiving process so it doesn't
> seem specific to building kernel.txz.

What timecounter do you use? Perhaps show the whole output from
sysctl kern.timecounter.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YV9NBCZOnpefRNXP>