Upgrading from 25.07 to 25.07.1 causes a fatal trap 12 on boot.

w0w

@stephenw10 said in Upgrading from 25.07 to 25.07.1 causes a fatal trap 12 on boot.:

Ah so that worked for you?

Yes, and loader.conf.local works too, I just forgot that I have Filer package

stephenw10

@w0w said in Upgrading from 25.07 to 25.07.1 causes a fatal trap 12 on boot.:

I just forgot that I have Filer package

Ha, I've done that.

w0w

So I investigated a bit deeper and found that I can eliminate this problem by disabling the “Above 4G decoding” option in the BIOS. However, I now recall why it was enabled in the first place — pfSense refused to boot without it in some earlier version.

Anyway, it looks like

exec="staging_slop 268435456"

fixes the issue in both cases. But after discussing it further, I realized that this only works around the bug at the boot stage, not at the OS level. The suggested workaround is to also disable the use of the ACPI MCFG table and fall back to classic PCI config access by adding:

hw.pci.mcfg=0

There are other possible methods, such as manually patching the ACPI tables and loading them from disk, but this seems too complicated for little real benefit.

All of this explains why I occasionally had unexplained fatal traps on this motherboard, with a similar access range…

ldangpfng

Vendors have firmware bugs similar to this quite often, and usually you'd see the OS failing suddenly for no good reason. Falling back to PCI IO access for the config space will probably only allowing boot-through, but any time something allocates memory into that region, it won't be going to DRAM... leading to data corruption.

If you enable above 4GB decoding (and it successfully boots), there could be a change to the ACPI tables that the firmware generates.

In any case, we'll need to find a way to let FreeBSD know not to use that memory region for allocations.