Date: Thu, 15 Apr 2021 19:18:23 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915 Message-ID: <bug-254695-27103-8JpE2RCmwn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254695-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-254695-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254695 --- Comment #9 from Gordon Bergling <gbe@FreeBSD.org> --- (In reply to Wei Hu from comment #8) Thanks for the investigation. I was able to boot a kernel from today (15 Ap= ril) on this machine. I tracked the issue down to the tcp_bbr or cc_htcp. I build the system with WITH_EXTRA_TCP_STACKS=3D1 and have tcp_bbr_load=3D"YES" cc_htcp_load=3D"YES" in /boot/loader.conf and net.inet.tcp.cc.algorithm=3Dhtcp net.inet.tcp.functions_default=3Dbbr in /etc/sysctl.conf. I first disabled the sysctl.conf settings and the panic is still happening.= So it is enough to load the modules at boot time. If I disable both modules the system is starting as usual. If one of these modules is loaded at boot time, the system panics. Maybe it is something locking related. Hope that helps to track down that issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254695-27103-8JpE2RCmwn>