Date: Mon, 22 Aug 2022 07:12:33 -0700 From: John Kennedy <warlock@phouka.net> To: Marek Soudny <soumar@soudny.net> Cc: freebsd-arm@freebsd.org Subject: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 Message-ID: <YwOO0eaMbMBowyRv@phouka1.phouka.net> In-Reply-To: <e71cbb3f-2f69-a913-1b85-e1df9d1d8eb1@soudny.net> References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> <Yv1zyQob9Q0aHLm%2B@phouka1.phouka.net> <e71cbb3f-2f69-a913-1b85-e1df9d1d8eb1@soudny.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 22, 2022 at 03:57:52PM +0200, Marek Soudny wrote: > thank you again for your advice and opinions. I purchased new SanDisk sd > card and usb stick as well, just in case. > > I have to say, that I diged a bit further and found out the RPI4B (4G > RAM) becomes unresponsive right after I try to access it via wireguard > vpn, or when I tried to access the rest of the wireguard vpn from the > box. I disabled the wireguard service before weekend and the box has an > uptime since. > > So, has anybody had an issue with wireguard and rpi4? 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. ... and that is the reason that I do horrible things to my RPIs and their storage like compiling the kernel and poudriere my packages. :D
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YwOO0eaMbMBowyRv>