Kernel panic after upgrade

[RGijsen]

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.

While you guys are probably running a *nix variant, any Windows 10 Pro machine (with a fairly recent Intel CPU) will do for testing. My old Intel 5i5RYH NUC, with a i5 5250u cpu suffers the same, with an OPNsense test-VM on Hyper-V, which is available in 10 pro. Server 2016 / 2019 more or less equals Windows 10 (resp. 1607 and 1809 builds). So you wouldn't need an expensive box to test.

[akron]

I don't think is necessary, a simple laptop with windows 10 would do the job, however for a more professional environment I can provide a remote LAB with Hyper-V and ESXi where you can spin as many VMs as you wish to help test.

this UEFI bug plagues some baremetal, Hyper-V Gen 2 UEFI and ESXi UEFI VMs and me as well other dozens of users have interest to help get this fixed as we use OPNsense in productions environments.

Cheers

[golebole]

Hi,

is the problem solved with the new update or still the same?

Topic has 3000 Views, so I think the most important topic at the moment .

Thanks
Christian

[jmeyer]

Hi,

I have the same Issue with a clean install of OPNsense 19.1 on a new DELL PowerEdge R340 Server.

Using the Boot Options and trying the different Images (nano, dvd,vga) did not help. Also tried enabling and disabling UEFI in the BIOS does not helped.

kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
Stopped at fpuinit+0x179: orb $0x10,ctx_switch_xsave+0x3

[RGijsen]

For shits and giggles I created a Hyper-V gen1 VM, installed 19.1 and updated to the latest-as-of-yet 19.1.2, ran fine under gen1. Mounted the disk under a Gen2, and *poof*, still crash. So no, 19.1.2 didn't fix it, although we would have already known that.

While I totally understand the limited resources of the team (all respect for them!), it's getting hard for us to rely on this given that 18.x is now EOL (ie not secure in my book) but 19.x doesn't run at all.

[franco]

Please sponsor the project if you feel we're not doing enough. <3

[peter008]

No offense, but I think you should not be so sensitive.

It is very annoying indeed if you recommend updating to a version (19.x) which constantly crashes the total system of the users, while on the other site you take out a running (18.x) of support.

Besides you did not make it clear for days that the freezes were based on the update, so maybe I was not the only one who tried to find the mistake for hours on his own system.

After all it was quite a challenge to eliminate these mistakes and get back to running systems.

We all appreciate your work, but, sorry, those kind of bugs suck.

[franco]

I know. Everybody expects work here and there. And we get constantly side-tracked by fixing operating system and third-party related issues while pulling off progress for the software that we actually do write:

https://github.com/opnsense/core/pulse/monthly

I have to be sensitive, because people ask for a lot without realising that not helping us move forward doesn't work well for them.


Cheers,
Franco

[franco]

I have actually said this before. Users that do not like this particular issue ask us to:

Never change the operating system version.

We cannot make that choice. FreeBSD very quickly and almost deliberately destroys usability of 11.x not officially supported.

So we have no choice but to upgrade and when users don't like the changes we ship but did not want to have in the first place the concerns are voiced in the wrong direction, because we're simply caught in the middle.

So between not upgrading the operating system and upgrading it we will always have to bite the bullet and upgrade until somebody comes along and provides an OS that will:

* Push long term security updates and third-party ports updates
* Provides timely updates for new hardware
* Provided 100% hardware compatibility

Maybe it's called Linux, but we're not there. Sorry. In conclusion:

1. *Everybody* knows what they get in an open source software. That also means things may not work but most things eventually get fixed.

2. You can use any old version for as long as you want. There are no restrictions here.

When you ask for 1. and 2. at the same time and steady security updates on top you're pushing too far for a free product, maybe even for a paid one.

[RGijsen]

All fair enough, but I have to agree with peter008 here; this is quite some bug, killing opnSense for weeks on end now, which had quite easiliy be tracked or at least found before eol-ing 18.x. I'm just wondering (trying to be constructive again), what hardware do you test the builds on before putting them out on the street? I assume there's multiple devices tested, right? Of course it's obvious not all hardware can be tested, there's practically an unlimited number of different configurations out there. Still, this bug as far as I could distill from the fora is with UEFI machines, and maybe slightly related to Spectre / Meltdown patches (although disabling them didn't help me). That means pretty much any Intel based pc / laptop from the last.. 5 or 6 years? Testing on an ESX machine or Hyper-V which ships in every Windows 10 Pro on ots own is trivial. So really I'm trying to understand your point here.

You keep telling us to donate, which I might if I have enough confidence (we are still evaluating OPNSense in favour of our current pfSense setup) but I'm not sure what you'd want. You want my money? You want the most generic Windows 10 box or laptop? I've read a thread this morning were people offer a VPS to test this on as well. Sure, might be not ideal, but WHAT do you exactly need that you don't have right now? It's hard to believe you don't have a laptop running Windows 10? But please prove me wrong and tell me what you DO need.

[franco]

Feel free to take sides. Here is the hard truth:

It may take 6 months to fix this. It may be fixed in 11.4. Or it may never be fixed.

I'm not asking for money. I'm asking for incentive, motivation and acceptance. I can see that some are not willing to give it at all. That's fine. I can understand. But such people will not change OPNsense or the community behind it.

Best to use the product that works for you and be done with it.


Cheers,
Franco

[RGijsen]

Not sure what you are trying to achieve with your attitude. A few post back you replied to me that I should sponsor the project. I ask you how, and this is your response?

People offered machines (even if VPS) but that doesn't seem to be what you want either. No offence, but I said I tried to be constructive, and asked how I / we can help. Not what we can do NOT to help you. But alas. Take out the popcorn.

[franco]

No need for popcorn, we simply don't seem to "click" and I can't get that across very well.


Cheers,
Franco

[franco]

PS: To be more clear, we seem to want different things from OPNsense. You want fixes, I want others to take responsibility for providing fixes or at least a basis for them. If we solely rely on others to get what we want the whole house of cards falls apart and nothing will get done and ideally that should be avoided, should it not?

[RGijsen]

Honestely, I don't care how you feel about me. IIf you've made your image on me based on the 14 (count 'em!) posts I've made so far, that's tells me more about you than about me.

As stated, I tried to be constructive, as do other people. But hey, we don't click. So whatever I offer is probably not any good. Too bad, I can live with that. I can't contribute code-wise if its <> .NET or gwbasic. But if my car's engine blows out, I can't fix it either. That doesn't mean I shouldn't drive one.

Anyway, it seems I can't help at all fixing this issue. Sorry community, my bad, I tried.