OPNsense Forum

English Forums => 25.1, 25.4 Production Series => Topic started by: j_s on March 25, 2025, 10:44:30 PM

Title: kernel panic after uploding config file.
Post by: j_s on March 25, 2025, 10:44:30 PM
I have an opnsense box I've been managing for about 5 years.  Supermicro C3758 based system.  I decided that since an upgrade failed long ago, when 25.1 came out I'd do a fresh install and import my config file.  While I was onsite I did a BIOS and IPMI update.  BIOS was factory defaulted and reconfigured appropriately.  System booted up 24.7.14 (whatever the last version was) without issues.

I then decided to install 25.1 which happened without issues.  I then uploaded the config file and first reboot was fine.  However if I reboot again (even if I change nothing) the box kernel panics while booting.

So I reinstalled 25.1 again and updated it to 25.1.3 without problems.  Did a few reboots and no problems.  Then I uploaded my config file and after 2 reboots it kernel paniced again on bootup.

Here's a screenshot of the panic.  Can anyone shed some light on this?  I *really* don't want to have to start over from scratch, it has quite a few VPN links and other things, and if this can give me a direction to go, I'd prefer to go that way before having to start with a clean config.

Note that I hadn't gotten to install any of the plugins yet because I was still in basic testing when I realized this problem.

Title: Re: kernel panic after uploding config file.
Post by: j_s on March 26, 2025, 01:35:44 AM
Quick little update...

I installed 24.7, updated it to 24.7.12_4 and imported the config file.  No issues.

Updated to 25.1, kernel panic.

So definitely something about 25.1 isn't thrilled with my 24.7 settings.
Title: Re: kernel panic after uploding config file.
Post by: patient0 on March 26, 2025, 11:42:26 AM
What component is crashing the kernel? It would be listed in the lines above the 'instruction point', not visible on the screenshot.
Title: Re: kernel panic after uploding config file.
Post by: j_s on March 26, 2025, 08:43:30 PM
Found the problem.  Added qat_load=YES to the system years ago.  Apparently it's no longer necessary or somehow is incompatible with FreeBSD 14.  In any case, system is now working fine on the latest version!