Re: LRO Kernel Panic on Hyper-V VM

Shawn Webb <[email protected]> Thu, 16 Apr 2026 00:15:13 +0000

Newsgroups	gmane.os.freebsd.current
Message-ID	<ar4wbc4nkmgogwp6akm2acjzomh3si4zybetkaqpwt5y4q2kfn@vqy7y7dybqv5>

On Wed, Apr 15, 2026 at 10:37:08PM +0200, Michael Tuexen wrote:
> > On 15. Apr 2026, at 22:12, Michael Tuexen <[email protected]> wrote:
> > 
> >> On 15. Apr 2026, at 21:32, Shawn Webb <[email protected]> wrote:
> >> 
> >> Hey all,
> >> 
> >> I've updated one of my Hyper-V VMs earlier today against an up-to-date
> >> source tree. I've noticed quite a few networking-related changes in
> >> FreeBSD on 16-CURRENT and I suspect (at least) one of those changes is
> >> problematic.
> >> 
> >> I'm not at all well-versed in the networking code, so I'm unsure
> >> what's going on.
> >> 
> >> I've uploaded a core.txt dump:
> >> https://hardenedbsd.org/~shawn/2026-04-15_lro-panic-r01.txt
> > Thanks. The problem is that the vnet is not set correctly.
> > 
> > This should fix it:
> > https://reviews.freebsd.org/D56420
> The fix has been committed:
> https://cgit.FreeBSD.org/src/commit/?id=2d13620c6e1be7f8136095f648a6b824158d0941 <https://cgit.freebsd.org/src/commit/?id=2d13620c6e1be7f8136095f648a6b824158d0941>
> 
> Thanks for reporting the issue!

Thanks a bunch for the quick fix! My Hyper-V VM is happy once again.

-- 
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

Signal Username:  shawn_webb.74
Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50
https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc

signature.asc (application/pgp-signature, 833 B)