Date: Sun, 29 Mar 2020 09:12:42 +0200 From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> To: Mark Millard <marklmi@yahoo.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FYI: head -r358966 -> -r359376 and RPi4: -r359376 fails to boot (unless I use boot -v) where -r358966 booted fine before update Message-ID: <eff57f3d-097f-ce15-f919-61f1971e8eb0@plan-b.pwste.edu.pl> In-Reply-To: <AB6A78AD-DB89-446E-B150-CA3AC8BE0B67@yahoo.com> References: <B501E3CD-A76E-4D9F-A7AA-70F2D2087BBC@yahoo.com> <147DDCEF-C081-4237-A81E-AEBCD71AB016@yahoo.com> <AB6A78AD-DB89-446E-B150-CA3AC8BE0B67@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --oFeBLMH5zyUY9QqSL9U6hqhgzKYZRP9Y4 Content-Type: multipart/mixed; boundary="fxWP5blVh2munGe8b4EgxjW6L4QOfVsdy"; protected-headers="v1" From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> To: Mark Millard <marklmi@yahoo.com>, freebsd-arm <freebsd-arm@freebsd.org> Message-ID: <eff57f3d-097f-ce15-f919-61f1971e8eb0@plan-b.pwste.edu.pl> Subject: Re: FYI: head -r358966 -> -r359376 and RPi4: -r359376 fails to boot (unless I use boot -v) where -r358966 booted fine before update References: <B501E3CD-A76E-4D9F-A7AA-70F2D2087BBC@yahoo.com> <147DDCEF-C081-4237-A81E-AEBCD71AB016@yahoo.com> <AB6A78AD-DB89-446E-B150-CA3AC8BE0B67@yahoo.com> In-Reply-To: <AB6A78AD-DB89-446E-B150-CA3AC8BE0B67@yahoo.com> --fxWP5blVh2munGe8b4EgxjW6L4QOfVsdy Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US W dniu 29.03.2020 o=C2=A004:48, Mark Millard via freebsd-arm pisze: > [Just correcting a persistent version number typo: > head -r359376 is correct, not -r359736 . Subject > corrected too.] > > On 2020-Mar-28, at 18:18, Mark Millard <marklmi atyahoo.com> wrote: > >> On 2020-Mar-28, at 17:14, Mark Millard <marklmi at yahoo.com> wrote: >> >>> 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: > Make that: -r358376 . > >>> 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.) >>> >> Booting the old kernel seems to consistently >> work (unload, load, boot sequence). >> >> boot -v of the new kernel can fail. >> >> Plain boot of the new kernel can on occasion >> boot. >> >> This makes for more comparable output >> difference checking . . . >> >> >> Dealing with pain boot 1st (then I'll >> show the boot -v comparison), I show >> just differences in the captured output >> . . . >> >> >> EFI boot manager: Cannot load any image >> 679248 bytes read in 91 ms (7.1 MiB/s) >> libfdt fdt_check_header(): FDT_ERR_BADMAGIC >> >> vs. >> >> EFI boot manager: Cannot load any image >> 679248 bytes read in 90 ms (7.2 MiB/s) >> libfdt fdt_check_header(): FDT_ERR_BADMAGIC >> >> >> Booting [/boot/kernel/kernel]... =20 >> >> vs. >> >> Booting [/boot/kernel/kernel] in 9 seconds...=20 >> >> Type '?' for a list of commands, 'help' for more detailed help. >> OK boot >> >> >> Extra lines on "it boots" case, after the first 2 >> "REGSITER DUMP"s, starting inside the 3rd >> >> sdhci_bcm1-slot0: Argument: 0x000001aa | Trn mode: 0x00000000 >> sdhci_bcm1-slot0: Present: 0x000f0000 | Host ctl: 0x00000001 >> sdhci_bcm1-slot0: Power: 0x0000000f | Blk gap: 0x00000000 >> sdhci_bcm1-slot0: Wake-up: 0x00000000 | Clock: 0x0000fa07 >> sdhci_bcm1-slot0: Timeout: 0x00000000 | Int stat: 0x00000000 >> sdhci_bcm1-slot0: Int enab: 0x01ff00bb | Sig enab: 0x01ff00bb >> sdhci_bcm1-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000 >> sdhci_bcm1-slot0: Caps: 0x00000000 | Caps2: 0x00000000 >> sdhci_bcm1-slot0: Max curr: 0x00000001 | ADMA err: 0x00000000 >> sdhci_bcm1-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 >> sdhci_bcm1-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= >> sdhci_bcm1-slot0: Got command interrupt 0x00030000, but there is no ac= tive command. >> sdhci_bcm1-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_bcm1-slot0: Sys addr: 0x00000000 | Version: 0x00009902 >> sdhci_bcm1-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 >> sdhci_bcm1-slot0: Argument: 0x000001aa | Trn mode: 0x00000000 >> sdhci_bcm1-slot0: Present: 0x000f0000 | Host ctl: 0x00000001 >> sdhci_bcm1-slot0: Power: 0x0000000f | Blk gap: 0x00000000 >> sdhci_bcm1-slot0: Wake-up: 0x00000000 | Clock: 0x0000fa07 >> sdhci_bcm1-slot0: Timeout: 0x00000000 | Int stat: 0x00000000 >> sdhci_bcm1-slot0: Int enab: 0x01ff00bb | Sig enab: 0x01ff00bb >> sdhci_bcm1-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000 >> sdhci_bcm1-slot0: Caps: 0x00000000 | Caps2: 0x00000000 >> sdhci_bcm1-slot0: Max curr: 0x00000001 | ADMA err: 0x00000000 >> sdhci_bcm1-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 >> sdhci_bcm1-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= >> sdhci_bcm1-slot0: Got command interrupt 0x00030000, but there is no ac= tive command. >> sdhci_bcm1-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_bcm1-slot0: Sys addr: 0x00000000 | Version: 0x00009902 >> sdhci_bcm1-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 >> >> >> Extra lines on the "it fails to boot" side: >> >> 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 >> >> >> After one "Root mount waiting for: CAM" >> that both have, the failing side has: >> >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 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 >> >> >> As for the "it boots" side of the comparison: >> >> 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 >> Setting hostuuid: a4f7fbeb-f668-11de-b280-ebb65474e619. >> Setting hostid: 0xcd8e9e25. >> Starting file system checks: >> /dev/label/RPi4root: FILE SYSTEM CLEAN; SKIPPING CHECKS >> /dev/label/RPi4root: clean, 19046293 free (498933 frags, 2318420 block= s, 1.8% fragmentation) >> >> (And so on.) >> >> >> >> By contrast, the failing boot -v >> comparison goes like (not much is >> different between the two boot -v >> instances) . . . >> >> >> The working one had a 3rd REGISTER DUMP >> before the mmc0 bus width notice that the >> failing one did not have: >> >> sdhci_bcm1-slot0: Got command interrupt 0x00030000, but there is no ac= tive command. >> sdhci_bcm1-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_bcm1-slot0: Sys addr: 0x00000000 | Version: 0x00009902 >> sdhci_bcm1-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 >> sdhci_bcm1-slot0: Argument: 0x000001aa | Trn mode: 0x00000000 >> sdhci_bcm1-slot0: Present: 0x000f0000 | Host ctl: 0x00000001 >> sdhci_bcm1-slot0: Power: 0x0000000f | Blk gap: 0x00000000 >> sdhci_bcm1-slot0: Wake-up: 0x00000000 | Clock: 0x0000fa07 >> sdhci_bcm1-slot0: Timeout: 0x00000000 | Int stat: 0x00000000 >> sdhci_bcm1-slot0: Int enab: 0x01ff00bb | Sig enab: 0x01ff00bb >> sdhci_bcm1-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000 >> sdhci_bcm1-slot0: Caps: 0x00000000 | Caps2: 0x00000000 >> sdhci_bcm1-slot0: Max curr: 0x00000001 | ADMA err: 0x00000000 >> sdhci_bcm1-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 >> sdhci_bcm1-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= >> >> where both then had: >> >> mmc0: setting bus width to 4 bits high speed timing >> >> >> The failing boot -v ended with: >> >> CPU 1: ARM Cortex-A72 r0p3 affinity: 1 >> CPU 2: ARM Cortex-A72 r0p3 affinity: 2 >> CPU 3: ARM Cortex-A72 r0p3 affinity: 3 >> regulator: shutting down unused regulators >> 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 >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 10 more seconds >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 9 more seconds >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 8 more seconds >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 7 more seconds >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 6 more seconds >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 5 more seconds >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 4 more seconds >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 3 more seconds >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 2 more seconds >> Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying fo= r 1 more second >> 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>=20 >> >> >> The working boot -v instead had for that last area of the >> above output: >> >> 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: a4f7fbeb-f668-11de-b280-ebb65474e619. >> Setting hostid: 0xcd8e9e25. >> Starting file system checks: >> /dev/label/RPi4root: FILE SYSTEM CLEAN; SKIPPING CHECKS >> /dev/label/RPi4root: clean, 19057570 free (498234 frags, 2319917 block= s, 1.8% fragmentation) >> >> (I omit the rest.) >> >> >> That is it for output differences for >> boot -v. >> >> >> I'll note that "shutdown -r now" does not reboot >> but just stops after the "Uptime:" message line. >> I do not expect that this is new. > > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" This is probably RPi4 specific only. I have just upgraded Pine64LTS to recent CURRENT and rebooted without issues. --=20 Marek Zarychta --fxWP5blVh2munGe8b4EgxjW6L4QOfVsdy-- --oFeBLMH5zyUY9QqSL9U6hqhgzKYZRP9Y4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAl6ASm4ACgkQdZ/s//1S jSz26Af+Ls9ueP2TCjen2O66oO5mmtFxe39cKHP1xgD1iFqCuo+Vsa6/kDYnaoT6 bYrUKf9Eq/5ZsoFQnrQQoLCxcjWbFFL4cbQbuFQm4xybA/AAxold75WcbASjCrIY Skqrr5JmQs1H+ERi7gy5ymLTkll4TjJiWvbHUMaXBNdE1Yh3LKYCCppHjCVCFAPY XdypdJjw+6dapzGSvuWskmfpn7a5GDD2P8tK51mm6EWszv1olAo3XVlLrmzX5q3Z v69Xh3x+1N7sfuTym1KQgypE+/vPXIQLKDRUkEaNT3b51vayitiYqVE07EO7kqWS eMniD9L4d4bz0mDw4CUtQJTp6HmLIg== =zWq2 -----END PGP SIGNATURE----- --oFeBLMH5zyUY9QqSL9U6hqhgzKYZRP9Y4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eff57f3d-097f-ce15-f919-61f1971e8eb0>