Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kernel panic when run in a VM with i350 VF. #202

Open
Phreeman33 opened this issue Apr 12, 2024 · 5 comments
Open

Kernel panic when run in a VM with i350 VF. #202

Phreeman33 opened this issue Apr 12, 2024 · 5 comments
Labels
upstream Third party issue

Comments

@Phreeman33
Copy link

Same issue with this.

Environment:
VM System: Proxmox VE 8.1.10 (Linux 6.5.13-5-pve)
OPNsense: 24.1.5_3
CPU: Intel i5-3340
NIC: intel i350-t4

@AdSchellevis AdSchellevis added the upstream Third party issue label Apr 12, 2024
@fichtner
Copy link
Member

fichtner commented Feb 5, 2025

Closing due to switch to FreeBSD 14.x

@fichtner fichtner closed this as completed Feb 5, 2025
@abirkill
Copy link

abirkill commented Feb 6, 2025

I'm not sure if this has been closed because it's believed fixed in FreeBSD 14.x? But I can confirm this is still an issue in OPNsense 25.1 when using Virtual Functions with an Intel i350 NIC.

Image

Also, I'm not sure if I'm looking in the right place, but I checked the FreeBSD Bugzilla with the keyword IntelNetworking (https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=IntelNetworking), and I can't find any reports of this.

Indeed, there are reports (such as this one) that suggests FreeBSD does basically work with i350 VFs. So it's possible this might not be an upstream issue, but I haven't yet tried booting FreeBSD with an i350 VF passed through to see if it gets past the kernel panic that happens in OPNsense.

@fichtner
Copy link
Member

fichtner commented Feb 6, 2025

I don’t mind reopening, but that won’t change much if this does not get reported to FreeBSD with a full panic or better yet a core dump (we do have a debug kernel for this purpose).

Intel may have something say about the behaviour on FreeBSD too. Some bugs are known, but not widely reported.

Cheers,
Franco

@abirkill
Copy link

abirkill commented Feb 6, 2025

That's fair enough. I've been slightly less lazy than in my previous comment and actually tried FreeBSD 14.2, and can confirm it also fails with a very similar kernel panic.

When I get a bit more time I'll try and figure out how to collect the diagnostics required to usefully open a FreeBSD issue.

Thanks for your help!

@fichtner fichtner reopened this Feb 6, 2025
@fichtner
Copy link
Member

fichtner commented Feb 6, 2025

@abirkill thanks, I'll reopen and if you need help let me know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Third party issue
Development

No branches or pull requests

4 participants