Date: Wed, 24 Aug 2022 11:45:55 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: soumar@soudny.net Cc: freebsd-arm@freebsd.org Subject: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 Message-ID: <795495190.105.1661334355891@localhost> 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
------=_Part_104_22844988.1661334355822
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Van: Marek Soudny <soumar@soudny.net>
Datum: woensdag, 24 augustus 2022 11:29
Aan: freebsd-arm@freebsd.org
Onderwerp: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4
>
> 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
>
>
>
>
Hi,
Do you have a serial console connected to the RPI4? That would enable you to see crash messages.
Regards,
Ronald.
------=_Part_104_22844988.1661334355822
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<html><head></head><body>
<p><strong>Van:</strong> Marek Soudny <soumar@soudny.net><br />
<strong>Datum:</strong> woensdag, 24 augustus 2022 11:29<br />
<strong>Aan:</strong> freebsd-arm@freebsd.org<br />
<strong>Onderwerp:</strong> Re: wireguard, was: kernel: Fatal data abort - issue on rpi4</p>
<blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px">
<div class="MessageRFC822Viewer" id="P">
<div class="TextPlainViewer" id="P.P">Hello,<br />
> I don't use wireguard myself, but if a package includes a kernel<br />
> driver you have to be really careful that you keep them in sync. I run<br />
> into this possibility with video drivers (nvidia, radion, etc) all the time.<br />
<br />
I use GENERIC kernel with freebsd-update and quarterly pkg branch, so everything should be in sync.<br />
<br />
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.<br />
<br />
No idea how to debug this, thou. Anyway, I can reproduce it anytime.<br />
<br />
BR,<br />
Marek<br />
</div>
<hr /></div>
</blockquote>
<br />
<br />
Hi,<br />
<br />
Do you have a serial console connected to the RPI4? That would enable you to see crash messages.<br />
<br />
Regards,<br />
Ronald.<br />
</body></html>
------=_Part_104_22844988.1661334355822--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?795495190.105.1661334355891>