From nobody Thu Aug 25 09:54:37 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 4MCyxG4X6kz4bMZK for ; Thu, 25 Aug 2022 09:54:42 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MCyxF2f3gz3lXN for ; Thu, 25 Aug 2022 09:54:41 +0000 (UTC) (envelope-from ronald-lists@klop.ws) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=klop.ws; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From:References: To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=835aB+EJ+jyCTrK5E1w/EZ8epL/CbhwZ18j2M2PoyLU=; b=YFKAiAKcDsx5Iy6aR7v+9Ulzch 7GB6sqE7mJlcsD4PmyxRqqayvAhHK04Apmgb4HuT1a/fbydj439GDzohd5Y2xPMZsl+HH1PiEMJze HfF3qNeYOPgarUFVJZuLQ8Imwl2HzlNhEY1I5UemkpvNV52BmSwjmdVUWpm767v9K2r8=; Message-ID: <3baa8d6f-045b-ea29-ee66-a182875fe197@klop.ws> Date: Thu, 25 Aug 2022 11:54:37 +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.13.0 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> <182d45f59fa.110ea3128111181.817157529973929418@FreeBSD.org> From: Ronald Klop In-Reply-To: <182d45f59fa.110ea3128111181.817157529973929418@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.greenhost.nl X-Spam-Level: / X-Spam-Score: -0.4 X-Spam-Status: No, score=-0.4 required=5.0 tests=ALL_TRUSTED,BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,T_SCC_BODY_TEXT_LINE autolearn=disabled version=3.4.2 X-Scan-Signature: 4c3c8b3d32e7d0cfaf2d58264fc1daa3 X-Rspamd-Queue-Id: 4MCyxF2f3gz3lXN X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=mail header.b=YFKAiAKc; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 195.190.28.88 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-0.99)[-0.987]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; R_DKIM_ALLOW(-0.20)[klop.ws:s=mail]; R_SPF_ALLOW(-0.20)[+ip4:195.190.28.64/27]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[195.190.28.88:from]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:47172, ipnet:195.190.28.0/24, country:NL]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 8/25/22 11:39, Bernhard Froehlich wrote: > > -- > Bernhard Froehlich > https://www.bluelife.at/ > ---- On Wed, 24 Aug 2022 11:29:58 +0200 Marek Soudny wrote --- > > 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 > > 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. > > 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. > > 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. > > -- > Bernhard Fröhlich > https://www.bluelife.at/ > > To give some perspective to "VERY soon". Full builds take a long time (as in multiple days). And also uploading all these packages to mirrors takes a considerable amount of time. My past experience is that if the 13.1 pkg builders start at September 1th the pkg might be available around September 7th. NB: I'm not part of the pkg builders team, so I'm not aware of the specific plans and dates. Just my empirical 2 cents on this. Regards, Ronald.