From nobody Mon Aug 22 14:12:33 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 4MBDqg2bGtz4Zkcc for ; Mon, 22 Aug 2022 14:13:51 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MBDqf2cfbz469J for ; Mon, 22 Aug 2022 14:13:50 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.16.1/8.16.1) with ESMTPS id 27MECXhJ003540 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 22 Aug 2022 07:12:33 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.16.1/8.16.1/Submit) id 27MECXoC003539; Mon, 22 Aug 2022 07:12:33 -0700 (PDT) (envelope-from warlock) Date: Mon, 22 Aug 2022 07:12:33 -0700 From: John Kennedy To: Marek Soudny Cc: freebsd-arm@freebsd.org Subject: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 Message-ID: References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4MBDqf2cfbz469J X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net X-Spamd-Result: default: False [-1.80 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; MIME_TRACE(0.00)[0:+]; R_SPF_NA(0.00)[no SPF record]; RCPT_COUNT_TWO(0.00)[2]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[phouka.net]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net] X-ThisMailContainsUnwantedMimeParts: N 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