From owner-freebsd-arm@freebsd.org Sun Mar 29 01:20:40 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4D0B326D2C2 for ; Sun, 29 Mar 2020 01:20:40 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic313-48.consmr.mail.gq1.yahoo.com (sonic313-48.consmr.mail.gq1.yahoo.com [98.137.65.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48qd7h6M2Nz4VyQ for ; Sun, 29 Mar 2020 01:20:32 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: N_6BpMEVRDvd.miR6A7lED5GPdAEx7ojsA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Sun, 29 Mar 2020 01:20:22 +0000 Received: by smtp417.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 3f90b1cd2a0dad96ef670e9fcf55ec8e; Sun, 29 Mar 2020 01:18:21 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: FYI: head -r358966 -> -r359736 and RPi4: -r359736 fails to boot (unless I use boot -v) where -r358966 booted fine before update Date: Sat, 28 Mar 2020 18:18:19 -0700 References: To: freebsd-arm In-Reply-To: Message-Id: <147DDCEF-C081-4237-A81E-AEBCD71AB016@yahoo.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 48qd7h6M2Nz4VyQ X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.48 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.988,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.992,0]; RCVD_COUNT_TWO(0.00)[2]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE_FREEMAIL(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; RCVD_IN_DNSWL_NONE(0.00)[111.65.137.98.list.dnswl.org : 127.0.5.0]; MV_CASE(0.50)[]; IP_SCORE(0.00)[ipnet: 98.137.64.0/21(0.82), asn: 36647(0.65), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2020 01:20:41 -0000 On 2020-Mar-28, at 17:14, Mark Millard 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. >=20 > So at head -r358966 I'd been able to both the > Rock64 and the RPi4 from the same media. >=20 > Now with head -r359736 in place instead: >=20 > A) The Rock64 boots via that media just fine. >=20 > B) The RPi4 fails to boot (nothing special > like "boot -v"). >=20 > C) The RPi4 with "boot -v" boots just fine. > (This makes identifying the issue non-obvious.) >=20 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 = active 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 = active 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 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: : [options] Mount using filesystem 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) 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 blocks, = 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 = active 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 for = 10 more seconds Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for = 9 more seconds Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for = 8 more seconds Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for = 7 more seconds Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for = 6 more seconds Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for = 5 more seconds Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for = 4 more seconds Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for = 3 more seconds Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for = 2 more seconds Mounting from ufs:/dev/label/RPi4root failed with error 2; retrying for = 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: : [options] Mount using filesystem 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) 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 blocks, = 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)