From nobody Sun Aug 07 22:43:44 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 4M1Ds46nylz4Y2BB; Sun, 7 Aug 2022 22:43:52 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail0.glenbarber.us", Issuer "Gandi Standard SSL CA 2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M1Ds46Nvsz3cxM; Sun, 7 Aug 2022 22:43:52 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from smtpclient.apple (70.15.90.15.res-cmts.sewb.ptd.net [70.15.90.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id BBF3D56203; Sun, 7 Aug 2022 22:43:45 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 mail0.glenbarber.us BBF3D56203 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 (1.0) Subject: Re: Looks like the arm 20220805 snapshots are still odd, so probably kern.geom.part.mbr.enforce_chs=0 was still in use From: Glen Barber In-Reply-To: <6AF28022-A8E7-46B3-B64E-99D217E9B6AC@yahoo.com> Date: Sun, 7 Aug 2022 18:43:44 -0400 Cc: Warner Losh , "Rodney W. Grimes" , Ed Maste , FreeBSD Hackers , freebsd-arm Message-Id: <0E0083BD-A749-4112-8FDA-62326EA95F8A@freebsd.org> References: <6AF28022-A8E7-46B3-B64E-99D217E9B6AC@yahoo.com> To: Mark Millard X-Mailer: iPhone Mail (19G71) X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Rspamd-Queue-Id: 4M1Ds46Nvsz3cxM X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Will do. I=E2=80=99ll commit the suggested change to main tomorrow. Thank you for your vigilant investigation. Glen Sent from my phone. Please excuse my brevity and/or typos. > On Aug 7, 2022, at 3:50 PM, Mark Millard wrote: >=20 > =EF=BB=BFOn 2022-Aug-7, at 12:32, Glen Barber wrote: >=20 >> Correct, it was set to =E2=80=9C0=E2=80=9D for these builds. >>=20 >> I honestly do not have any idea where the problems you are seeing are cre= eping in. >>=20 >> Should it be set back to =E2=80=9C1=E2=80=9D? I=E2=80=99m not sure how t= o proceed otherwise. >=20 > My guess is that if the release/tools/arm.subr line: >=20 > chroot ${CHROOTDIR} gpart add -t freebsd-ufs -a 64k ${mddev}s= 2 >=20 > was instead (note the added -b use): >=20 > chroot ${CHROOTDIR} gpart add -t freebsd-ufs -b 64k -a 64k ${= mddev}s2 >=20 > then the line: >=20 > chroot ${CHROOTDIR} newfs -U -L rootfs /dev/${mddev}s2a >=20 > would work as expected and things would still be aligned: > no aliasing of BSD vs. freebsd-ufs. (In part this is by > prior steps already having achieved alignment of BSD.) >=20 > But I do not know how to classify doing so: Work around? > Known required-procedure for -L rootfs to correctly > identify the the freebsd-ufs /dev/${mddev}s2a ? >=20 > Absent better information from folks that know more, I'd > suggest trying such an adjusted release/tools/arm.subr > next week, leaving kern.geom.part.mbr.enforce_chs=3D0 in > place, if such an experiment can be reasonable. >=20 >> Glen >> Sent from my phone. >> Please excuse my brevity and/or typos.