Date: Wed, 24 Aug 2022 11:29:58 +0200 From: Marek Soudny <soumar@soudny.net> To: freebsd-arm@freebsd.org Subject: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 Message-ID: <e937fef0-5c28-27ac-2f36-41991d344610@soudny.net> In-Reply-To: <YwOO0eaMbMBowyRv@phouka1.phouka.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e937fef0-5c28-27ac-2f36-41991d344610>