Date: Thu, 25 Aug 2022 11:39:55 +0200 From: Bernhard Froehlich <decke@FreeBSD.org> To: "soumar" <soumar@soudny.net> Cc: "freebsd-arm" <freebsd-arm@freebsd.org> Subject: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 Message-ID: <182d45f59fa.110ea3128111181.817157529973929418@FreeBSD.org> In-Reply-To: <e937fef0-5c28-27ac-2f36-41991d344610@soudny.net> References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> <Yv1zyQob9Q0aHLm%2B@phouka1.phouka.net> <e71cbb3f-2f69-a913-1b85-e1df9d1d8eb1@soudny.net> <YwOO0eaMbMBowyRv@phouka1.phouka.net> <e937fef0-5c28-27ac-2f36-41991d344610@soudny.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-- Bernhard Froehlich https://www.bluelife.at/ ---- On Wed, 24 Aug 2022 11:29:58 +0200 Marek Soudny wrote ---=20 > Hello, > > I don't use wireguard myself, but if a package includes a kernel > > driver you have to be really careful that you keep them in sync. I ru= n > > into this possibility with video drivers (nvidia, radion, etc) all the= time. >=20 > I use GENERIC kernel with freebsd-update and quarterly pkg branch, so=20 > everything should be in sync. >=20 > Anyway, I can confirm that loading if_wg kernel module does not do=20 > anything wrong, on it's own. Starting the wireguard service does not do= =20 > anything wrong either, on it's own. BUT :) As soon as I tried to ping=20 > the wireguard interface from another box, my rpi stopped responding=20 > without stating why (I was tailing=20 > /var/log/{messages,debug.log,daemon.log}) and rebooted itself after (a)= =20 > few minutes. >=20 > No idea how to debug this, thou. Anyway, I can reproduce it anytime. >=20 > BR, > Marek There is no need to waste any more time on this. We have seen this all already and it's caused because all ports (latest and quarterly branch) for FreeBSD 13.x are build on 13.0 currently. But because of an ABI break in 13.1 the wireguard kernel module will panic when used. Your chances are either rebuild the kernel module on 13.1 and it will work fine or you wait until packages are build on 13.1 which is VERY soon. FreeBSD 13.0 is EoL in less than a week (August 31, 2022), so official package builders will switch soon - the next full build will not have that problem anymore.=20 -- Bernhard Fr=C3=B6hlich https://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?182d45f59fa.110ea3128111181.817157529973929418>