From nobody Mon Mar 27 17:44:07 2023 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 4PlgDN1Xt5z41qGk for ; Mon, 27 Mar 2023 17:44:20 +0000 (UTC) (envelope-from sr@genyosha.net) Received: from ns5.genyosha.net (ns5.genyosha.net [50.53.250.76]) (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 "float.home.genyosha.net", Issuer "float.home.genyosha.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PlgDM1s4Rz4TYf for ; Mon, 27 Mar 2023 17:44:19 +0000 (UTC) (envelope-from sr@genyosha.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of sr@genyosha.net designates 50.53.250.76 as permitted sender) smtp.mailfrom=sr@genyosha.net; dmarc=none Received: from dragon.home.genyosha.net (ops.genyosha.net [50.53.250.77]) by ns5.genyosha.net (8.17.1/8.16.1) with ESMTPS id 32RHiCBY001058 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Mar 2023 10:44:12 -0700 (PDT) (envelope-from sr@genyosha.net) Received: from dragon.home.genyosha.net (localhost [127.0.0.1]) by dragon.home.genyosha.net (8.14.7/8.14.7) with ESMTP id 32RHi7IH014381; Mon, 27 Mar 2023 10:44:07 -0700 Received: (from sr@localhost) by dragon.home.genyosha.net (8.14.7/8.14.7/Submit) id 32RHi7Uk014380; Mon, 27 Mar 2023 10:44:07 -0700 Date: Mon, 27 Mar 2023 10:44:07 -0700 From: Steve Rikli To: bob prohaska Cc: "freebsd-arm@freebsd.org" Subject: Re: Boot stops at loader after build/install cycle Message-ID: References: <20230327164919.GA65182@www.zefox.net> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Greylist: inspected by milter-greylist-4.6.4 (ns5.genyosha.net [50.53.250.76]); Mon, 27 Mar 2023 10:44:12 -0700 (PDT) for IP:'50.53.250.77' DOMAIN:'ops.genyosha.net' HELO:'dragon.home.genyosha.net' FROM:'sr@genyosha.net' RCPT:'' X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (ns5.genyosha.net [50.53.250.76]); Mon, 27 Mar 2023 10:44:12 -0700 (PDT) X-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.997]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; ASN(0.00)[asn:20055, ipnet:50.53.0.0/16, country:US]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[genyosha.net]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4PlgDM1s4Rz4TYf X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Mon, Mar 27, 2023 at 06:52:37PM +0200, Warner Losh wrote: > On Mon, Mar 27, 2023, 6:49 PM bob prohaska wrote: > > > For some time (months, I think) a Pi4 running -current > > has been stopping at the loader prompt on first reboot > > following a buildworld/buildkernel/installeverything > > cycle. The system uses a USB mechanical disk, no microSD > > and has never had trouble finding the disk. > > > > It seems to happen only on the first reboot, though > > I'm not absolutely certain since I haven't been > > keeping notes. > > > > Is this intentional behavior? > > No. Should either always stop or never... Shot in the dark: Bob, are you perhaps using serial console? My rpi4b had behavior similar to what you described for a while after I first got it; it was mostly pilot error: I am using serial console and had neglected to setup /boot.config with the proper serial parameters (e.g. "-Dh -S115200"). I think what was happening was a bit of leftover characters from my serial console server was getting interpretted by loader, so it stopped. I could always boot successfully from there, and a subsequent reboot from the serial console consistently "just worked" also, presumably because any stray characters and keystrokes on the line had cleared. The clue for me was occasionally seeing a little ascii junk around the login: prompt on console -- I typically don't see that. Once I setup /boot.config the loader didn't get interrupted. This is all with FreeBSD 13.1 from official arm64-aarch64-RPI image, fwiw, upgraded from src buildworld ever since. Cheers, sr.