Date: Sun, 22 May 2022 03:28:43 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 264114] net/wireguard-kmod: Crashes on 13.1-RELEASE: panic: vm_fault_lookup: fault on nofault entry, addr: 0 (wireguard) Message-ID: <bug-264114-7501-iMqdNep37f@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264114-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-264114-7501@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=3D264114 --- Comment #3 from Nick Briggs <nicholas.h.briggs@gmail.com> --- It would be a much better UX if the wireguard kmod if_wg.ko were tagged such that the kernel module loader noticed that it was not compatible with the n= ew kernel. The virtualbox module seems to be coded so that the module loader detects t= hat situation, reports an error, and refuses to load. I much prefer that over having to deal with a system that panics each time someone tries establish a tunnel. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264114-7501-iMqdNep37f>