From nobody Wed Aug 24 09:45:55 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 4MCLng1JG8z4ZmhC for ; Wed, 24 Aug 2022 09:45:59 +0000 (UTC) (envelope-from SRS0=Ad7j=Y4=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 4MCLnf18ZRz3dFT for ; Wed, 24 Aug 2022 09:45:58 +0000 (UTC) (envelope-from SRS0=Ad7j=Y4=klop.ws=ronald-lists@realworks.nl) Date: Wed, 24 Aug 2022 11:45:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1661334356; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=doQvEt+XFlj4FVPV2o0sgeWHbjFMRvCteiTB6/nlPf0=; b=mMDmaqrMfqZd+7uBLW1/YVwRWaajnfz5TIYMNaojGeXijQkBjjiBi6xC3LXCJ7SToaPbP1 cBcp9Kv55JD8ZhPhRlRimM3h14utbPw5fE+IdFUXxFvNU/Sl0jqxdBcHIfPYOspe+/lglS WjHqVC7CLB+QiIS6Ezib1Nmup1UW6aaw1xGa4z2HlOeAgYvcx7MKftm1d8h5eeoADArawi y6eXUSB9K7JirVJjlJYiwwzkaC+tol1ciF+Ya0ihBCx8zyVHGhp9avxkqRrKHJsPLJNNpn kfEH3ibiOPXE1oCrya/KFpx24r8uo4oDD/DW7kVeNE/UX51gHJYp1wVALQ33rw== From: Ronald Klop To: soumar@soudny.net Cc: freebsd-arm@freebsd.org Message-ID: <795495190.105.1661334355891@localhost> In-Reply-To: References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> Subject: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 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: multipart/alternative; boundary="----=_Part_104_22844988.1661334355822" X-Mailer: Realworks (620.114) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4MCLnf18ZRz3dFT X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=mMDmaqrM; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=Ad7j=Y4=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=Ad7j=Y4=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.20 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_LONG(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; MID_RHS_NOT_FQDN(0.50)[]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=Ad7j=Y4=klop.ws=ronald-lists@realworks.nl]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ZERO(0.00)[0]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_HAS_DN(0.00)[]; HAS_X_PRIO_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=Ad7j=Y4=klop.ws=ronald-lists@realworks.nl] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_104_22844988.1661334355822 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Marek Soudny Datum: woensdag, 24 augustus 2022 11:29 Aan: freebsd-arm@freebsd.org Onderwerp: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4 > > 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 > > > > Hi, Do you have a serial console connected to the RPI4? That would enable you to see crash messages. Regards, Ronald. ------=_Part_104_22844988.1661334355822 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

Van: Marek Soudny <soumar@soudny.net>
Datum: woensdag, 24 augustus 2022 11:29
Aan: freebsd-arm@freebsd.org
Onderwerp: Re: wireguard, was: kernel: Fatal data abort - issue on rpi4

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
 


Hi,

Do you have a serial console connected to the RPI4? That would enable you to see crash messages.

Regards,
Ronald.
  ------=_Part_104_22844988.1661334355822--