From nobody Thu Aug 25 09:59:36 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 4MCz316hCkz4bN0D for ; Thu, 25 Aug 2022 09:59:41 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MCz305g36z3mPq; Thu, 25 Aug 2022 09:59:40 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1140:c3d:d8ce:8a19:a651:d449]) (Authenticated sender: macmic) by drew.franken.de (Postfix) with ESMTPSA id 529827220BFAF; Thu, 25 Aug 2022 11:59:37 +0200 (CEST) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 From: tuexen@freebsd.org In-Reply-To: <182d45f59fa.110ea3128111181.817157529973929418@FreeBSD.org> Date: Thu, 25 Aug 2022 11:59:36 +0200 Cc: soumar , freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> <182d45f59fa.110ea3128111181.817157529973929418@FreeBSD.org> To: Bernhard Froehlich X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Spam-Status: No, score=-1.2 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_SCC_BODY_TEXT_LINE,URIBL_SBL,URIBL_SBL_A autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-Rspamd-Queue-Id: 4MCz305g36z3mPq X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 193.175.24.27 is neither permitted nor denied by domain of tuexen@freebsd.org) smtp.mailfrom=tuexen@freebsd.org X-Spamd-Result: default: False [-2.70 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[193.175.24.27:from]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:680, ipnet:193.174.0.0/15, country:DE]; FROM_NO_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEFALL_USER(0.00)[tuexen]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; RCVD_VIA_SMTP_AUTH(0.00)[] X-ThisMailContainsUnwantedMimeParts: N > On 25. Aug 2022, at 11:39, Bernhard Froehlich = wrote: >=20 >=20 > -- > Bernhard Froehlich > https://www.bluelife.at/ > ---- On Wed, 24 Aug 2022 11:29:58 +0200 Marek Soudny wrote ---=20 >> 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. >>=20 >> I use GENERIC kernel with freebsd-update and quarterly pkg branch, so=20= >> everything should be in sync. >>=20 >> Anyway, I can confirm that loading if_wg kernel module does not do=20 >> anything wrong, on it's own. Starting the wireguard service does not = do=20 >> anything wrong either, on it's own. BUT :) As soon as I tried to ping=20= >> the wireguard interface from another box, my rpi stopped responding=20= >> without stating why (I was tailing=20 >> /var/log/{messages,debug.log,daemon.log}) and rebooted itself after = (a)=20 >> few minutes. >>=20 >> No idea how to debug this, thou. Anyway, I can reproduce it anytime. >>=20 >> BR, >> Marek >=20 > There is no need to waste any more time on this. We have seen this all > already and it's caused because all ports (latest and quarterly = branch) for > FreeBSD 13.x are build on 13.0 currently. But because of an ABI break = in > 13.1 the wireguard kernel module will panic when used. Which ABI was changed between 13.0 and 13.1? Best regards Michael >=20 > Your chances are either rebuild the kernel module on 13.1 and it will = work > fine or you wait until packages are build on 13.1 which is VERY soon. >=20 > FreeBSD 13.0 is EoL in less than a week (August 31, 2022), so official > package builders will switch soon - the next full build will not have = that > problem anymore.=20 >=20 > -- > Bernhard Fr=C3=B6hlich > https://www.bluelife.at/ >=20 >=20