Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Nov 2025 15:38:16 -0800
From:      Mark Millard <marklmi@yahoo.com>
To:        Konstantin Belousov <kib@freebsd.org>, Michal Meloun <mmel@freebsd.org>, Warner Losh <imp@bsdimp.com>, freebsd-arm@freebsd.org, freebsd-current@freebsd.org
Cc:        bob prohaska <fbsd@www.zefox.net>, Adrian Chadd <adrian@freebsd.org>, Carl Shapiro <cshapiro@panix.com>, Ronald Klop <ronald@freebsd.org>
Subject:   Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ]
Message-ID:  <32C6B8A3-E390-48C8-8454-753511ADDF57@yahoo.com>
In-Reply-To: <265F191D-5400-4A9D-BE99-F060770B5DED@yahoo.com>
References:  <aOvTG-20QRJtJJwf@int21h> <aRXuLTN4hkGykHIl@www.zefox.net> <877bvthymv.fsf@panix.com> <aRdJ5xYeKEmhuIgh@www.zefox.net> <ouy1pm0nued.fsf@panix3.panix.com> <aRtBYaaa0n3_lwar@www.zefox.net> <CAJ-Vmo=TbT7nD7rBrNnq3cutwMp9f7WXtQ-k9mUBne5ht4zGWg@mail.gmail.com> <13E753F4-84F8-4ADB-96B6-908897D6971C@yahoo.com> <3174F751-9853-4697-B0C0-98B54518A69F@yahoo.com> <E634EF40-545C-44D7-9050-83D18090F6EB@yahoo.com> <BA9E6753-F895-46C8-95F3-C3C8B1692033@yahoo.com> <A27FE12B-0074-4403-81F7-8A224CC96CC8@yahoo.com> <D17E06B0-4591-45F2-8C46-70D94E371941@yahoo.com> <463AC500-C7C7-43FB-B5EF-332CEBA3D944@yahoo.com> <F9590F2F-0CB0-4AA9-870E-A97D45C1EC01@yahoo.com> <3E0D6079-0F5B-463E-94D4-37506A837D33@yahoo.com> <05479AC8-C8EB-42A3-9A54-2CAF687023D2@yahoo.com> <422A55DB-E005-4DA5-89F3-52879F35F6A4@yahoo.com> <F1F45DCF-609B-4C15-A799-5BE757F43EB2@yahoo.com> <87fra9fd4m.fsf@panix.com> <CB53A94B-8C78-4BCC-AD99-66DE833C749D@yahoo.com> <878qg1f8wz.fsf@panix.com> <265F191D-5400-4A9D-BE99-F060770B5DED@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help

# cd /usr/src/

# env WITH_META_MODE= make -j10 buildworld
. . .
Building /usr/obj/usr/src/i386.i386/lib/clang/libclang/CodeGen/CGExprScalar.pico
<jemalloc>: /usr/src/contrib/jemalloc/include/jemalloc/internal/ehooks.h:170: Failed assertion: "p[i] == 0"
Building /usr/obj/usr/src/i386.i386/lib/clang/libclang/CodeGen/CGGPUBuiltin.pico
Abort trap (core dumped)
*** [CodeGen/CGBuiltin.pico] Error code 134

The 7950X3D system has 32 FreeBSD cpus (16 cores), 192 GiByTes of RAM,
Optane PCIe Storage media.

# uname -apKU
FreeBSD 7950X3D-UFS 16.0-CURRENT FreeBSD 16.0-CURRENT main-n281922-4872b48b175c GENERIC-NODEBUG amd64 amd64 1600004 1600004

But in the chroot:

# uname -apKU
FreeBSD 7950X3D-UFS 16.0-CURRENT FreeBSD 16.0-CURRENT main-n281922-4872b48b175c GENERIC-NODEBUG i386 i386 1600004 1600004

For that particular system I used:

# grep physmem /boot/loader.conf
hw.physmem="5G"

It resulted in:

# dmesg -a | grep 'memory *='
real memory  = 137434759168 (131068 MB)
avail memory = 2708901888 (2583 MB)

My odd top hack for monitoring and reporting
various "Max(imum) Obs(erved)" figures shows:

1914Mi   MaxObsActive
821116Ki MaxObsWired
2585Mi   MaxObs(Act+Wir+Lndry)
1617Mi   MaxObsSwapUsed,
3488Mi   MaxObs(Act+Lndry+SwapUsed),
4166Mi   MaxObs(A+Wir+L+SU) [at such a time: 4193Mi (A+W+L+SU+InAct)]

I had to build main 16 for the i386 myself, based on the /usr/src/
from the official pkgbase system in use: such is no longer available.
I did not make changes to allow SIGABRT to core dump.

-j8 did not fail. -j12 ran out of RAM+SWAP.

===
Mark Millard
marklmi at yahoo.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32C6B8A3-E390-48C8-8454-753511ADDF57>