Kernel panic after upgrade

[myksto]

What happens when you set:

hw.ibrs_disable=1
vm.pmap.pti=0

Where do we have to set those parameters?

[greY]

Those parameters are at System > Settings > Tunables
...you have to modify them there.

[myksto]

Those parameters are at System > Settings > Tunables
...you have to modify them there.

Ok but, wait a minute please.
I understand that those parameters are to be used in case of kernel panic.
They can be set in the GUI.
In case of kernel panic system doesn't boot so I can I change those parameters in the GUI?
Maybe they have to be changed before the ugrade?
I'm on 18.7 yet and I can't find those parameters in System -> Settings -> Tunables: maybe thare are to be addedd?
Can you please try to explain exactly what to do?

Thanks anche cheers,
Michele.

[lattera]

You can also set them for only the current boot by escaping to the loader prompt in the bootloader. So when you see the OPNsense boot menu, hit select option 3, then type:

set vm.pmap.pti="0"
set hw.ibrs_disable="1"
boot

Doing this does disable Meltdown/Spectre mitigations. But only for that one boot just to see if that's the problem.

[greY]

how ever this settings did not helped me    (see attachment)

[bunchofreeds]

These switches do not work for me either unfortunately. Running them at boot after confirming they are set with 'show'

For me this is what works and doesn't - All under Hyper-V 2019

19.1 Gen 2 - Fails (Have tried all manner of boot time switches offered here so far)
19.1 Gen 1 - Works
18.7 Gen 2 - Works
18.7 Gen 1 - Works

From what I understand, Gen 1 Hyper-V Hardware virtualisation boots with BIOS and IDE. Gen 2 Boots with UEFI and SCSI

https://www.serverwatch.com/server-tutorials/hyper-v-2012-r2-pros-and-cons-of-generation-1-vs.-generation-2-vms.html

[newsense]

how ever this settings did not helped me    (see attachment)

Would this apply to a Virtualbox 6.0.4 VM which ran the 18.x series last year without issues on a Win10 host ? The system is powered by a rather old Athlon 2 with 3 cores + HT and trying to boot 19.1 following the 18.7.10_4 reboot completely freezes the host machine.

[Aloist]

Did anyone succeed with booting 19.1 on a Dell Poweredge R410?
I am reluctant to upgrade not knowing that it will work on my hardware.

A question in that context: is there a way to make a full backup of all files, before an upgrade attempt, and go back in case the upgrade fails?

I assume just booting an older kernel might not work, as a lot of system files, besides the kernel, will have been replace by the upgrade, and they may no longer work with the older kernel.

[newsense]

You can always boot 19.1 from a stick in live mode and test things out without changing anything on the box.

If things look good you can even do a new install importing the config in the process.

[myksto]

I've two Dell Power Edge 1950 and I am reluctant to upgrade not knowing that it will work on my hardware too.

Is there any way to avoid this kernel panic?

I saw that version 19.1.1 has been released: will it solve this problem also?

Cheers,
Michele.

[newsense]

The post above yours would have been a good starting point...

[myksto]

The post above yours would have been a good starting point...

You mean your advice about using a pen drive to test the hardware or even reinstall the server by zero?
Unfortunately my servers need to work 7/24 and I can't do test with them.

I'm hoping some guru will find a "better" solution. 

Cheers,
Michele.

[newsense]

The better solution is a proper testing environment. If all your options are "Testing in Production" then it will always be a gamble and no 'guru' will ever be able to help.

The most appropriate way to do it if production is the only option would be to engage the vendor support team - probably Deciso in this case ? - to assist with the upgrade process.

[Aloist]

You can always boot 19.1 from a stick in live mode and test things out without changing anything on the box.

If things look good you can even do a new install importing the config in the process.

How do I get my current configuration onto this boot stick?

And what if the boot problems of the new FreeBSD release are related to the Raid controller or Raid configuration in the Dell hardware? That will not become apparent by booting from a stick, when the disks are not involved.

[myksto]

You can always boot 19.1 from a stick in live mode and test things out without changing anything on the box.

If things look good you can even do a new install importing the config in the process.

How do I get my current configuration onto this boot stick?

And what if the boot problems of the new FreeBSD release are related to the Raid controller or Raid configuration in the Dell hardware? That will not become apparent by booting from a stick, when the disks are not involved.

Infact booting with a usb stick not involving server hardware is almost no sense and of no use.