Kernel panic during reboot after updating 26.7.7 -> 26.7.8_1

[filippo24]

Posting this just for the record this problem. For now, everything works fine now.

Setup: mini PC with Intel N150, 8 GB RAM, Intel i226 ports. OPNsense 26.7.7, with Zenarmor active only on the LAN interface (igc1).

What happened:

I updated from 26.7.7 to 26.7.8_1 (bootloader already updated).
During the automatic reboot, the system took longer than usual and a kernel panic occurred. The attached .txt crash log shows it happened while the old system was shutting down, and it mentions Zenarmor's netmap adapter on igc1 just before.

On the following boot (with monitor video)it panicked again with "panic: no init" (photo attached, i haven't ful txt log), and stayed stuck until I booted a previous snapshot from the console.

From the snapshot I ran the update again with Zenarmor disabled, and it rebooted without problems. I then re-enabled Zenarmor, rebooted, and everything is fine on 26.7.8_1.
(So unfortunately I don't know if it was really a zenarmor bug that maybe corrupted the current boot environment or if it was an isolated case)

Note: since I needed the firewall back up quickly, the attached crash log and photo are all I saved. I can't say whether this is reproducible, an isolated glitch, or really related to Zenarmor.

[OneTimePad]

Thanks for documenting this, it is useful for anyone running Zenarmor in netmap mode on igc interfaces. Booting the previous snapshot from the console is exactly why ZFS boot environments are worth having on a firewall. Disabling Zenarmor before an update and re-enabling it after the reboot seems a sensible habit until the cause is clear. It might also be worth attaching the crash log to a report with the Zenarmor team so they can check the netmap teardown path.