From nobody Fri Nov 14 07:16:56 2025 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 4d77k36TJ0z6H71M; Fri, 14 Nov 2025 07:16:59 +0000 (UTC) (envelope-from cshapiro@panix.com) Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) (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 4d77k24Khwz3Xqn; Fri, 14 Nov 2025 07:16:58 +0000 (UTC) (envelope-from cshapiro@panix.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=panix.com header.s=panix header.b=NmuO2Dnt; dmarc=pass (policy=none) header.from=panix.com; spf=pass (mx1.freebsd.org: domain of cshapiro@panix.com designates 166.84.1.89 as permitted sender) smtp.mailfrom=cshapiro@panix.com Received: from css-ThinkPad-T14s-Gen-2a (c-73-231-159-157.hsd1.ca.comcast.net [73.231.159.157]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4d77k13dScz48fW; Fri, 14 Nov 2025 02:16:57 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix; t=1763104618; bh=HNr+H9g0HLCRPAA61UIozIZwEcxB2yeEpYQTKD2YzGY=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=NmuO2DntFZANBQFCEsRKcyxE7YTuwZO9qXhRdU9euejIx9yeZlzzm9gPRN5TQitbj 3hHpq/9fFObB65EbAudGxjtIKB8vO7dEn5jWU8Rt81DlrcVG3QC8CLsMALL1DhVz+k o8DPYWGorknJeQM0HStibwjsCyh+hiFH0KTAXVdY= From: Carl Shapiro To: bob prohaska Cc: Ronald Klop , freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld In-Reply-To: (bob prohaska's message of "Thu, 13 Nov 2025 06:41:49 -0800") References: <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org> <87ldkai9lu.fsf@panix.com> Date: Thu, 13 Nov 2025 23:16:56 -0800 Message-ID: <877bvthymv.fsf@panix.com> User-Agent: Gnus/5.13 (Gnus v5.13) 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 X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.14 / 15.00]; DWL_DNSWL_LOW(-1.00)[panix.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.94)[-0.936]; DMARC_POLICY_ALLOW(-0.50)[panix.com,none]; R_DKIM_ALLOW(-0.20)[panix.com:s=panix]; R_SPF_ALLOW(-0.20)[+ip4:166.84.1.64/26:c]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[166.84.1.89:from]; RCVD_IN_DNSWL_LOW(-0.10)[166.84.1.89:from]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org,freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[panix.com:+] X-Rspamd-Queue-Id: 4d77k24Khwz3Xqn bob prohaska writes: > All the assertion failures I've seen have been in the clang libraries during > buildworld. They appear to happen in a variety of cases, indicated by the > different .sh and .cpp filenames found in the files under > http://www.zefox.net/~fbsd/assertion_failure/ Do you have the stdout and stderr of the build somewhere in there as well? The make(1) invocation in the readme file shows its output being redirected to a file. The assert you mentioned in the subject of your e-mail message, which I also saw in the readme file, could come from jemalloc. See these lines of code for the context https://github.com/facebook/jemalloc/blob/dev/src/extent.c#L805-L814 That assertion will be tripped when jemalloc sees non-zero memory that it expects to be zeroed. See for example https://github.com/facebook/jemalloc/blob/dev/src/pages.c#L55-L106 Looking at the code, my hypothesis would be that jemalloc thinks it's committing memory for the first time but the memory is coming back with non-zero data. Just curious, but is over-commit enabled on your system? Here is the signal jemalloc is using to check https://github.com/facebook/jemalloc/blob/dev/src/pages.c#L729-L737 > The failures are random in the sense that restarting buildworld either > produces a new assertion failure in a different library or completion. > > It isn't obvious how to capture a stack trace, if you can provide guidance > I'll give it a try. As is, buildworld simply stops, the machine does not > crash. It might be captured for you already? I noticed files with names containing "symbolizer-input" and "symbolizer-ouput" like this one http://www.zefox.net/~fbsd/assertion_failure/hostname_pelorus.zefox.org/symbolizer-output-7282d9 and the output files contain a stack trace like this llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) /usr/src/contrib/llvm-project/llvm/lib/Support/Unix/Signals.inc:731:7 llvm::sys::RunSignalHandlers() /usr/src/contrib/llvm-project/llvm/lib/Support/Signals.cpp:0:5 SignalHandler /usr/src/contrib/llvm-project/llvm/lib/Support/Unix/Signals.inc:0:3 handle_signal /usr/src/lib/libthr/thread/thr_sig.c:0:3 Any idea who or what is creating those files and when?