From nobody Mon Aug 22 13:57:52 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MBDTQ3XG1z4Zj1D for ; Mon, 22 Aug 2022 13:58:02 +0000 (UTC) (envelope-from soumar@soudny.net) Received: from schrodinger.soudny.net (schrodinger.soudny.net [46.28.108.130]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MBDTP46lfz44jp for ; Mon, 22 Aug 2022 13:58:01 +0000 (UTC) (envelope-from soumar@soudny.net) Received: from [192.168.111.10] (unknown [46.57.88.202]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) (Authenticated sender: marek@soudny.net) by schrodinger.soudny.net (Postfix) with ESMTPSA id 638B628675 for ; Mon, 22 Aug 2022 15:57:53 +0200 (CEST) Message-ID: Date: Mon, 22 Aug 2022 15:57:52 +0200 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Reply-To: soumar@soudny.net Subject: wireguard, was: kernel: Fatal data abort - issue on rpi4 Content-Language: en-US To: freebsd-arm@freebsd.org References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> From: Marek Soudny Organization: soudny.net In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4MBDTP46lfz44jp X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of soumar@soudny.net designates 46.28.108.130 as permitted sender) smtp.mailfrom=soumar@soudny.net X-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[soudny.net]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; HAS_REPLYTO(0.00)[soumar@soudny.net]; TO_DN_NONE(0.00)[]; HAS_ORG_HEADER(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:197019, ipnet:46.28.104.0/21, country:CZ]; TO_MATCH_ENVRCPT_ALL(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N 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. >