Date: Tue, 5 Jan 2021 14:39:38 -0800 From: Mark Millard <marklmi@yahoo.com> To: Mark Murray <mrvmurray@icloud.com> Cc: freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: aarch64 based on main 58661b3ba9eb : panic for "ufs_dirbad: /: bad dir ino 66371814 at offset 106496: mangled entry" Message-ID: <5D99B7D1-CDF6-4C96-AF62-ADF9626639CF@yahoo.com> In-Reply-To: <3420FB5B-6499-42E5-8FFE-F9BF57CCECE7@icloud.com> References: <D0D027B5-8CF1-46F7-A5D5-DDC61C198822.ref@yahoo.com> <D0D027B5-8CF1-46F7-A5D5-DDC61C198822@yahoo.com> <3420FB5B-6499-42E5-8FFE-F9BF57CCECE7@icloud.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Jan-5, at 13:28, Mark Murray <mrvmurray at icloud.com> wrote: >> On 5 Jan 2021, at 20:15, Mark Millard <marklmi at yahoo.com> wrote: >>=20 >> The machine is a MACCHIATOBin Double Shot. >=20 > Thanks for the warning :-) >=20 > I'm using an MBin/DS as my firewall/gateway, and in its Copious Free = Time=E2=84=A2, an ARM64 build-box. >=20 > How recent is your UEFI SD boot image? Are you maintaining a history = and download site? >=20 [Note: This reply has no information related to the problem report. I'm just answering other questions.] I was given a UEFI materials to use a fair time ago and they have worked sufficiently for my use. Absent a FreeBSD port that I can use to build UEFI updates in a normal, ports-style way, I've left it alone in this area. The UEFI screen reports: MARVELL UEFI 18.09.0 The boot sequence reports: BootROM - 2.03 Starting CP-0 IOROM 1.07 Booting from SD 0 (0x29) Found valid image at boot postion 0x000 lNOTICE: Starting binary extension NOTICE: SVC: SW Revision 0x0. SVC is not supported mv_ddr: mv_ddr-armada-18.09.2-g99d7725 (Oct 29 2018 - 23:32:10) mv_ddr: completed successfully NOTICE: Cold boot NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(release):v1.5-219-g711ecd3 (Marvell-armada-18.09.4) NOTICE: BL1: Built : 23:32:27, Oct 29 2018 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(release):v1.5-219-g711ecd3 (Marvell-armada-18.09.4) NOTICE: BL2: Built : 23:32:35, Oct 29 2018 BL2: Initiating SCP_BL2 transfer to SCP NOTICE: SCP_BL2 contains 5 concatenated images NOTICE: Skipping MSS CP3 related image NOTICE: Skipping MSS CP2 related image NOTICE: Load image to CP1 MSS AP0 NOTICE: Loading MSS image from addr. 0x40265f4 Size 0x1ad8 to MSS at = 0xf4280000 NOTICE: Done NOTICE: Load image to CP0 MSS AP0 NOTICE: Loading MSS image from addr. 0x40280cc Size 0x1ad8 to MSS at = 0xf2280000 NOTICE: Done NOTICE: Load image to AP0 MSS NOTICE: Loading MSS image from addr. 0x4029ba4 Size 0x4a40 to MSS at = 0xf0580000 NOTICE: Done NOTICE: BL1: Booting BL31 lNOTICE: BL31: v1.5(release):v1.5-219-g711ecd3 (Marvell-armada-18.09.4) NOTICE: BL31: Built : 23:32:47, Oct 29 2018 Armada 8040 MachiatoBin Platform Init (I'll stop with that.) One issue is that between: Booting [/boot/kernel/kernel]... =20 |=08/=08-=08\=08No valid device tree blob found! WARNING! Trying to fire up the kernel, but no device tree blob found! and: Setting hostuuid: **REPLACED**. Setting hostid: **REPLACED**. Starting file system checks: there is no output to the serial console. If I ever have problems in that time frame, recovery would be a problem unless I found a better UEFI variation to put in place, one that outputs everything to the serial console. As for my use, no history/download site, nothing externally visible at all. No use as a firewall or gateway either. But I do some aarch64 and armv7 builds on it. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5D99B7D1-CDF6-4C96-AF62-ADF9626639CF>