From nobody Sun Oct 2 20:46:36 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 4Mgbc167Jpz4d2vT for ; Sun, 2 Oct 2022 20:46:41 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mgbc10nppz3bNc for ; Sun, 2 Oct 2022 20:46:41 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-ed1-x533.google.com with SMTP id y8so12148325edc.10 for ; Sun, 02 Oct 2022 13:46:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20210112; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date; bh=d4xEMqtF+jzQG0Go0mJX8YlFBN146xaTM26gRsgPWzw=; b=HSf/D2B1aBFBm3qkZwe3v3R+KPKztETCebrBnSMM0Lz7oBgHdciNNwc/JDpwfXG19g r7UVcbeFirzSlQNCei1gKqCQu93YmbV9AVf+WgqI5Onj1bM+yDoP2cXgipiYvuKyXIGJ xCLcY/edicHxEYuvjD51JZ3mtrdcVnyP/ZbFxwY4gQU9NlOQB13DtKdVCtOau+BOv273 Jnm33Q9ktSU6iKaJIIeAMNx2WVKEX6Kv4rudt9wrkUSu9Ov4JOO04UGxrR0iDPPwn9q6 4lzr36uBWZDopQfemNXaZ1Xxb/pwQm2HltCcylmNLyunVzUrkpX7RnJu0eFc+MxgG/YO cpLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date; bh=d4xEMqtF+jzQG0Go0mJX8YlFBN146xaTM26gRsgPWzw=; b=cwNXQ2PFApWmwaP9HoJ2Ci17KpL+Ds6/Ly5V6nIIsfCvJKaH/+nkN1CDWo4qrG3/Uz gbkZps8aMHT41ccu19j1HEfPAzng3GqG2yyxhkirQI0RRuP4ESc2jsIPgtDNQsyDTgn4 W49Lb4THVEFzRkL0Y56SG2yu1SOKzGIWTE3bjz6Tf8gmAUpzqHfQVtO1q7FZLGP++rLI ml8fdGzDhppCsM65Ved+rzA1inT8qXxjfvqXG3GXFB2HCETiomiYiAyxlJDgzWc+1r+o J/r3+2IMLLHjfPpYR3Pvrnml0MmnvPB6Ti8PKaLoL/8daFUwR8ODAdk7VdWXiJJab9y1 EH7Q== X-Gm-Message-State: ACrzQf1G0v4O04OYr8bv//ZNNM7rgMovAH6d9xFyIARKycmb7X/WfXs9 5ANhq5vxGz5YbL0kX7gcvOA= X-Google-Smtp-Source: AMsMyM5AzKwN8ZNVzczEozttLSxOX920ruxuejx8K665JZ/o5KE4B22Z+VTNv3W0zgRp5hkx0Rzb9A== X-Received: by 2002:aa7:d392:0:b0:458:800a:c47 with SMTP id x18-20020aa7d392000000b00458800a0c47mr10880493edq.5.1664743599721; Sun, 02 Oct 2022 13:46:39 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-061-084.46.114.pool.telefonica.de. [46.114.61.84]) by smtp.googlemail.com with ESMTPSA id u15-20020a17090657cf00b007867dcd3f15sm4417979ejr.104.2022.10.02.13.46.38 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Oct 2022 13:46:39 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 16.0 \(3696.120.41.1.1\)) Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Date: Sun, 2 Oct 2022 22:46:36 +0200 References: <20220929002131.GA77106@www.zefox.net> <197D3C46-063B-4C67-AB1A-A3A072521D7F@yahoo.com> <6AA65AE6-41F1-405F-A592-7D641EA4C9CF@yahoo.com> <20221001174724.GA98055@www.zefox.net> <20221001193033.GA98348@www.zefox.net> <46226720-D867-4AD3-9559-A4365FAC28C4@yahoo.com> <6DB88FC9-629C-43E6-9673-32640FC547F7@yahoo.com> <20221002182049.GA2255@www.zefox.net> <5FFDAA6A-AD8C-4E40-A2EB-4082E5086679@googlemail.com> <38DFEB91-AC60-4FD1-8088-95B0A06C5E5D@yahoo.com> To: Mark Millard , freebsd-arm@freebsd.org, bob prohaska In-Reply-To: Message-Id: <64C1085D-D3F8-45A3-80FB-4B88F81E480E@googlemail.com> X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Rspamd-Queue-Id: 4Mgbc10nppz3bNc X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=googlemail.com header.s=20210112 header.b="HSf/D2B1"; dmarc=pass (policy=quarantine) header.from=googlemail.com; spf=pass (mx1.freebsd.org: domain of maciphone2@googlemail.com designates 2a00:1450:4864:20::533 as permitted sender) smtp.mailfrom=maciphone2@googlemail.com X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.986]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20210112]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::533:from]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[googlemail.com:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com,freebsd.org,www.zefox.net]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org] X-ThisMailContainsUnwantedMimeParts: N > Am 02.10.2022 um 22:18 schrieb Klaus K=C3=BCchemann = : >=20 >=20 >=20 >> Am 02.10.2022 um 21:58 schrieb Mark Millard : >>=20 >> On 2022-Oct-2, at 12:35, Klaus K=C3=BCchemann = wrote: >>=20 >>> Am 02.10.2022 um 20:20 schrieb bob prohaska : >>>>=20 >>>> On Sat, Oct 01, 2022 at 02:21:42PM -0700, Mark Millard wrote: >>>>>=20 >>>>> http://nemesis.zefox.com/~fbsd/pelorus_console.txt7_orig_fragment >>>>>=20 >>>>> still shows all the debug output. It did not >>>>> avoid the timing changes. >>>>>=20 >>>>> You might need to not use either of: >>>>>=20 >>>>> patch-common_usb__hub.c >>>>> patch-common_usb__storage.c >>>>>=20 >>>>> and to disable the LOG_DEBUG and DEBUG lines in: >>>>>=20 >>>>> patch-common_usb.c >>>>>=20 >>>>> via turning them into comments by adding // as >>>>> indicated below: >>>>>=20 >>>>> +//#define LOG_DEBUG >>>>> +//#define DEBUG >>>>>=20 >>>>=20 >>>> I think the changes were successful, u-boot compiles and >>>> runs. There's no extra output, and unfortunately only one=20 >>>> successful reboot so far. Bus scanning seems quite slow. >>>> Storage devices are rarely found on reset, but usb reset >>>> does sometimes work. Run bootcmd_usb0 paused for minutes >>>> at Device 0: and paused again after reporting ..current device. >>>> No echo from the console, ctrl-C did nothing.=20 >>>>=20 >>>> The attempt sequence was >>>> SRBSPRMRPRRPUPPRRUPUCUUC >>>> where=20 >>>> S is shutdown -r >>>> R is reset of u-boot >>>> U is usb reset >>>> P is powercycle >>>> M is stop at mountroot >>>> C is run bootcmd_usb0 >>>>=20 >>>> The console log is at >>>> http://nemesis.zefox.com/~fbsd/pelorus_console.txt8_no_debug >>>>=20 >>>> It now appears that the run bootcmd_usb0 rather reliably gets >>>> stuck, with the disk LED on steadily (no activity). Maybe in >>>> one of the loops seen earlier?=20 >>>>=20 >>>> Thanks again for all your help! >>>>=20 >>>> bob prohaska >>>>=20 >>>=20 >>>=20 >>> So if you now reapply the #define DEBUG patches(while keeping the = mdelay-patch) and the reboot issues definitely went away >>> we have a typical so called Heisenbug, hopefully more or less now a = fixed issue. >>=20 >> No. Bob has more than one problem: more problems observed >> after "1 Storage Device(s) found". The DEBUG/mdelay >> combination only seemed to cause the "1 Storage Device(s) >> found" to be at least more reliable, not later stages. >>=20 >> It is not obvious if earlier activity contributes or not >> to the problems observed after "1 Storage Device(s) found". >>=20 >> So far nothing has gotten near having things just work for >> booting without manual intervention, multiple retries >> being involved sometimes. >>=20 >>> Well, USB-boot problems on earlier Pi models( afaik all except the = 4) are commonly known, from defective HW to power cycle issues we will = find a lot of discussions on the WWW and we will see that even the = debug-message =E2=80=9Eis your USB cable bad?=E2=80=9C did fix issues = in some cases. Others applied RNG devices or external clock or even = plugging a mouse fixed it( to change usb enumeration). >>>=20 >>> I think with the working u-boot.bin after 1500 successful reboots = you can be sure it=E2=80=99s working =E2=80=A6. >>> just kidding=E2=80=A6 :-) >>>=20 >>=20 >>=20 >> =3D=3D=3D >> Mark Millard >> marklmi at yahoo.com >=20 > hard to read and remember every log but I thought Bob wrote about = aprox. 30 successful reboots after the mdelay patch, > while of course that could be coincidence, who really knows what = happens in this untrackable inconsistent behavior of the usb-boot?! >=20 >> Am 02.10.2022 um 21:48 schrieb Mark Millard : >>=20 >> (RaspiOS and Ubuntu do not use U-Boot last I knew. So >> they do not make for good comparisons for the purpose >> as far as I know.) >=20 > RaspiOS doesn=E2=80=99t , Ubuntu(and others) use u-boot since years = =E2=80=A6 > while possible Ubuntu(or others) have own u-boot patches , > from guessing it seems more probable that they also will sometimes = hang after (re)boot. >=20 > If I would want to keep such a device as an online server, like Bob = does, for whatever reason I would=20 > Implement something like an =E2=80=9EIPMI=E2=80=9C or simpler said: > An immediate console remote access after being warned by a script that = the machine is offline. > But I would remove it from cluster if there are known Hardware = problems.=20 >=20 >=20 > Regards >=20 > Klaus >=20 >=20 =E2=80=A6 but of course, Mark, that is correct : overwriting parts of the msdos-partition by linux ones could be the last = resort to save something=E2=80=A6 but if linux had patched inside u-boot, as you did it for Bob, I would = see other problems coming=E2=80=A6 Regards Klaus