Date: Fri, 22 Jul 2022 12:45:30 +0000 From: Glen Barber <gjb@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: Warner Losh <imp@bsdimp.com>, Ed Maste <emaste@freebsd.org>, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, dev-commits-src-main@freebsd.org, "Dr. Rolf Jansen" <freebsd-rj@cyclaero.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: git: 1dfcff294e44 - main - release: increase IMAGE_SIZE for arm, arm64, riscv [odd alignment for SBC images] Message-ID: <20220722124530.GM30607@FreeBSD.org> In-Reply-To: <D630043D-6EAC-4216-A046-910DB64F8B4A@yahoo.com> References: <16906DFD-286B-4D59-9438-CA9CD9026C55@yahoo.com> <202207171708.26HH81bA062303@gndrsh.dnsmgr.net> <CAPyFy2D1aBe8h4kq=RqCR2tkEiEXh_pHNEqaAnW7tk9-HxCmBQ@mail.gmail.com> <20220719204245.GL30607@FreeBSD.org> <CANCZdfoABLggPQgDeCZ5FzYCf8243kvr-p8Bj5_JGNnEszGHBw@mail.gmail.com> <D630043D-6EAC-4216-A046-910DB64F8B4A@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--+YUU1pJ1U2q9bSvj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 20, 2022 at 10:08:20AM -0700, Mark Millard wrote: > On 2022-Jul-19, at 15:45, Warner Losh <imp@bsdimp.com> wrote: >=20 > > On Tue, Jul 19, 2022, 2:42 PM Glen Barber <gjb@freebsd.org> wrote: > >>> . . . > >>=20 > >> My concern with this is kern.geom.part.mbr.enforce_chs is always '1' on > >> the builders, which effectively means all arm builds will fail every > >> time. I think we need to get to the actual root of the problem here, > >> versus applying band-aids to a shark bite. > >=20 > > I think this is the actual problem. While such pedantry can be useful f= or ancient picky BIOSes, these days only the LBA fields of the MBR are used= =2E And the fake BIOS geometry is crazy weird. We can likely tweak it to be= more friendly.=20 > >=20 > > Why is it =3D=3D 1 on the builder? If people want things aligned gpart = has an option for years iirc to do that. And we want that off for the build= s. >=20 > Would it seem appropriate to use a week (this week?) to do all > the snapshot builds with the builders all set to have > kern.geom.part.mbr.enforce_chs=3D0 and see what breaks, if anything? > (Sort of a snapshot exp run.) >=20 Sorry, it is too late for this week's snapshots, but I will set it to '0' for next week's (I was out the past two days, so did not see this email until now). > More than just the SBC images might be involved for > kern.geom.part.mbr.enforce_ch consequences, for all I know. >=20 This vaguely rings a bell. I am still trying to find the original problem being reported that caused me to set enforce_csh=3D1, but I have not had much luck. I do recall it being a strange case that enforce_csh=3D1 had apparently fixed (or masked something else going on). Glen --+YUU1pJ1U2q9bSvj Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmLam+UACgkQAxRYpUeP 4pPlgRAAiqGGR4NL+bdFSruB/9DycuO7ZyVVUMb7hFMcQDiCzBF3cR30WVRzsWtW KGaXttwBMC7dMPsYdChR8K6PZeQALWRbov5SoVW4xoh64jGLuYDimVY955C0t9P1 Sha0wnp+JYDkXZEnxI43MTBaJKEob9HHUqJJrowEkFQkDyL37wYsruVg2TcmTyjV a9PoNumpIlRX8bsZAcRLNLL70Yl9MFw+bEIJsVhJpPC0Y+k7sxq1pEolOrZJWO+z mrjRByNASZwiBy1qolTDhhCFXdc4jie3hFzr+D8sHM1/phr/rkmG9nv7qlQyP5+b SE9ld/qrHzoes60jWw8j9fJp+w4GwCjHV9ZkrLl2lfBMRd9+HW5sJzKuSG73wftJ nZW2bm+2FAfpwzLQZKPJeFKcHcBnmRpGU/ffPtzWO8yeVTC+EMTYxfabIYcuJ/ZY keNQ+DCIf6OByqacILOy2WrPFJt8fncI/JTwWjFTXZuhahk/0ZK2R327fV9zREXc FoHBm2TEAo5gUICNcnozdP9PNH3F15VfALn1S4Uh3oB5TAtUSnASyYrHIwCJ2Dif jImyajnj8Ml8ioawWpRxMhOdmRPVDTngLPZhB9X4FZ89i1jt0CNNbrZ00CKqWfwR 28uBqUy3luB8+zY6SHAJSYFfIV9Idz7LXcw0jQ3SmonKs+tar+M= =OPeq -----END PGP SIGNATURE----- --+YUU1pJ1U2q9bSvj--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220722124530.GM30607>