Re: Still seeing Failed assertion: "p[i] == 0" [ * i386 chroot on amd64 can get the failure on main 16 too * ]

Reply: Mark Millard : "Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ]"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Mark Millard <marklmi_at_yahoo.com>
Date: Thu, 20 Nov 2025 23:38:16 UTC

# 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