From nobody Sat Oct 1 19:30:33 2022 X-Original-To: freebsd-uboot@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 4Mfxyc2D3dz4dpsj; Sat, 1 Oct 2022 19:30:32 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mfxyb11mdz4QGX; Sat, 1 Oct 2022 19:30:30 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 291JUYH4098436 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 1 Oct 2022 12:30:34 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 291JUXEP098435; Sat, 1 Oct 2022 12:30:33 -0700 (PDT) (envelope-from fbsd) Date: Sat, 1 Oct 2022 12:30:33 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm , freebsd-uboot@freebsd.org Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <20221001193033.GA98348@www.zefox.net> References: <62A7FD9D-DFAD-46B2-8681-F6EF0E5AC0DE@yahoo.com> <8CB25EDF-704A-4F86-B0D4-40818291C161@yahoo.com> <20220928234341.GA77046@www.zefox.net> <20220929002131.GA77106@www.zefox.net> <197D3C46-063B-4C67-AB1A-A3A072521D7F@yahoo.com> <6AA65AE6-41F1-405F-A592-7D641EA4C9CF@yahoo.com> <20221001174724.GA98055@www.zefox.net> List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-uboot List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-uboot@freebsd.org X-BeenThere: freebsd-uboot@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Mfxyb11mdz4QGX X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-1.06 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.96)[-0.962]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org,freebsd-uboot@freebsd.org]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[zefox.net]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sat, Oct 01, 2022 at 11:32:52AM -0700, Mark Millard wrote: > On 2022-Oct-1, at 10:47, bob prohaska wrote: > > > Wrong email for the patch in question. Wrong patch used > as well? (Actually, the log output still has the high > volume debug(...) messagess, so you did not use the patch > from the email that you replied to.) That's possible.... > > The email with the patch is Friday's 12:58 PM email about > the patching involving 3 mdelay(...) calls. > At this stage that's possible too 8-( Right now sysutils/u-boot-rpi-arm64/files contains root@pelorus:/usr/ports/sysutils/u-boot-rpi-arm64/files # ls -l total 24 -rw------- 1 root wheel 964 Oct 1 09:39 patch-common_usb.c which contains 3 references to mdelay. -rw------- 1 root wheel 382 Sep 28 21:31 patch-common_usb__hub.c -rw------- 1 root wheel 362 Sep 28 21:31 patch-common_usb__storage.c -rw------- 1 root wheel 291 Sep 28 21:31 patch-include_configs_rpi.h -rw-r--r-- 1 root wheel 510 Jul 24 09:31 patch-lib_efi__loader_efi__console.c -rw-r--r-- 1 root wheel 169 Sep 30 18:57 rpi_arm64_fragment If the sizes/dates are right maybe I copied the wrong u-boot.bin to /boot/msdos. If they're wrong a batch send of preferred patches is probably the best way to put things right. > > In testing the patch thee seem to be more cases of u-boot getting > > stuck in a loop, not all of the identical. > > > > The first in the script file left the disk LED stuck on with > > error 22 prominent, the second left the disk LED stuck off, > > with error 110 repeating. > > > > The script file is at > > http://nemesis.zefox.com/~fbsd/ > > in file pelorus_console.txt5_concise_loop_fails > > > > As I understand the possible result of the intended > patch is it might avoid the "0 Storage Device(s) > found" problem but need not avoid the later -110 -22 > error code related problems. > > So if you no longer get "0 Storage Device(s) found" > problems, that is progress/good, independent of any > later issues. Otherwise the mdelay(...) changes are > probably a waste and would just be reverted. > Out of the last 24 boot attempts there have been 6 loops and no failures to find a boot device. The log file is at http://nemesis.zefox.com/~fbsd/pelorus_console.txt6_more_loops > It might not be handy to test lots of examples of > the "Storage Device(s) found" messages, independent > of what follows each non-zero one. But that is the > kind of thing needed to test the consequences of > the 3 mdelay(...) calls. It's one of the few things I'm marginally capable of 8-) Thanks for all your help! bob prohaska