From nobody Mon Mar 27 16:52:37 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 4Plf4x4c9Kz41mDV for ; Mon, 27 Mar 2023 16:52:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 4Plf4x47YZz4NZ7 for ; Mon, 27 Mar 2023 16:52:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x532.google.com with SMTP id h8so38865797ede.8 for ; Mon, 27 Mar 2023 09:52:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; t=1679935968; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oMMBzYqx3gvPnYIRILCCfsfuKXoVLQdb8hKwl52+w6E=; b=lcmM5ivIHqSL0Js09zjGNp98WF1p9c3i0DhTyhZtZGaypQe7L/mDOMd14OQb4RYGs0 0Il9B/KU1kTDReGPmLcFeTkiNPUvN5GG4X31Xunlx3kUFRhl6NS4ikXH6oieBi3QdNCq VEo3ACa7Y4pGRj9xeEsCI/G+DzDct1KsY2Lup4nmWfRtLAKZRqHmZ2RPUhUwQ8RJtaXs Nds7cznv6zgrFyAZy90YykhzzckRVRq6ZXfDXKey2KCf35MCGtWXoOFAhesG5A836Nk8 MTFmLvSfaObJr5SSkOMJzCyBViSn9kmMyrMVrWIflrrAsJ3+Qx1qPsNl3lfjUqUWafog 5YiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679935968; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oMMBzYqx3gvPnYIRILCCfsfuKXoVLQdb8hKwl52+w6E=; b=jblV4H6sZa2nr9kwTMign6duOpaYmEIQ9vdmA3uLXzO0ZCrTPsaPWk9Mh5guq160Kz 9lckn/C44tO+KAKBm4aawrMyFDJO1WBjVoEzem1ZESdRuMaJjbG0AhPCTDZ4LTLnoJaf AgMzhPY6tSLppcr8+4bPhG3LDM2XV0IvdxAYZt9WDyrYsICaNkEJNlj7LVSvBy4YF72L HqqInmHDtlAZ/EzBJeEUx1pxtd8dRAGD7su6vqoOEX6Gyp4vF7bPAQUBvRFMEl3sp8Zb Sbyn4gU5DOzN8qnVACo+PJA8NygHttihdYB67pECEQil5vLdY97sRIb+L7nSWaNT+HJv FxtA== X-Gm-Message-State: AAQBX9e10sU0XSJkd+H96mQT+IIm1asf7zDLbBh0WSOH1jl1kXaR6E4W gPFEMZPjoIU5bqUW5ASRennAl1iv5pBomaInMWtGvAoleLgxPD9uArc= X-Google-Smtp-Source: AKy350aLua4b90b9+P7plr6+zi3bUHqVTS7nDBcUnllSQ98AodIalTltDaqQJpz+wGpSqWjlQ9YHYYHbDD2/DaOsnxE= X-Received: by 2002:a17:906:fe49:b0:8b1:3298:c587 with SMTP id wz9-20020a170906fe4900b008b13298c587mr6614464ejb.2.1679935968425; Mon, 27 Mar 2023 09:52:48 -0700 (PDT) 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 References: <20230327164919.GA65182@www.zefox.net> In-Reply-To: <20230327164919.GA65182@www.zefox.net> From: Warner Losh Date: Mon, 27 Mar 2023 18:52:37 +0200 Message-ID: Subject: Re: Boot stops at loader after build/install cycle To: bob prohaska Cc: "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="000000000000a4d0b305f7e492a4" X-Rspamd-Queue-Id: 4Plf4x47YZz4NZ7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000a4d0b305f7e492a4 Content-Type: text/plain; charset="UTF-8" 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... Warner > Thanks for reading, > > bob prohaska > > > --000000000000a4d0b305f7e492a4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Mar 27, 2023, 6:49 PM bob prohaska <fbsd@www.zefox.net> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">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.=C2=A0

It seems to happen only on the first reboot, though
I'm not absolutely certain=C2=A0 since I haven't been
keeping notes.

Is this intentional behavior?


No.=C2=A0 Should e= ither always stop or never...

Warner=C2=A0
Thanks for reading,

bob prohaska


--000000000000a4d0b305f7e492a4--