Date: Fri, 17 Jul 2020 15:04:15 -0700 From: Mark Millard <marklmi@yahoo.com> To: freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Pine64+2GB unable to boot after attempted update, failure very early: efipart_readwrite: rw=1, blk=... size=32 status=7; RPi3 has no problem Message-ID: <B7E94C19-DB4E-4CF8-A981-2616FEF94E7B@yahoo.com> In-Reply-To: <B719FBD3-F26C-40A9-8CA1-4FE89ADE4222@yahoo.com> References: <F9305636-79D0-4A0A-9CE3-F27CED51A9A5@yahoo.com> <B719FBD3-F26C-40A9-8CA1-4FE89ADE4222@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Jul-16, at 23:15, Mark Millard <marklmi at yahoo.com> wrote: > [Trying again: I missed removing a type of character (escape) > beyond the [?25h removals. My choice of editor was not the > best for the context and it was not obvious that the > escapes were present.] >=20 > I'll mostly just send the text that has the > additional removals. The boot text with the error > messages then is: >=20 >=20 > U-Boot SPL 2020.07 (Jul 13 2020 - 12:12:14 +0000) > DRAM: 2048 MiB > Trying to boot from MMC1 > NOTICE: BL31: v2.3(): > NOTICE: BL31: Built : 23:56:54, Apr 26 2020 > NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689) > NOTICE: BL31: Found U-Boot DTB at 0x4092b68, model: Pine64+ > NOTICE: PSCI: System suspend is unavailable > alloc space exhausted >=20 >=20 > U-Boot 2020.07 (Jul 13 2020 - 12:12:14 +0000) Allwinner Technology >=20 > CPU: Allwinner A64 (SUN50I) > Model: Pine64+ > DRAM: 2 GiB > MMC: mmc@1c0f000: 0 > Loading Environment from FAT... *** Warning - bad CRC, using default = environment >=20 > In: serial > Out: serial > Err: serial > Net: phy interface7 > eth0: ethernet@1c30000 > starting USB... > Bus usb@1c1a000: USB EHCI 1.00 > Bus usb@1c1a400: USB OHCI 1.0 > Bus usb@1c1b000: USB EHCI 1.00 > Bus usb@1c1b400: USB OHCI 1.0 > scanning bus usb@1c1a000 for devices... 1 USB Device(s) found > scanning bus usb@1c1a400 for devices... 1 USB Device(s) found > scanning bus usb@1c1b000 for devices... 3 USB Device(s) found > scanning bus usb@1c1b400 for devices... 1 USB Device(s) found > scanning usb for storage devices... 1 Storage Device(s) found > Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20 > switch to partitions #0, OK > mmc0 is current device > Scanning mmc 0:1... > 38612 bytes read in 4 ms (9.2 MiB/s) > Found EFI removable media binary efi/boot/bootaa64.efi > Scanning disk mmc@1c0f000.blk... > ** Unrecognized filesystem type ** > Scanning disk usb_mass_storage.lun0... > ** Unrecognized filesystem type ** > ** Unrecognized filesystem type ** > ** Unrecognized filesystem type ** > Found 7 disks > 7[r[999;999H[6n8BootOrder not defined > EFI boot manager: Cannot load any image > 695648 bytes read in 33 ms (20.1 MiB/s) > [2J[1;1H[2J[1;1HConsoles: EFI console =20 >=20 >=20 > |/-\|/-\| Reading loader env vars from /efi/freebsd/loader.env >=20 >=20 > Setting currdev to disk0p1: >=20 >=20 > /-\|/-FreeBSD/arm64 EFI loader, Revision 1.1 >=20 >=20 >=20 >=20 >=20 > Command line arguments: loader.efi >=20 >=20 > Image base: 0xb8e63000 >=20 >=20 > EFI version: 2.80 >=20 >=20 > EFI Firmware: Das U-Boot (rev 8224.1792) >=20 >=20 > Console: comconsole (0) >=20 >=20 > Load Path: /efi\boot\bootaa64.efi >=20 >=20 > Load Device: = /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x403= b,0x1ffe0) >=20 >=20 > Trying ESP: = /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x403= b,0x1ffe0) >=20 >=20 > Setting currdev to disk0p1: >=20 >=20 > \|/-\|/-\|/-Trying: = /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x244= 00,0xe600000) >=20 >=20 > Setting currdev to disk0p2: >=20 >=20 > \|/-\|efipart_readwrite: rw=3D1, blk=3D123244224 size=3D32 status=3D7 >=20 >=20 > /efipart_readwrite: rw=3D1, blk=3D148608 size=3D32 status=3D7 >=20 >=20 > -efipart_readwrite: rw=3D1, blk=3D148545 size=3D32 status=3D7 >=20 >=20 > efipart_readwrite: rw=3D1, blk=3D148545 size=3D32 status=3D7 >=20 >=20 > \efipart_readwrite: rw=3D1, blk=3D148608 size=3D32 status=3D7 >=20 >=20 > |efipart_readwrite: rw=3D1, blk=3D148545 size=3D32 status=3D7 >=20 >=20 > efipart_readwrite: rw=3D1, blk=3D148545 size=3D32 status=3D7 >=20 >=20 > /efipart_readwrite: rw=3D1, blk=3D148608 size=3D32 status=3D7 >=20 >=20 > -efipart_readwrite: rw=3D1, blk=3D148545 size=3D32 status=3D7 >=20 >=20 > efipart_readwrite: rw=3D1, blk=3D148545 size=3D32 status=3D7 >=20 >=20 > ERROR: cannot open /boot/lua/loader.lua: no such file or directory. >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > Type '?' for a list of commands, 'help' for more detailed help. >=20 >=20 > OK=20 >=20 >=20 >=20 >=20 >=20 > The contrasting RPi3B text near the area with first errors above: >=20 >=20 >=20 > \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08Trying: = /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x244= 00,0xe600000) >=20 >=20 > Setting currdev to disk0p2: >=20 >=20 > = \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08= |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08Lo= ading /boot/defaults/loader.conf >=20 >=20 > /=08-=08\=08|=08/=08-=08\=08Loading /boot/defaults/loader.conf >=20 >=20 > Loading /boot/device.hints >=20 >=20 > |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08Loading = /boot/loader.conf >=20 >=20 > |=08/=08-=08\=08Loading /boot/loader.conf.local >=20 >=20 >=20 > (I'll not list more.) >=20 > For reference: >=20 > # gpart show -p > =3D> 63 249737153 mmcsd0 MBR (119G) > 63 16380 - free - (8.0M) > 16443 131040 mmcsd0s1 fat32lba [active] (64M) > 147483 997 - free - (499K) > 148480 241172480 mmcsd0s2 freebsd (115G) > 241320960 8416256 - free - (4.0G) >=20 > =3D> 0 241172480 mmcsd0s2 BSD (115G) > 0 230686720 mmcsd0s2a freebsd-ufs (110G) > 230686720 10485760 - free - (5.0G) >=20 > =3D> 40 468862048 da0 GPT (224G) > 40 2008 - free - (1.0M) > 2048 413138944 da0p1 freebsd-ufs (197G) > 413140992 6291456 da0p2 freebsd-swap (3.0G) > 419432448 6291456 da0p4 freebsd-swap (3.0G) > 425723904 43138184 - free - (21G) >=20 > # find /boot/efi/ -print | sort | more > /boot/efi/ > /boot/efi/COPYING.linux > /boot/efi/EFI > /boot/efi/EFI/BOOT > /boot/efi/EFI/BOOT/bootaa64.efi > /boot/efi/LICENCE.broadcom > /boot/efi/System Volume Information > /boot/efi/System Volume Information/WPSettings.dat > /boot/efi/armstub8.bin > /boot/efi/bcm2710-rpi-2-b.dtb > /boot/efi/bcm2710-rpi-3-b-plus.dtb > /boot/efi/bcm2710-rpi-3-b.dtb > /boot/efi/bcm2710-rpi-cm3.dtb > /boot/efi/bootcode.bin > /boot/efi/config.txt > /boot/efi/dtb > /boot/efi/dtb/allwinner > /boot/efi/dtb/allwinner/sun50i-a64-pine64-lts.dtb > /boot/efi/dtb/allwinner/sun50i-a64-pine64-plus.dtb > /boot/efi/dtb/allwinner/sun50i-a64-pine64.dtb > /boot/efi/dtb/allwinner/sun50i-a64-pinebook.dtb > /boot/efi/dtb/allwinner/sun50i-a64-sopine-baseboard.dtb > /boot/efi/dtb/overlays > /boot/efi/dtb/overlays/spigen-rpi3.dtbo > /boot/efi/dtb/overlays/sun50i-a64-opp.dtbo > /boot/efi/dtb/overlays/sun50i-a64-pwm.dtbo > /boot/efi/dtb/overlays/sun50i-a64-rpwm.dtbo > /boot/efi/dtb/overlays/sun50i-a64-spi0-spigen.dtbo > /boot/efi/dtb/overlays/sun50i-a64-timer.dtbo > /boot/efi/fixup.dat > /boot/efi/overlays > /boot/efi/overlays/disable-bt.dtbo > /boot/efi/overlays/mmc.dtbo > /boot/efi/overlays/pwm.dtbo > /boot/efi/start.elf > /boot/efi/u-boot.bin >=20 > (Where /boot/efi refers to /dev/mmcsd0s1 .) >=20 > I forgot to indicate: that the context is based > on head -r363123 FreeBSD and -r542111 ports. >=20 Well, I've had back-to-back boot attempts go from fails to works, same media. It may just be the old Pine64+2GB is no longer reliable (in one or more ways). Outside the Pine64+2GB context, I've no evidence of the microsd card being problematical. I've some past evidence of USB failing on occasion on the Pine64+2GB. Difficult to tell if such hardware problems are the overall issue. The timing of the the recent boot failure failures starting also might point at the updated sysutils/u-boot-pine64 material. (FreeBSD had been updated previous to the u-boot update.) Using the RPi3B I'd moved where mmcsd0s2 started on the microsd card after the prior reports, but that had made no difference in the behavior for a time and so is not likely to be related to the boot attempt that worked. For now I'm going to ignore such Pine64+2GB boot failures relative to list reporting. (That still leaves me with Rock64 booting being broken buy head -r363122 / -r363213 . powerpc64 and 32-bit powerpc are still untested for head -r363123. Given problems with 32-bit powerpc having the kernel zero-out pages of user-process memory [known problem], I'm not so sure it will get any testing.) =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?B7E94C19-DB4E-4CF8-A981-2616FEF94E7B>