Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Jul 2022 20:34:29 +0000
From:      Glen Barber <gjb@freebsd.org>
To:        Mark Millard <marklmi@yahoo.com>
Cc:        dev-commits-src-main@freebsd.org
Subject:   Re: git: 1dfcff294e44 - main - release: increase IMAGE_SIZE for arm, arm64, riscv
Message-ID:  <20220713203429.GZ30607@FreeBSD.org>
In-Reply-To: <20220713201327.GY30607@FreeBSD.org>
References:  <84410D65-6F86-44E5-8B14-8A523C9919C7.ref@yahoo.com> <84410D65-6F86-44E5-8B14-8A523C9919C7@yahoo.com> <20220713201327.GY30607@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--G2f4KVJdnHWgnG1a
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 13, 2022 at 08:13:27PM +0000, Glen Barber wrote:
> On Wed, Jul 13, 2022 at 12:06:55PM -0700, Mark Millard wrote:
> > Glen Barber <gjb_at_FreeBSD.org> wrote on
> > Date: Wed, 13 Jul 2022 18:37:34 UTC :
> >=20
> > > The branch main has been updated by gjb:
> > >=20
> > > URL: https://cgit.FreeBSD.org/src/commit/?id=3D1dfcff294e44d4b4581328=
8ef4095c36abb22f0e
> > >=20
> > > commit 1dfcff294e44d4b45813288ef4095c36abb22f0e
> > > Author:     Glen Barber <gjb@FreeBSD.org>
> > > AuthorDate: 2022-07-13 18:36:22 +0000
> > > Commit:     Glen Barber <gjb@FreeBSD.org>
> > > CommitDate: 2022-07-13 18:36:22 +0000
> > >=20
> > >     release: increase IMAGE_SIZE for arm, arm64, riscv
> > >    =20
> > >     Related to:     PR 264032
> > >     MFC after:      5 minutes
> > >     Sponsored by:   Rubicon Communications, LLC ("Netgate")
> >=20
> > I may have some evidence that, for example,
> >=20
> > http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/14.0/FreeBSD-1=
4.0-CURRENT-arm64-aarch64-RPI-20220708-a0b956f5ac5-256605.img.xz
> >=20
> > and:
> >=20
> > http://ftp3.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/13.1/FreeBSD-13=
=2E1-RELEASE-arm-armv6-RPI-B.img.xz
> >=20
> > were not built fully via the /usr/src/release procedures
> > using modern builds of mdconfig and such. The below is
> > taken from a different list exchange.
> >=20
> > QUOTE
> > I tried what it looks to me the /usr/src/release/
> > code would do initially for arm64/RPI.conf (but with
> > my file naming and an explicit -u0 style of use):
> >=20
> > # truncate -s3072m mmjnk.test
> > # mdconfig -u0 -fmmjnk.test -x63 -y255
> > # gpart create -sMBR md0
> > md0 created
> > # gpart show md0
> > =3D>     63  6291393  md0  MBR  (3.0G)
> >       63  6291393       - free -  (3.0G)
> > # gpart add -t'!12' -a512k -s50m -b1m md0
> > md0s1 added
> > # gpart show md0
> > =3D>     63  6291393  md0  MBR  (3.0G)
> >       63     1985       - free -  (993K)
> >     2048   102400    1  fat32lba  (50M)
> >   104448  6187008       - free -  (3.0G)
> >=20
> > I tried the same sequence in a chroot into a 13.0-RELEASE-p11
> > tree on an aarch64 main [so: 14] machine. I got the same result.
> >=20
> > But such is not what the 13.1-RELEASE build produced, for
> > example:
> >=20
> > # mdconfig -u0 -fFreeBSD-13.1-RELEASE-arm64-aarch64-RPI.img -x63 -y255
> > # gpart show md0
> > =3D>     63  6291393  md0  MBR  (3.0G)
> >       63     2016       - free -  (1.0M)
> >     2079   102312    1  fat32lba  [active]  (50M)
> >   104391  6187041    2  freebsd  (3.0G)
> >  6291432       24       - free -  (12K)
> >=20
> > (There are no 13.1-STABLE snapshots available to download
> > and look at.)
> >=20
> > Looking at the recent 14.0-CURRENT snapshot:
> >=20
> > # mdconfig -u0 -fFreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20220708-a0b956=
f5ac5-256605.img -x63 -y255
> > # gpart show md0
> > =3D>     63  6291393  md0  MBR  (3.0G)
> >       63     2016       - free -  (1.0M)
> >     2079   102312    1  fat32lba  [active]  (50M)
> >   104391  6187041    2  freebsd  (3.0G)
> >  6291432       24       - free -  (12K)
> >=20
> > So, also not matching.
> > END QUOTE
> >=20
>=20
> There are no local configurations on the builders that would produce
> differing output.  Why, though, are you specifying '-x' and '-y' to
> mdconfig?  I think that may be obfuscating something when attaching the
> image as an md(4) device.
>=20

Also, if you haven't already seen it, PR 264032 suggests there may be
a bug, notably this comment:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264032#c17

I forgot to include this in my reply.

Glen


--G2f4KVJdnHWgnG1a
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmLPLFUACgkQAxRYpUeP
4pNc3A/9HxNcnytJz1T9a2SemXttxSn9LzbkZz7HmGOu3vwHZNETP+Q6x6ypENGB
/5jVyxESCLucCSohOfCBI5K7AQsxvJ9tPXKQNKB5LlXl0QoIS7MazwU5pII1XA7v
g2O9bMgJ7+agaYB48fIwi9PPkON4DnkIGQ009+3z9WfoPEXWPuTAuJgTwcErGrfj
IE+tyy1D4pi/yy75vbUe/gW3DkppX3Th9caW9bItjM5TaxPEwof5jU9nJn5lOS4X
S+KHWdK76Cj2VCB8Z+WMUMRD36DBAX/M8gYp0gQTDlyfAm4GhxuTfIOSOtYoe5QJ
w8jBLp0aaKFWsngZNP83BVvOPDQV6Dmza0tRUNqnZLSQ64n4xUwKjGs9oqKg+MpG
LKBGd/7CnALTdRWIhNrjbIQhI+COoqmtt8r+NDYEgJpA8IFGe2lvIEW1OkeRYV0z
6nOz/xFSAVBmqBbdqVwEpRMRJxMgVpRT2wR1KyDw/G39s6NRatsNeu0SSzROcbkd
yFRkeDrlkVfomEAvsWC319gQqUcMu4943hQSX2DOUlRIhAXn2jPXrGiYhpYcqTap
jhVM80cwKBD6A0lBXpp4Noai/VrytDnTxYGD08VvQzPiF5Mj82Fe+1p0z0JfDd6Y
/MQRnaqhvcEVnCUaxxcYFWGconP1cPOTW0he43lFN5wfToxKc68=
=F5jM
-----END PGP SIGNATURE-----

--G2f4KVJdnHWgnG1a--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220713203429.GZ30607>