From nobody Wed Jun 01 18:04:53 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 0A8F21B64FE9 for ; Wed, 1 Jun 2022 18:05:06 +0000 (UTC) (envelope-from irontree043111@gmail.com) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LCxrK2xp1z3wFT for ; Wed, 1 Jun 2022 18:05:05 +0000 (UTC) (envelope-from irontree043111@gmail.com) Received: by mail-yb1-xb2b.google.com with SMTP id f34so4291746ybj.6 for ; Wed, 01 Jun 2022 11:05:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Cdazh4td8NXwhnZIi3DaZAMWxA+vOWcDaR0RZdLsYeY=; b=J9MkGALGNUXOm6dEUcDVF9q+u/5Yb82k3m4/0TTq49i5hbQ4IetTj8CCmXEBXO0RcB Aq4tALQH9niUGO30RDd468CjNsqryEDqkVUCuWKT+ocCvWzfhEcTfbnhI/nS76aIx1TZ 0GuVBk8g+VR7hzPl5/ixTzCXPVdMRYQ/XFfITyZqzrrcoK6YTQ8c6fDH7TKh5o2Nhfkz NWJ4hzM+xfQB+25zmd2saOo+L14xsO38GmIxZ6xwHD6pttV5vY6DqllbnlEWY8ei8CPb fyuWfNCcijCVfOw0sdh3zhPuyVkKgAhDJz8OHdjwmyGVNppJa+BO91xuJyg2s9u92Zud aQ5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Cdazh4td8NXwhnZIi3DaZAMWxA+vOWcDaR0RZdLsYeY=; b=xWFw2y7RbTo1Gw60wFYOZAuZ1O9eReZTY7nCDsQQBqloiYOVhlPzAbzc5KTN3VtwbZ 5mrvo5xCNG3gStim1LRyrD2q99uuQZLt2PLVycIcwouKMpfunGE4L0WSPRwStjGG+xaY NbgTHIqvUEqU8KOIvO0IUsv7ZEtSNQ2EymCn6EUEvgQx+7tWkW5c7F+iMC3LScvQPF60 zqITYvgeq7CItTZ4mLNG2pKd4iGl1EWO9hhG0V5NP1NoNj3rDBnwEz9JvbnEd/T6T0h8 dhTwJ2qx/6S2kgOpbScrPMn2TAkK1XyVY75xXFwpVpElz/m2hgZZbzgfCbxlaAWZg4Ll JyXw== X-Gm-Message-State: AOAM5339UFOY8dd5djPCD9Hw4394BcK6gDks0gAqPhxzjNXcyxTFZnXN R+jj9pPFZLud42nq4uS1nW6awEHRh2nnkpX51LCimGkAxCNeAQ== X-Google-Smtp-Source: ABdhPJwTt+Ditr8dmhzYqTwZY0j3M+LCU7CAsWL5AbsYYVC0ofis51N5XQ5cqtm03q9Z9q1yCrpyhnQqV5w2HFqFmuM= X-Received: by 2002:a25:814b:0:b0:650:db5:6ba with SMTP id j11-20020a25814b000000b006500db506bamr1033760ybm.237.1654106704784; Wed, 01 Jun 2022 11:05:04 -0700 (PDT) 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 References: <20220601154142.GA41835@www.zefox.net> <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> In-Reply-To: From: Robert Montano Date: Wed, 1 Jun 2022 11:04:53 -0700 Message-ID: Subject: Re: Mountroot problems on RPi3/aarch64 To: Warner Losh Cc: Mark Millard , bob prohaska , Free BSD Content-Type: multipart/alternative; boundary="0000000000008f31e505e066baa6" X-Rspamd-Queue-Id: 4LCxrK2xp1z3wFT X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=J9MkGALG; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of irontree043111@gmail.com designates 2607:f8b0:4864:20::b2b as permitted sender) smtp.mailfrom=irontree043111@gmail.com X-Spamd-Result: default: False [-3.98 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.985]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2b:from]; MLMMJ_DEST(0.00)[freebsd-arm]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_CC(0.00)[yahoo.com,www.zefox.net,freebsd.org]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --0000000000008f31e505e066baa6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you for your emails! On Wed, Jun 1, 2022, 9:29 AM Warner Losh wrote: > > > On Wed, Jun 1, 2022 at 10:17 AM Mark Millard wrote: > >> On 2022-Jun-1, at 08:41, bob prohaska wrote: >> >> > Since about 05/29 mountroot has been failing on a Pi3 self-hosting >> -current, >> > using a usb mechanical hard disk. >> > >> > Anybody else seen this sort of behavior? >> >> You do not report much context. FreeBSD version? UFS? ZFS? >> And so on. >> >> However, there has been today (for main): >> >> git: bc218d89200f - main - Two bug fixes to UFS/FFS superblock integrity >> checks when reading a superblock >> >> that is for fixing boot problems in UFS contexts. See: >> >> >> https://lists.freebsd.org/archives/dev-commits-src-main/2022-June/006977= .html >> >> This is for fixes related to the 2022-May-27 change: >> >> =E2=80=A2 git: 076002f24d35 - main - Do comprehensive UFS/FFS su= perblock >> integrity checks when reading a superblock. Kirk McKusick >> > > I'd expect these to fix only the boot loader issues, not the mountroot > issues, but it wouldn't hurt to try... p3 is aarch64 which is UEFI which > had the right MAXPHYS in the boot loader... though since the change is i= n > the tree, it wouldn't hurt to try it... > > Warner > --0000000000008f31e505e066baa6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you for your emails!

On Wed, Jun 1, 2022, 9:29 AM Wa= rner Losh <imp@bsdimp.com> wrot= e:


On Wed, Jun 1, 2022 at 10:17 AM Mark Millard <marklmi@yahoo.com= > wrote:
On 2= 022-Jun-1, at 08:41, bob prohaska <fbsd@www.zefox.net> wrote:

> Since about 05/29 mountroot has been failing on a Pi3 self-hosting -cu= rrent,
> using a usb mechanical hard disk.=C2=A0
>
> Anybody else seen this sort of behavior?

You do not report much context. FreeBSD version? UFS? ZFS?
And so on.

However, there has been today (for main):

git: bc218d89200f - main - Two bug fixes to UFS/FFS superblock integrity ch= ecks when reading a superblock

that is for fixing boot problems in UFS contexts. See:

https://list= s.freebsd.org/archives/dev-commits-src-main/2022-June/006977.html

This is for fixes related to the 2022-May-27 change:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 git: 076002f24d35 - main - Do compreh= ensive UFS/FFS superblock integrity checks when reading a superblock. Kirk = McKusick

I'd expect these to fix on= ly the boot loader issues, not the mountroot issues, but it wouldn't hu= rt to try...=C2=A0 p3 is aarch64 which is UEFI which had the right MAXPHYS = in the boot loader...=C2=A0 though since the change is in the tree, it woul= dn't hurt to try it...

Warner
--0000000000008f31e505e066baa6--