26.7.1_1 -> 26.7.2 Boot loop

[axsdenied]

Apologies in advanced as this post won't have a lot of useful info yet. Unfortunately, I don't have time this morning to figure out what happened but when upgrading to 26.7.2 I ended up in a boot loop.  I changed my BE back to 26.7.1_1 and was back up.

I have time later today to see what was going on and provide logs, but I wanted to post in case someone else was running into the same thing and might have more to share.

Quick addition, I do not have cpu microcode installed.

[adamklein]

same as here. kernel panic..

[franco]

Something really fishing going on here.

https://www.reddit.com/r/opnsense/comments/1vmeevo/comment/p395i6t/

Looking into it.

[nicospavlou]

Hello,

Same issue here!

Had to connect a screen and select option 6, to boot in old kernel.

If I can do something to troubleshoot just tell me.

Cheers,
Nicos

[meyergru]

Could that also have to do something with the old, buggy bootloader that triggered the os-microcode bug in the first place?

I updated all bootloaders beforehand and saw no problems on any system I upgraded.

[franco]

No it gets too far and chokes on an ifconfig call into the kernel to an interface that doesn't have counters allocated (or already freed).


Cheers,
Franco

[Labfox]

Hello,

I've got the same issue, on a practically blank OPNSense install. Same problem as everyone, the old kernel worked.

I've attached the crash dumps. I am using ZFS, and realtek-re-kmod. This may not be related, but the machine's CPU started overheating while in the boot loop, which never happenned before with this setup.

[Shoog]

Can confirm this behaviour on my system. Infinite bootloop.
At the first opnsense console if I select option 6. kernel and use the retained kernel.old everything works.
So it seems to be  dodgy kernel upgrade. This is an unusustainable solution since if opnsense does a reboot for any reason it goes back to a bootloop.

Hope this can be resolved quickly.