From nobody Wed Jun 01 16:28:50 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 5B9AC1B4B5BB for ; Wed, 1 Jun 2022 16:29:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (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 4LCvjb1q4jz3jqp for ; Wed, 1 Jun 2022 16:29:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe36.google.com with SMTP id k4so2204002vsp.3 for ; Wed, 01 Jun 2022 09:29:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZP1qbJU0Jbxgtptja4UPoaAtCL1KCaqg0o3pjxOSIZY=; b=RBVTrSuCVRvfMQwndzlZ6Ju73zX5knW6tzGBgOqNtlO6ztzvFu0UxkglR9fjxj0V0i Nh9lvToCiXGCFmI0nkjAIHtITJG2nJJA8MGX0riyvVgo3mNPExHWD+D/UgEjG1BA7nu7 nbh5F0f+oC71Jibg0yuk5IPg+J4Cg33krflc5pF9rk7TcF5G3ACpzAq7QuUZAv/fXCe4 E0Vvux3aMYmJh2k8+pOl3F25bvna1hA70BvTPQvBMwNSRQAmOUTAz7NXG4W1RnvftOTe 2zBZ+6A8ZXS6DB0bzbay2XyxrKyOveNIe1GVs4b0E/fZ2bCRCQOZyej8oLb5GSDEZbpR 9Y+w== 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=ZP1qbJU0Jbxgtptja4UPoaAtCL1KCaqg0o3pjxOSIZY=; b=01OKt/EYzmWmcsZLEHYLh/+9hR+z18jkEVpSO27vQDr/9lmy/KdjcX2crF0fYnFBKS wXBKP8Umq2Ux03l8Kl3KFUX8/zwCjCc9Q8qGT9kJmfCkmNhFiTd4q2tUQCuovPaiPIlq ps6KjRB78FN2oBn8ZueGiZWiuf2yo1IGJXs3gypON8sblaRYLfNgqYokWP5Pp+55wmaw /f3M4D/pqGuOsX3Qkj5bkTPdYXfKTSC3QuvJo2pS0+4cNs3BELUwIhsek1qYttsB4bK7 eYobUZNU/SoFSJ7BLNpU1qlfLEJtDg1g9+N2G9l9M3vEqDtXHSPLwhZUes9eMMZIlcW8 Td1g== X-Gm-Message-State: AOAM531exIICmgM8FTq+N+p8EfLCrZv66sdTX4xVL0hTQwtsX+mY6wcs QsdMnDjJ7zm+S7ZnVaqs9gVpIG3gqkJkFtnHWJ+7L12XF1w= X-Google-Smtp-Source: ABdhPJxUmF8czU7iphHwnvmd+opZAGdJxclw7TMShSrzesOZgSFaFCI5pWN/J9NAA7irFCfGdMPWQlF5KIbfQ/zCouQ= X-Received: by 2002:a67:1547:0:b0:32c:f3a1:bdd8 with SMTP id 68-20020a671547000000b0032cf3a1bdd8mr395879vsv.44.1654100941299; Wed, 01 Jun 2022 09:29:01 -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: <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> From: Warner Losh Date: Wed, 1 Jun 2022 10:28:50 -0600 Message-ID: Subject: Re: Mountroot problems on RPi3/aarch64 To: Mark Millard Cc: bob prohaska , "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="00000000000007780c05e06563ba" X-Rspamd-Queue-Id: 4LCvjb1q4jz3jqp X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=RBVTrSuC; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::e36) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::e36:from]; MLMMJ_DEST(0.00)[freebsd-arm]; FREEMAIL_TO(0.00)[yahoo.com]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --00000000000007780c05e06563ba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 sup= erblock > 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 in the tree, it wouldn't hurt to try it... Warner --00000000000007780c05e06563ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Jun 1, 2022 at 10:17 AM Mark = Millard <marklmi@yahoo.com> = wrote:
On 2022-J= un-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://lists.freebsd.o= rg/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
--00000000000007780c05e06563ba--