Date: Tue, 16 Mar 2021 02:53:41 -0700 From: Mark Millard <marklmi@yahoo.com> To: Mark Murray <mrvmurray@icloud.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: aarch64 based on main 58661b3ba9eb : panic for "ufs_dirbad: /: bad dir ino 66371814 at offset 106496: mangled entry" Message-ID: <13F0E8C6-639D-4529-8348-79DDCCC3B4F4@yahoo.com> In-Reply-To: <5D99B7D1-CDF6-4C96-AF62-ADF9626639CF@yahoo.com> References: <D0D027B5-8CF1-46F7-A5D5-DDC61C198822.ref@yahoo.com> <D0D027B5-8CF1-46F7-A5D5-DDC61C198822@yahoo.com> <3420FB5B-6499-42E5-8FFE-F9BF57CCECE7@icloud.com> <5D99B7D1-CDF6-4C96-AF62-ADF9626639CF@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Jan-5, at 14:39, Mark Millard <marklmi at yahoo.com> wrote: > On 2021-Jan-5, at 13:28, Mark Murray <mrvmurray at icloud.com> wrote: >=20 >>> 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 >=20 > [Note: This reply has no information related to the problem > report. I'm just answering other questions.] >=20 > 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: >=20 > MARVELL UEFI 18.09.0 >=20 > The boot sequence reports: >=20 > BootROM - 2.03 >=20 > Starting CP-0 IOROM 1.07 >=20 > Booting from SD 0 (0x29) >=20 > Found valid image at boot postion 0x000 >=20 > 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 >=20 > Armada 8040 MachiatoBin Platform Init >=20 > (I'll stop with that.) >=20 > One issue is that between: >=20 > 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! >=20 > and: >=20 > Setting hostuuid: **REPLACED**. > Setting hostid: **REPLACED**. > Starting file system checks: >=20 > 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. >=20 >=20 > 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. >=20 FYI on what I was using and am now using: I discovered that what I'd been using is an exact copy of the content of: = https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/wiki/files= /flash-image-18.09.4.bin despite getting it via: = https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image2.= bin originally. But . . . I just switched to using a copy of: https://people.freebsd.org/~manu/flash-image-2020-07-01-mainline-tfa.bin which looks to be a copy of: = https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image-2= 020-07-01-mainline-tfa.bin I dd'd it to a microsd card on a different FreeBSD machine, via: dd if=3Dflash-image-2020-07-01-mainline-tfa.bin of=3D/dev/mmcsd1 bs=3D512 = seek=3D1 conv=3Dsync status=3Dprogress With this media I get to see the kernel output that was missing before and so would have a chance of gathering evidence if there was a boot problem. I still have never tried to use the PCIe bus. A verbose boot reported: pcib0: <Generic PCI host controller> on acpi0 pcib0: Bus is cache-coherent pcib0: ECAM for bus 0-0 at mem e0000000-e00fffff pci0: <PCI bus> on pcib0 pci0: domain=3D0, physical bus=3D0 but that was all for pci*. pciconf -l reported an empty output. The uefi build was, apparently, a debug build so earlier there was: 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-devel-18.08.0-ga881467 (Jul 01 2020 - 21:18:08) mv_ddr: completed successfully NOTICE: Cold boot NOTICE: Booting Trusted Firmware NOTICE: BL1: v2.3(release):v2.3-269-g568a88172-dirty = (Marvell-devel-18.12.0) NOTICE: BL1: Built : 21:19:59, Jul 1 2020 NOTICE: BL1: Booting BL2 NOTICE: BL2: v2.3(release):v2.3-269-g568a88172-dirty = (Marvell-devel-18.12.0) NOTICE: BL2: Built : 21:20:00, Jul 1 2020 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. 0x40269f4 Size 0x1cd8 to MSS at = 0xf4280000 NOTICE: Done NOTICE: Load image to CP0 MSS AP0 NOTICE: Loading MSS image from addr. 0x40286cc Size 0x1cd8 to MSS at = 0xf2280000 NOTICE: Done NOTICE: Load image to AP0 MSS NOTICE: Loading MSS image from addr. 0x402a3a4 Size 0x5420 to MSS at = 0xf0580000 NOTICE: Done NOTICE: SCP Image doesn't contain PM firmware NOTICE: BL1: Booting BL31 lNOTICE: MSS PM is not supported in this build NOTICE: BL31: v2.3(release):v2.3-269-g568a88172-dirty = (Marvell-devel-18.12.0) NOTICE: BL31: Built : 21:19:59, Jul 1 2020 . . . Armada Platform Init Comphy0-0: PCIE0 5 Gbps =20 Comphy0-1: PCIE0 5 Gbps =20 Comphy0-2: PCIE0 5 Gbps =20 Comphy0-3: PCIE0 5 Gbps =20 Comphy0-4: SFI 10.31 Gbps Comphy0-5: SATA1 5 Gbps =20 Comphy1-0: SGMII1 1.25 Gbps=20 Comphy1-1: SATA2 5 Gbps =20 Comphy1-2: USB3_HOST0 5 Gbps =20 Comphy1-3: SATA3 5 Gbps =20 Comphy1-4: SFI 10.31 Gbps Comphy1-5: SGMII2 3.125 Gbps UTMI PHY 0 initialized to USB Host0 UTMI PHY 1 initialized to USB Host1 UTMI PHY 2 initialized to USB Host0 . . . add-symbol-file = /home/greg/src/github.com/tianocore/edk2/Build/Armada80x0McBin-AARCH64/DEB= UG_CLANG38/AARCH64/ArmPkg/Drivers/ArmPciCpuIo2Dxe/ArmPciCpuIo2Dxe/DEBUG/Ar= mPciCpuIo2Dxe.dll 0xBF79D000 Loading driver at 0x000BF79C000 EntryPoint=3D0x000BF79D03C = ArmPciCpuIo2Dxe.efi . . . add-symbol-file = /home/greg/src/github.com/tianocore/edk2/Build/Armada80x0McBin-AARCH64/DEB= UG_CLANG38/AARCH64/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciHostBridgeDxe/= DEBUG/PciHostBridgeDxe.dll 0xBF6AE000 Loading driver at 0x000BF6AD000 EntryPoint=3D0x000BF6AE03C = PciHostBridgeDxe.efi WaitForLink: no PCIE device detected (Not that I know how to interpret all that.) I've not tried it but there seems to be a: https://people.freebsd.org/~manu/flash-image-mcbin.bin that is possibly 4 days newer than what I used. It might be from experiments with building the sysutils/edk2 port and trying to use the result. ( I've no clue how to accurately rebuild flash-image-2020-07-01-mainline-tfa.bin . Being able to rebuild in a known way could be an advantage to using a working port.) There is also: https://people.freebsd.org/~manu/flash-image-2020-07-01.bin and: = https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image-2= 020-07-01.bin that I have not tried. =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?13F0E8C6-639D-4529-8348-79DDCCC3B4F4>