From nobody Sat Apr 09 22:26:48 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9B6951A980BE for ; Sat, 9 Apr 2022 22:27:03 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic309-21.consmr.mail.gq1.yahoo.com (sonic309-21.consmr.mail.gq1.yahoo.com [98.137.65.147]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KbV922zL3z4pX1 for ; Sat, 9 Apr 2022 22:27:02 +0000 (UTC) (envelope-from marklmi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1649543214; bh=oBxdQc1mM8OAIndJYps5dWnwSgBMeDYtKmyHIxQV714=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=trUCueeiPdPx0y1OJ8gQr7npTdXJ6wy+AF5V8HzTdrQBKTrwhF1oH/fZYRcapxcApzhAU3XShxRAX/brKWqBBuU5BX1QQ4VdiqJnm+FU4K8pbZTokVL7OB0kO0RUKe7TgJZ5/jEvbeNZgrLNSIE7CaF+VREJRZtiKfTHgF74UdHWb9RYSvUqzj6mqHShhJ24n6LEDMRmzj1WYGu8c6XIOerNGYJXFdgrAyTWIBUlU/rf6eL1BBTufbc7EXiUJw6HSSHQcIIJP1Pv51mWu98tiMOTyypjCcpte6oIWh3MDC5TRDMaYIkbqIrO2b5246cWbM7SzrZep287yr6yM52Klg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1649543214; bh=biHBEmM+N+z/W1+VHBy/bFhBxu9RHa1x7PhSJdSfbuB=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=V0jsyEO63ZU+thV16Bt/DMokb+anlLMuaj9Rh893qpvFKm1/z8yrMaK6R+UBnYOP+1WZVW+bvLwSpOTxxmg8CQQXbtnPzYQ45JrwpoLXNXDwMwUNKFYBENJktAWmu2mRjp35kew3Q9ivyi7Iwc9KNp6DZABXaVXNT73GAixptNOffgyyYc+9TXYJ3Arxt6kzcbEdAEmFB+0P8Ly6T9/rYqtBbVN7/0G89MIWeUyLdqqSqvTguQqLUZddWqOGeOq2KTG4r0sPAEyZ7ykPpNOp5W+OEGUHUIyU7nco1yaNotNb1RbbLvIKEcC9dxXfdZOMKjr74DGcAeNrxvX4zfRyHA== X-YMail-OSG: ts9q5XQVM1mNmwpx0jvr.9gFDUJrL65PJ3HqtPf_S9jDHyrE_f3ki1otl.fDI9l zOwz0qg1JbRbJvfVMC1Ma79CLQZS4_NcW3EyF9Bu_uvcqQKV8P.DFjqOMphO8vF2jjnxrEsUMbMy DgyQ3jVY2nwrYfY.yhYue6nr_pTnpvVdZ1Uz1VZykz8Di0Fp3lmRVslCxKwkEL3c3gLUcNLTyYHV EmyNfKnRlaaFgxOmR34IozgRq.JwwEsy3PVfD.E9_uCEm1ndXo0oCsIvxth5zU7Se7pvKLK29e8R Tj0hol4K6KRHKSuRHfhm9IXMWixaeHAqgoel854FM7GapuRWVOyJySrwSFj8vuWI5H3cTQqwCCmH GStlDLMHnX6.S8tak7ASzM6RTt0fKeo4MtRr2ZFTfkYcRS6ALwtXpClyzmd9_V0nKbZ0F2fl1sqR qA2Ak4JlMhUetXWfqmMPH48_T8g0lSMW.XdHq1K73Mp2u.hkuMnYAYQfqHkts6HUnqZYARHXeeL0 J6iXbI3IHoTRtWHAoB89GzCgDyxwb1nMhA4acFvC6DmN_ZplUFnVYPEwnG34SHKy0vDZIPsWQGBB WAVwgc81EjsXM4hmzHWA27e5f.c2pzxVv5J5zkLDDho6kx43Q10dvToGJdKLE8z13xEzDLTPlYdL 5wqTk9AuqY6KbOXu9ySJlbgCEtQeYC7_EkhuLY6DE34qsRSmqaUAbHFiTmPuvJLeflhnlo0u.s_B INlzaZxTcRQlVlOPHXXA4GE2yF4OCevFS3a6DK_H3GtaBLkcA6.mUnuRlYgA8fyavIu2zIWOaCno MV._aiL.sxjRkiFVG8ONoEe.9XpNk_9yx.N1RoBySe7KKwaOkRB57n2surDlmcZNwbfxhml0OisS YwoFu0mI055hTCBzj6PhLfkTWqK8a2WrLhvj4CABVpAsMXHP396U5X0RVhAqm7txbTMaVR0Wn5Yj aLQzahzbOByvwoaSN.mj2yAxbQRQcCm_yj42fyycst95VNPja.PvK9sSYtcyWzONMkoE4je.6.XF KfdaT_6gSUHKxMruSOcOfwJNoyfUfWiKIFGiXIYE4rkPtgGcZCIrFoCOiMBtX.IzVE021.kzRBGc V3d27R.U7XAuOsNUTOl9Atvc7VnhjzHnnZtSSPZI0_in0LnqoI0UdGvSet3uZm2k_B3naUJidJtZ B_S5SPF1rX3pT0.QJKvtJpt1R2k91DA5TwjDsK931LFpR6lsS6SK4ry6ICZltTIgEJXeLOn6.Zlv 1J3upIzCE9TSXmcX79kE4IRLuutJdirhHVuf8s2EqV6Vq6INpn.dj1cM09GSwmGp0IB2oaQ90cNn XvaauMtTVlQjiWd4NRpgFTuL9zxtunDOMRGO7CkSxCsZCrsmZO.ssY38JWKFPR9JvtvXDWOxgHBd CITv8mCAsB4BhavObaDynq_hQgvKt32uNdlpqZ9B0G9q9Yr5Vm.HQeJOuPkzZTd36bqQsQ.XIP_. fJIAYrynbF0U2oZjlkTCmxtXsXSxROD2OxxvbOh2vrmduICtRE401H9vHVokfSE3KRKC4hRYCk1n OPNpKEDn4MeY12ZBCTSFNdsVdsrjo.kk.L5pKm4xYFaYGA80RSaZ5GXiLNqVJVmntD61jNIE2fhk cLzo2Ki3PtJGSnq_3i2xilZx_ly.T_q3gGngC64tD1xF5BQkh0ev4ZPxUZUXyQPhTwvSqCqa._hR iEjATBGP0fI0G8SflMOAHxyqcV7f9FfknUwbD624zzJLYYadnEewVHQGwRnQ3a9MSVzqKyUy_Lsf ZKnbA_DUrxKmuQXBeA_WXHY.T5qbaQvjwXEURwv._KYrLBwNJmuV2XERnq9WXCxvq4CudbPgA6fu x3_Yp6tvFJ5BgrboxHEJo6Dx8S0eCB5rLXnFBPksnIwoCK1SPzh4eMhX4VaW_BFjDj222PSotgK_ pimM5mt9VmCXEYQ3Rtr0WYQoix6uY3mgEs85ct84R34ZWHxeHj8cpvubQtDdRw7F3DGUvdjaMILv b8LJ7IwdkNuE9.BKQXxk64AR6d.5arJ9yDhEU4tU.y4x8ZA34L3UG.bWQ1YQ_xCY6bL8WWsoiTet uNMNXOYHLNsaPHwt33O.Qg4eXPMqaNyFw0lI4MPw4QIe1uTVjR5sZuM_zfHpAjZxn4XAoxLTrZ6d oKT_S7iutkZ7RWKmeNTTt3UwZUiu9h5XJn5e9qwCbKzrX1oOOSXlDhzpkQ5ngbwXRc4uRdPuuYzz cWEPMp8XkNS4aW89vZ.zNkYwwHIwSWIeo96.En2t0LW7Rsk2lUTr09zaJ8c9rcCnbmZaexZfZDRZ nSnwXg6lQsTRJTkYgNtizifWU X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.gq1.yahoo.com with HTTP; Sat, 9 Apr 2022 22:26:54 +0000 Received: by hermes--canary-production-bf1-665cdb9985-6p9bt (VZM Hermes SMTP Server) with ESMTPA ID 6a4196d62d3695a01b37e8473f95370e; Sat, 09 Apr 2022 22:26:50 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: RPI4 panic on boot with -current From: Mark Millard In-Reply-To: <1B2DD49C-96AD-4586-B9A7-F6D8386D4DE0@yahoo.com> Date: Sat, 9 Apr 2022 15:26:48 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <63FAC16E-2C49-4A09-BDC8-ED6E74FAA3BB@yahoo.com> References: <20220409015321.GA52002@www.zefox.net> <20220409154433.GB55458@www.zefox.net> <1B2DD49C-96AD-4586-B9A7-F6D8386D4DE0@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Rspamd-Queue-Id: 4KbV922zL3z4pX1 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=trUCueei; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.65.147 as permitted sender) smtp.mailfrom=marklmi@yahoo.com X-Spamd-Result: default: False [-3.25 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-0.77)[-0.772]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.977]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.147:from]; MLMMJ_DEST(0.00)[freebsd-arm]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.147:from]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On 2022-Apr-9, at 13:59, Mark Millard wrote: > On 2022-Apr-9, at 08:44, bob prohaska wrote: >=20 >> On Fri, Apr 08, 2022 at 07:46:57PM -0700, Mark Millard wrote: >>> On 2022-Apr-8, at 18:53, bob prohaska wrote: >>>=20 >>>> Might this be related to "RPi4B's got a PMIC replacement,..." = reported 4/3 ? >>>=20 >>> No: See the later note about the RPi4B Revision. >>>=20 >>>> A Pi4 (mechanical disk only, no microsd) trying to boot a fresh = build of=20 >>>> -current reports: >>>>=20 >>>> Resetting system ...=20 >>>>=20 >>>> U-Boot 2020.10 (Mar 04 2021 - 04:32:31 +0000) >>>=20 >>> This is an old U-Boot compared to sysutils/u-boot-* . >>> There may well be good reasons for using it, for all >>> I know. >>>=20 >>=20 >> Only the most universal reasons: Inertia and ignorance 8-) >>=20 >> There are many versions of u-boot for rpi boards, some of=20 >> which are rather ambiguously named; u-boot-rpi-arm64 versus >> u-boot-rp4 is a good example. >=20 > u-boot-rpi-arm64 handles various RPi4B's, RPi3*'s, and, if I > remember right, RPi2B v1.2's. This is what snapshots and > BETA and PRERELEASE and RELEASE builds use these days. >=20 > The older ports are more specific, as I understand: >=20 > u-boot-rpi4 does not handle RPi3*'s or RPi2B v1.2's. > u-boot-rpi3 does not handle RPi4B's. >=20 > So the usable-contexts do overlap. Technically. there is no > unique answer to which to use. >=20 >> It appears the pkg-descr files >> have been updated since I last looked, but the descriptions >> overlap and it's not obvious how to choose among them. Man >> pages seem passe, is there some other guidance?=20 >>=20 >> Even if one knows which to select and build from ports the >> make install command doesn't really install; the admin still >> has to know what files to copy where. >=20 > With good reason for where: the msdosfs file system is not part > of FreeBSD's file systems (UFS or ZFS) and there is no standard > mount point for the msdosfs in FreeBSD's file system. >=20 > The admin may well be able to set up scripts that match how they > have things configured. >=20 >> Your instructions for=20 >> the task have been noted and saved, but even then it's very >> easy to make mistakes that are hard to recover from. >=20 > I suspect that you are referring to more than u-boot.bin above, > i.e., not just U-Boot. >=20 > Keeping a copy around of the last known-usable msdosfs content > before updating it is appropriate. The copy should be someplace > that can be used to replace any problematic update to the > msdosfs content. >=20 >> Does pkg handle u-boot and firmware updates more automatically? >=20 > No, with good reason for where: the msdosfs file system is not part > of FreeBSD's file systems (UFS or ZFS) and there is no standard > mount point for the msdosfs in FreeBSD's file system. >=20 > The admin may well be able to set up scripts that match how they > have things configured. >=20 >> Alternatively, is it feasible to update u-boot and firmware with >> an "installboot" target, either from the port directory or /usr/src? >=20 > No, with good reason for where: the msdosfs file system is not part > of FreeBSD's file systems (UFS or ZFS) and there is no standard > mount point for the msdosfs in FreeBSD's file system. >=20 > The admin may well be able to set up scripts that match how they > have things configured. >=20 I should have noted more fully: The issue is Small Board Computers in general, not just RPi*'s. RPi*'s are unusual in that U-Boot goes in an msdosfs instead of being dd'd someplace. And the RPi*'s firmware placement and handling is also atypical. Nothing even says that a msdosfs has to be mounted in FreeBSD at all. In fact, for a microsd card msdosfs used for RPi* firmware and u-boot.bin , but the EFI msdosfs being on a USB drive, along with a UFS or ZFS file system, there are two msdosfs around and used during booting, neither of which has to ever be mounted in FreeBSD at all in order for the system to boot and operate. (I use this EFI on "only the same media as UFS or ZFS" all the time. It allows me to use a microsd card to override any RPi* firmware or the like on that media that has UFS/ZFS, a microsd card that does not have the EFI content but has the other stuff. This can be handy for some forms of recovery from rpi* firmware/U-Boot/FreeBSD combinations that do not work well together.) And what if the devices connected overall have more than one msdosfs around that has RPi* firmware and/or u-boot.bin ? Which ones should be updated? Nothing requires that the snapshot/PRERELEASE/BETA/RC/RELEASE build images be used or that things outside FreeBSD file systems be organized the same as on those images. pkg and such can not presume that they are. The admin may well be able to set up scripts that match how they have things configured for the system. =3D=3D=3D Mark Millard marklmi at yahoo.com