From nobody Wed Aug 24 09:29:58 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 4MCLRP3wlVz4ZkwW for ; Wed, 24 Aug 2022 09:30:09 +0000 (UTC) (envelope-from soumar@soudny.net) Received: from schrodinger.soudny.net (schrodinger.soudny.net [IPv6:2a02:2b88:2:1::6dc8: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 4MCLRN5pJ7z3bt2 for ; Wed, 24 Aug 2022 09:30:08 +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)) (No client certificate requested) (Authenticated sender: marek@soudny.net) by schrodinger.soudny.net (Postfix) with ESMTPSA id CB9C5A4A2 for ; Wed, 24 Aug 2022 11:29:58 +0200 (CEST) Message-ID: Date: Wed, 24 Aug 2022 11:29:58 +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: Re: 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: 4MCLRN5pJ7z3bt2 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of soumar@soudny.net designates 2a02:2b88:2:1::6dc8: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:+]; ASN(0.00)[asn:197019, ipnet:2a02:2b88::/32, country:CZ]; 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)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N 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