Kernel panic after upgrade

[TheGrandWazoo]

Hi,

I've spend more than a day trying to replicate the issue and tracking it's origin, since it doesn't occur on all EUFI boot systems.
Virtualbox for example boots without issues in UEFI mode, on Parallels (osx) I was able to find the crash as well .

Code: [Select]

fpuinit_bsp1 () at /usr/src/sys/amd64/amd64/fpu.c:241
fpuinit () at /usr/src/sys/amd64/amd64/fpu.c:277
0xffffffff810adb3b in hammer_time (modulep=<optimized out>, physfree=<optimized out>) at /usr/src/sys/amd64/amd64/machdep.c:1801
0xffffffff80316024 in btext () at /usr/src/sys/amd64/amd64/locore.S:79

Let me make one thing very clear, none of our systems suffer from this issue, a lot of people where actively involved during the beta stages up to 19.1 using all kinds of hardware.

I've seen a couple of people complaining, nagging, not being to **any** help to anyone.
I understand you have an issue, we all do, but... there are always alternatives, using other types of setups, being involved earlier and actively helping improving the system.
Don't forget, if your setup fails and you have done nothing to prevent that from happening, it's still your issue.... nobody got paid to solve it for you.

The patch [1] available might not be the final fix, nor will it fix all issues in the world, but it looks promising.

I would like to thank Franco, Shawn and anybody involved in actually pinning this issue down.

A kernel with debug options enabled is available on our website [2], but if Franco has some time available he can probably move it to a better spot, maybe build some iso with kernel.


Best regards,

Ad

• https://github.com/HardenedBSD/hardenedBSD-stable/commit/77a10c68ac3bf9cd0da50bd537dab858462c07f7
• https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/sets/kernel-19.7.a_25-amd64.txz

UPDATE: I copied the 19.7 kernel mentioned above in the #2 link to the /boot/kernel/kernel of the 19.1.2 install (well mine it 19.1-netmap) and all is well in the world. Boots with NO issues with EFI or BIOS firmware.

Thank you guys. Let me know if I can continue to help.

Kev

[franco]

franco complained about not being payed enough for his work, the admin wants an Intel NUC from the community for 550 € just to test Hyper-V.

I have never been paid for *any* work on OPNsense. You're at best misleading, at worst deliberately trying to "get back at" me for telling you to stop imposing your personal beneficial view on the project. You can apologise for your toxic comment or leave for good.


Cheers,
Franco

[bunchofreeds]

This post is becoming a bit annoying.

Lots of helpful information to resolve the issue, but peppered with some pretty nasty feedback and grudges.

I would really like to have this resolved, pretty sure we all do.

Can we please focus on the fix and respect those who are helping to achieve that

 

[peter008]

You can apologise for your toxic comment ...

Good joke !

[franco]

Not a joke. End of the line for you.


Cheers,
Franco

[peter008]

Not a joke. End of the line for you.

...said the king !

[franco]

You're still here. I'm asking you to leave.

[peter008]

ok, i just wanted to go back to planet earth anyway.

[franco]

Please leave it. This is your last warning.

[peter008]

 

[franco]

I've disabled your ability to post. You can ask for an unlock via PM. The reason given was:

> Continued attacks on forum members and ignoring moderator requests


Cheers,
Franco

[akron]

I'm a peaceful person however as an enterprise user it amazes me the quantity of bashers and shills in this forum. (Almost same rethoric as pfsense decadent times)

First of all everyone is free to choose what is necessary to deliver the job.

Coming from Cisco and Dell background, spending 15000€ per device in useless hardware for many years because of the BIG brand and BIG things and the BIG names, still useless for the price TAG.

Second this is an open source, community fuelled project, actually one of the best projects in terms of performance and features globally available.

If one is hurt about these bugs, please open your wallet and buy the iPhone of firewalls, CISCO, PALO ALTO, Fortigate and so on and be happy.

No one can demand or snow flake around because there is a bug, I've been running enterprise hardware from Deciso moving away from Cisco and never once been disappointed. Franco helped many times fixed bugs, and as an active user contributed many times monetarily to the project and will continue to do so, because it pays the bills around here.

Also running dozens of virtual workloads, from time to time there is a bug here and there, however one is responsible for the R&D and as AD mentioned, also planning proper upgrade procedures and regressions is the user responsibility.

No serious enterprise company sysadmin cries around because there is a bug in this or that open source project, maybe is fine crying around when Cisco fails, or palo alto but not open source.

To conclude, this projects saved thousands of pounds to many organizations across the scene and this types of toxic comments undermine the project vision, so no point escalating it going further.

[marjohn56]

Couldn't have put it better myself.... 👍👍👍

[monstermania]

@akron
Well said!

BTW: My company uses a commercial UTM-Solution for many years now. The utm is fully supported only on her own hw! So, if you want full support you have to buy the appliance!
Of course, the utm had never had any boot problems. 

[golebole]

UPDATE: I copied the 19.7 kernel mentioned above in the #2 link to the /boot/kernel/kernel of the 19.1.2 install (well mine it 19.1-netmap) and all is well in the world. Boots with NO issues with EFI or BIOS firmware.

Is it possible to update the kerne to this one in the next 19.1 version ?