Date: Mon, 22 Aug 2022 15:57:52 +0200 From: Marek Soudny <soumar@soudny.net> To: freebsd-arm@freebsd.org Subject: wireguard, was: kernel: Fatal data abort - issue on rpi4 Message-ID: <e71cbb3f-2f69-a913-1b85-e1df9d1d8eb1@soudny.net> In-Reply-To: <Yv1zyQob9Q0aHLm%2B@phouka1.phouka.net> References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> <Yv1zyQob9Q0aHLm%2B@phouka1.phouka.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, 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? thx, Marek On 8/18/22 01:03, John Kennedy wrote: > On Wed, Aug 17, 2022 at 11:10:30AM +0200, Marek Soudny wrote: >> Hello, >> >> I am quite new to arm/aarch64. I recently purchased rpi4, burned an >> sdcard image and have been trying to run it. Time to time (but actually >> quite often) the box becomes unresponsive. I can not ping it, neither >> ssh into it. I am running fbsd 13.1-release. > > When I was doing a lot of SDcard work pre-RPI4, I was almostly > exclusively using SanDisk (Ultra) cards. I was looking for robust > cards with high transfer speed. Once USB became an option, I pretty > only much booted off them when I was forced to. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e71cbb3f-2f69-a913-1b85-e1df9d1d8eb1>