Kernel panic after upgrade

[Aloist]

I am happy to announce that I upgraded without problem from 18.7.10 to 19.1.1 through the normal upgrade process
on my Dell Poweredge R410 system.

I had feared upgrade problems due to report from others with similar Dell machines, but everything went fine.

[TheGrandWazoo]

Could it be a console issue with BIOS using VGA or UEFI using VGA instead of UEFI? I am trying many different combos to see if it might work (I bit time consuming).

I will see if I can copy the 18.7.x EFI files to 19.1.x and see if the issue disappears (or an Earth shattering Kaboom). It only a VM so I'll test anything right now.

[lattera]

@TheGrandWazoo

I think it is UEFI specific also. Which would make sense considering the broad spectrum of hardware and virtual platforms being impacted.

Looking at the contents of the ISO and comparing between 18.7 and 19.1. The files supporting EFI boot have been updated. Being /BOOT/BOOT1.EFI and /BOOT/LOADER.EFI

https://wiki.freebsd.org/UEFI
https://www.freebsdfoundation.org/freebsd-uefi-secure-boot/     Bit easier to understand but is looking at Secure Boot


Looks to be a FreeBSD or HardenedBSD issue?

Edit:  Tried a Hyper-V install using HardenedBSD-11-STABLE-v1100056.13-amd64-bootonly
Kernel Panic at the same point. Similar output, non responsive.

FYI: I'll be looking at the Hyper-V boot issue soon. I'm teaming up with a member of the HardenedBSD Foundation who relies on Hyper-V in parts of his infrastructure. As soon as our schedules match up, we'll be working this out together. :)

I'll report back as soon as I have more information. Thanks for your continued patience and support!

[peter008]

I can confirm that - with opnsense running as a VM under Hyper-V - is has something to to do with the bios of the server running the hypervisor: one old Siemens-Server of ours which just has MBR was upgrading the opnsense-VM to 19.x without problems, another Server with UEFI let the opnsense-VM freeze during updating as reported.

edit: forgot to mention that it made no difference to install the VM under Hyper-V as type 1 or 2

[senseivita]

So it isn't safe to upgrade yet? I just went through this for the first time, and several boots where it says "cd0" is waiting for something or the other way around, at that point I have to hard-restart the system.

The first time it showed me the kernel error I tried booting the old kernel and it showed me the cd0 error. I begged for it to come around if I tried again and luckily it did. Right away after booting it mentioned something about upgrading the system, but it actually went to 18.7.10_4 which in a way *is* upgrading because I think I was on 18.1, I pulled the image from a local file server to get started faster.

I took two snapshops, one with memory and backed up immediately after the system came up. I'm also getting a lot of this, even before the upgrade, is this normal?

[newsense]

That is a known issue that can happen sometimes.

Take a snapshot of the VM and update to 19.1.1 which is currently supported, 18.7 is now legacy

[bunchofreeds]

@lattera

Thanks for looking into this and let me know if I can help in any way. I run Hyper-V and can download and test OS installs and configurations easily. I'm not much good with FreeBSD or HardenedBSD though sorry, but will help where I can.

[bellyacres]

I've tried to update two machines and get a kernel panic on both.  Main machine is an AMD 3600 chip, single core, Athlon if memory serves.  Other is a Intel Duo Core.  When I set
hw.ibrs_disable=1
vm.pmap.pti=0
The Duo Core boots fine.

Have been unable to test the AMD box as it's our main box here.  Hardly mission critical, but with a teenager and friends depending on Internet for their lifeblood it becomes critical.

Posted mostly just to be able to follow this post, and see what the final solution is.

Thanks to all the devs for a great solution.  Your work doesn't go unappreciated!

Mike

[TheGrandWazoo]

@TheGrandWazoo

I think it is UEFI specific also. Which would make sense considering the broad spectrum of hardware and virtual platforms being impacted.

Looking at the contents of the ISO and comparing between 18.7 and 19.1. The files supporting EFI boot have been updated. Being /BOOT/BOOT1.EFI and /BOOT/LOADER.EFI

https://wiki.freebsd.org/UEFI
https://www.freebsdfoundation.org/freebsd-uefi-secure-boot/     Bit easier to understand but is looking at Secure Boot


Looks to be a FreeBSD or HardenedBSD issue?

Edit:  Tried a Hyper-V install using HardenedBSD-11-STABLE-v1100056.13-amd64-bootonly
Kernel Panic at the same point. Similar output, non responsive.

FYI: I'll be looking at the Hyper-V boot issue soon. I'm teaming up with a member of the HardenedBSD Foundation who relies on Hyper-V in parts of his infrastructure. As soon as our schedules match up, we'll be working this out together. :)

I'll report back as soon as I have more information. Thanks for your continued patience and support!

Thank you for looking into it.

I did try the 18.7.x efi files in the /boot and it did not help (didn't think it would) but worth a shot.

[buddwm]

Has any progress been made on this issue?  I'm on KVM and still can't seem to upgrade to the latest Opnsense version without getting the kernel panic.

[akron]

We hold off upgrade on production Instances for now.

is definitely an issue with HardenedBSD / OPN 19.1 UEFI only, BIOS works well


hopefully there will be a solution soon

at the moment several hardware, VMware and Hyper-V UEFI instances get the failed trap error

[schnipp]

I have migrated from 18.7.10_4 to 19.1.2. The migration process worked without any problems.

My system:

• Board: Supermicro A2SDi-4C-HLN4F
• RAM: 8 GB
• Sys: 64 Bit

Many thanks to all the developers and contributors who made this version possible  :D

[astoklas]

Is there an update on this?
I try a fresh install with a i7-8700 CPU/Shuttle XV310 and see the same kernel panic.
The suggested boot options did not help

Edit:
This is a fresh install on a pyhsical device - no hypervisor involved.
But it is the exact same kernel panic.

Any advise?

[RNHurt]

The latest update is 19.1.2 (Feb. 28th) but the release notes don't mention anything about fixing a kernel panic.  :(

[lattera]

If the price is right, I will be looking to acquire a budget-friendly system on which to run Hyper-V. HardenedBSD's budget for this kind of thing would be $500 USD.

Just a quick reminder that HardenedBSD accepts donations, both monetary and hardware. We appreciate all contributions of any kind.