25.11: Fatal trap 12 on reboot

stephenw10

Yup this new panic you;re seeing is specific to the debug kernel. We are fixing that so we will then be able to see the reboot issue.

w0w

@stephenw10
I am very grateful for your help and support!

stephenw10

No worries. I'm happy you're able to test an early dev snaphot. Finding these issues earlier makes it much easier for us.

stephenw10

Ok are you able to try a custom debug kernel here?

https://nc.netgate.com/nextcloud/s/Rj5F5K2qb4ps72R

If so rename the /boot/kernel folder to a backup then extract that .tgz into /boot and reboot into the new kernel.

w0w

@stephenw10 said in 25.11: Fatal trap 12 on reboot:

rename the /boot/kernel folder

You mean /boot/kernel.debug?

stephenw10

No I mean the kernel folder in boot. That tgz contains a complete replacement for that with the new debug kernel and all the modules for it.

stephenw10

So for example, assuming you uploaded the file via the GUI:

[25.11-DEVELOPMENT][admin@4860.stevew.lan]/root: mv /tmp/kernel_nd6_ifa_alloc.tgz /boot
[25.11-DEVELOPMENT][admin@4860.stevew.lan]/root: mv /boot/kernel /boot/kernel_old
[25.11-DEVELOPMENT][admin@4860.stevew.lan]/root: tar -xzf /boot/ker
[25.11-DEVELOPMENT][admin@4860.stevew.lan]/root: cd /boot
[25.11-DEVELOPMENT][admin@4860.stevew.lan]/boot: tar -xzf /boot/kernel_nd6_ifa_alloc.tgz

Then reboot and you should have:

[25.11-DEVELOPMENT][admin@4860.stevew.lan]/root: uname -a
FreeBSD 4860.stevew.lan 15.0-PRERELEASE FreeBSD 15.0-PRERELEASE #0 mjg-nd6-ifa_alloc-n256484-038e2217543a: Mon Sep 29 15:06:18 UTC 2025     root@pfsense-build-01.netgate.com:/usr/obj/usr/home/mjg/repos/FreeBSD-src/amd64.amd64/sys/pfSense-DEBUG amd64

w0w

@stephenw10

Uploaded primary29.zip

stephenw10

Nice! That looks like something we can work with. Thanks!

w0w

@stephenw10
Just for your information, the secondary firewall has exactly the same dump, and that’s good, I suppose.

stephenw10

Yes it's exactly what you want to see in a crash report. If you get one.

Here is a test kernel that should have that fixed. Same procedure as before;

https://nc.netgate.com/nextcloud/s/Sri33J8L5tZZQ9K

w0w

So far, so good, no crashes, thanks.

w0w

@stephenw10
I’ve opened another thread about the Virtual IP (VIP) issue I mentioned earlier.
https://forum.netgate.com/topic/198976/incomplete-vip-configuration-on-boot-causing-carp-failure-since-25.07-beta