From nobody Mon Nov 17 15:38:09 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 4d9Bgl5bl9z6GRXN; Mon, 17 Nov 2025 15:37:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4d9Bgj1gR2z3K36; Mon, 17 Nov 2025 15:37:05 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 5AHFcA7O053467 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 17 Nov 2025 07:38:10 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 5AHFc9tI053466; Mon, 17 Nov 2025 07:38:09 -0800 (PST) (envelope-from fbsd) Date: Mon, 17 Nov 2025 07:38:09 -0800 From: bob prohaska To: Carl Shapiro Cc: Ronald Klop , freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Message-ID: References: <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org> <87ldkai9lu.fsf@panix.com> <877bvthymv.fsf@panix.com> 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-Spamd-Bar: - X-Spamd-Result: default: False [-1.04 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-0.99)[-0.995]; NEURAL_HAM_SHORT(-0.95)[-0.946]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_WWW(0.50)[]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; MISSING_XM_UA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org,freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[zefox.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[4] X-Rspamd-Queue-Id: 4d9Bgj1gR2z3K36 On Fri, Nov 14, 2025 at 05:04:10PM -0500, Carl Shapiro wrote: > bob prohaska writes: > > > Those files have been overwritten by restarting the buildworld sessions. > > They tend to be large and diffcult to synchronize with the .cpp and .sh > > files generated by the crash. It could be done if it's useful. > > At least from the perspective of debugging malloc(3), they'd be useful, > even if the files for reproducing the crash are not synchronized with > the std{err,out} output. For example, there might be other log messages > generated by jemalloc. > > I need a moment to look at the code and step through what it is doing on > FreeBSD but my first guess is that there might just be an incorrect > assumption about committed memory always coming back zeroed. That > should be true on 64-bit Linux when MADV_DONTNEED is used but not true > if another advice is used like MADV_FREE on either FreeBSD or Linux. It > is always possible that the kernel is mishanding some memory but I would > like to rule out jemalloc itself before pointing a finger there. Here is an example of both the buildworld.log file and the generated diagnostic files, which for some reason didn't include .sh and .cpp files. http://www.zefox.net/~fbsd/assertion_failure/hostname_www.zefox.org/buildworld.log http://www.zefox.net/~fbsd/assertion_failure/hostname_www.zefox.org/symbolizer-input-bcaebf http://www.zefox.net/~fbsd/assertion_failure/hostname_www.zefox.org/symbolizer-output-1aa401 This host's particular buildworld attempt has been going on for a long time, to the extent that world and kernel are mismatched: root@www:/usr/src # uname -KU 1600000 1500063 The immediate goal is to get them back in sync. Thanks for reading, bob prohaska