Date: Thu, 7 Oct 2021 16:52:52 -0400 From: Mark Johnston <markj@freebsd.org> To: imb@protected-networks.net Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: intermittent bsdtar/jemalloc failures Message-ID: <YV9eJLPdHSWtl5hh@nuc> In-Reply-To: <31be6e3a-f303-ce78-4dab-5dcc77ed0464@protected-networks.net> References: <2908d747-8606-84d6-60b5-249c0d396b6b@protected-networks.net> <YV9NBCZOnpefRNXP@kib.kiev.ua> <31be6e3a-f303-ce78-4dab-5dcc77ed0464@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 07, 2021 at 04:18:28PM -0400, Michael Butler via freebsd-current wrote: > On 10/7/21 15:39, Konstantin Belousov wrote: > > 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. > > imb@vm01:/home/imb> sysctl kern.timecounter > kern.timecounter.tsc_shift: 1 > kern.timecounter.smp_tsc_adjust: 0 > kern.timecounter.smp_tsc: 1 > kern.timecounter.invariant_tsc: 1 > kern.timecounter.fast_gettime: 1 > kern.timecounter.tick: 1 > kern.timecounter.choice: ACPI-fast(900) HPET(950) i8254(0) TSC-low(1000) > dummy(-1000000) > kern.timecounter.hardware: HPET > kern.timecounter.alloweddeviation: 5 > kern.timecounter.timehands_count: 2 > kern.timecounter.stepwarnings: 0 > kern.timecounter.tc.ACPI-fast.quality: 900 > kern.timecounter.tc.ACPI-fast.frequency: 3579545 > kern.timecounter.tc.ACPI-fast.counter: 16124892 > kern.timecounter.tc.ACPI-fast.mask: 16777215 > kern.timecounter.tc.HPET.quality: 950 > kern.timecounter.tc.HPET.frequency: 14318180 > kern.timecounter.tc.HPET.counter: 1883995229 > kern.timecounter.tc.HPET.mask: 4294967295 > kern.timecounter.tc.i8254.quality: 0 > kern.timecounter.tc.i8254.frequency: 1193182 > kern.timecounter.tc.i8254.counter: 57 > kern.timecounter.tc.i8254.mask: 65535 > kern.timecounter.tc.TSC-low.quality: 1000 > kern.timecounter.tc.TSC-low.frequency: 1413153007 > kern.timecounter.tc.TSC-low.counter: 2352002295 > kern.timecounter.tc.TSC-low.mask: 4294967295 > > I overrode the default selection of counter-type as NTPD drifted so > badly as to require stepping almost hourly :-( Could you show output from # kldload cpuctl # cpucontrol -i 0x15 /dev/cpuctl0 # cpucontrol -i 0x16 /dev/cpuctl0 as well as a copy of the dmesg after a boot? I am looking at a similar problem currently.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YV9eJLPdHSWtl5hh>