Date: Thu, 25 Aug 2022 13:10:17 +0200 From: decke@freebsd.org To: "tuexen" <tuexen@freebsd.org> Cc: "soumar" <soumar@soudny.net>, "freebsd-arm" <freebsd-arm@freebsd.org> Subject: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 Message-ID: <182d4b21735.d607f074120196.5734997048820295304@freebsd.org> In-Reply-To: <E0FB2C9C-F224-4719-B60E-BBEC393C799F@freebsd.org> 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> <182d45f59fa.110ea3128111181.817157529973929418@FreeBSD.org> <E0FB2C9C-F224-4719-B60E-BBEC393C799F@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
---- On Thu, 25 Aug 2022 11:59:36 +0200 wrote --- > > > > On 25. Aug 2022, at 11:39, Bernhard Froehlich decke@FreeBSD.org> wrote: > > > > > > -- > > Bernhard Froehlich > > https://www.bluelife.at/ > > ---- On Wed, 24 Aug 2022 11:29:58 +0200 Marek Soudny wrote --- > >> 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 run > >>> into this possibility with video drivers (nvidia, radion, etc) all the time. > >> > >> I use GENERIC kernel with freebsd-update and quarterly pkg branch, so > >> everything should be in sync. > >> > >> Anyway, I can confirm that loading if_wg kernel module does not do > >> anything wrong, on it's own. Starting the wireguard service does not do > >> anything wrong either, on it's own. BUT :) As soon as I tried to ping > >> the wireguard interface from another box, my rpi stopped responding > >> without stating why (I was tailing > >> /var/log/{messages,debug.log,daemon.log}) and rebooted itself after (a) > >> few minutes. > >> > >> No idea how to debug this, thou. Anyway, I can reproduce it anytime. > >> > >> 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. > Which ABI was changed between 13.0 and 13.1? Check PR 264114 for more details. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114 -- Bernhard Froehlich https://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?182d4b21735.d607f074120196.5734997048820295304>