From nobody Thu Oct 7 21:11:45 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B59B712BC8A9 for ; Thu, 7 Oct 2021 21:11:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HQPCF1TM6z52km; Thu, 7 Oct 2021 21:11:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 197LBjiW010545 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 8 Oct 2021 00:11:48 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 197LBjiW010545 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 197LBj3h010544; Fri, 8 Oct 2021 00:11:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 8 Oct 2021 00:11:45 +0300 From: Konstantin Belousov To: Mark Johnston Cc: imb@protected-networks.net, freebsd-current Subject: Re: intermittent bsdtar/jemalloc failures Message-ID: References: <2908d747-8606-84d6-60b5-249c0d396b6b@protected-networks.net> <31be6e3a-f303-ce78-4dab-5dcc77ed0464@protected-networks.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.5 X-Spam-Checker-Version: SpamAssassin 3.4.5 (2021-03-20) on tom.home X-Rspamd-Queue-Id: 4HQPCF1TM6z52km X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, Oct 07, 2021 at 04:52:52PM -0400, Mark Johnston wrote: > 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_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. Do you have the issue with jemalloc(3), or the problem with imprecise TSC frequency as reported by CPUID leaf?