24.11 ---> 25.07 page fault while in kernel mode

MacG32

This happened with the beta and RC also. My system is: https://pcpartpicker.com/list/qj73Dx The only difference is a 16GB memory stick of the same brand with the same timings. If you need anything else, please let me know. I'm back on 24.11. Thank you.

stephenw10

It's an upstream bug in the firmware loader: https://redmine.pfsense.org/issues/16237

Remove/disable the wifi card or apply the workaround shown there.

MacG32

Thank you Stephen! Will do.

what3ver

Hi there,

I am having the same problem when upgrading form 24.11 to 25.07. The boot process stops with a fatal trap 12 error and goes into panic mode.

The culprit appears to be the Intel Wireless card (AC 3165) installed on the host. Is there any other solution than deactivating the device in the BIOS? I am using the Wifi card to connect to a backup MiFi in case my main Internet service is disrupted.

stephenw10

Hmm, if you need wifi it would be better to use a different wifi card there. Or better yet connect via cable.

But are you able to test anything? I might have something to try there.

what3ver

Yes, I may be able to install another NIC and connect the MiFi via cable. But are you saying that the Intel WiFi cards are too old and therefore unsupported in the newer BSD versions?

stephenw10

Nope I'm saying they require loading firmware into the card and the upstream firmware API is broken which is what you're seeing. Other wifi hardware/drivers like Atheros (ath(4)) do not and hence work fine in 25.07:

[25.07-RELEASE][admin@6100.stevew.lan]/root: pciconf -lv ath0
ath0@pci0:17:0:0:	class=0x028000 rev=0x01 hdr=0x00 vendor=0x168c device=0x0030 subvendor=0x168c subdevice=0x3112
    vendor     = 'Qualcomm Atheros'
    device     = 'AR93xx Wireless Network Adapter'
    class      = network

But this failing because it can't find the firmware and hits the bug. We may be able to work around it. Let me see if I can test something....

stephenw10

Hmm, nope. Even providing the firmware separately still hits the bug. As far as I can see this will remain until it's fixed upstream.