Date: Sat, 28 Mar 2020 17:14:16 -0700 From: Mark Millard <marklmi@yahoo.com> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: FYI: head -r358966 -> -r359736 and RPi4: -r359736 fails to boot (unless I use boot -v) where -r358966 booted fine before update Message-ID: <B501E3CD-A76E-4D9F-A7AA-70F2D2087BBC@yahoo.com> References: <B501E3CD-A76E-4D9F-A7AA-70F2D2087BBC.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I use a microsd card that is set up for booting both
a Rock64 and a RPi4: the dd'd u-boot vs. the RPi4
specific materials are in independent places and
the rest is shared and rather generic.
So at head -r358966 I'd been able to both the
Rock64 and the RPi4 from the same media.
Now with head -r359736 in place instead:
A) The Rock64 boots via that media just fine.
B) The RPi4 fails to boot (nothing special
like "boot -v").
C) The RPi4 with "boot -v" boots just fine.
(This makes identifying the issue non-obvious.)
For (B, i.e., no boot -v):
. . .
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]... =20
. . .
Release APs...done
CPU 0: ARM Cortex-A72 r0p3 affinity: 0
Trying to mount root from ufs:/dev/label/RPi4root [rw,noatime]...
=20
. . . (looks normal until after the CPU 3 line) . . .
CPU 1: ARM Cortex-A72 r0p3 affinity: 1
CPU 2: ARM Cortex-A72 r0p3 affinity: 2
CPU 3: ARM Cortex-A72 r0p3 affinity: 3
sdhci_bcm0-slot0: Controller timeout
sdhci_bcm0-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D REGISTER =
DUMP =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
sdhci_bcm0-slot0: Sys addr: 0x000006c8 | Version: 0x00001002
sdhci_bcm0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000001
sdhci_bcm0-slot0: Argument: 0x0ee2afc1 | Trn mode: 0x00000036
sdhci_bcm0-slot0: Present: 0x1fff0a06 | Host ctl: 0x00000007
sdhci_bcm0-slot0: Power: 0x0000000f | Blk gap: 0x00000080
sdhci_bcm0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107
sdhci_bcm0-slot0: Timeout: 0x00000003 | Int stat: 0x00000000
sdhci_bcm0-slot0: Int enab: 0x01ff003b | Sig enab: 0x01ff003b
sdhci_bcm0-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000
sdhci_bcm0-slot0: Caps: 0x45ee6432 | Caps2: 0x0000a525
sdhci_bcm0-slot0: Max curr: 0x00080008 | ADMA err: 0x00000000
sdhci_bcm0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000
sdhci_bcm0-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
Root mount waiting for: CAM
Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for =
10 more seconds
Mounting from ufs:/dev/label/RPi4root failed with error 2.
Loader variables:
vfs.root.mountfrom=3Dufs:/dev/label/RPi4root
vfs.root.mountfrom.options=3Drw,noatime
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:/dev/cd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot> ?
List of GEOM managed disk devices:
mmcsd0
mountroot>=20
So far the above has been 100% repeating.
For (C, i.e., boot -v in use):
. . .
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel] in 9 seconds...=20
Type '?' for a list of commands, 'help' for more detailed help.
OK boot -v
. . .
. . .
Release APs...done
CPU 0: ARM Cortex-A72 r0p3 affinity: 0
Trying to mount root from ufs:/dev/label/RPi4root [rw,noatime]...
. . .
CPU 1: ARM Cortex-A72 r0p3 affinity: 1
CPU 2: ARM Cortex-A72 r0p3 affinity: 2
CPU 3: ARM Cortex-A72 r0p3 affinity: 3
Root mount waiting for:regulator: shutting down unused regulators
CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Warning: no time-of-day clock registered, system time will not be set =
accurately
start_init: trying /sbin/init
Setting hostuuid: REPLACED.
Setting hostid: REPLACED.
Starting file system checks:
/dev/label/RPi4root: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/label/RPi4root: clean, 19057570 free (498234 frags, 2319917 blocks, =
1.8% fragmentation)
. . .
=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?B501E3CD-A76E-4D9F-A7AA-70F2D2087BBC>