From nobody Tue Aug 16 03:35:52 2022 X-Original-To: freebsd-current@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 4M6GyY0hzgz4ZBkJ for ; Tue, 16 Aug 2022 03:36:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 4M6GyX3Lydz3LW7 for ; Tue, 16 Aug 2022 03:36:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe29.google.com with SMTP id q190so9000160vsb.7 for ; Mon, 15 Aug 2022 20:36:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=n+oNGLO62xoBow10ODNwApg15ZmngD2IF7TnAB0HsUA=; b=PfwjW9G3gvjz8xwCo067TKzCex/rK9mm6nu37Ri9zgimaq40dhSCWrgrZgPsoqj2E7 1KQQWbhmqJAd08JWXAr37ogxFJGyKWlRFiKAivnHncGfBff477dq+VD360AXeOJookpZ vT6ci4pXwyEmV6VxqyljtOHPgXJPsRJk9QFfZ2txBa57sUqmJkZT+hi51/IO1Q4S3Xzv CRbaBmnwnmBDGSnEslVS1ZZ8oBjljEZVlwLdTzkL0WgUjx1XmXVeuwrvteT/pQY0ou3h ukfanOeQ9Lv5pFKylVu9EVJ3ESknmp570xrPU02BflVKj60U+paxKMfkpjespW5u5s+y DDEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=n+oNGLO62xoBow10ODNwApg15ZmngD2IF7TnAB0HsUA=; b=MjBPtKG5yK6ilu/iBMYiuSXP5TKhWC9pXPj7O8k1pmwBLO7Vr8htKq5dyIUiE/6PUY ROJx7AwgvPrpHtF+B5W9v1MlRa3SXOH2YD8pvZUxSPbze4ksrKdvxz5OQQVpqlFCBasn ACBK7WfcY30WGv/P/N5la/zI3YbSBaN7KA29a6ThW8PTC7yj4I//FTycovdvEDIowLtj jcym+7MFwAFi4cm3tnjFxWrmlAvQdaHbfDHyUKKmNtO48OxXLB8Id+DTVZjXgjqNY4KA 2szvqwffrz39XbWEwA37g4TvzvNyWHMcQINrH/WlIC7KzGWFU3F8Cxa+lSDBIEp00HyK sYTg== X-Gm-Message-State: ACgBeo00qomBP8ueUSFpfQcfQAv1Gylkr5kJLPiplIGPI4JHwbJRbKUa PXM4LGhlmpOm6I0efs3KGwNz7B3R7cbTJCa7cvMHN2elNnI= X-Google-Smtp-Source: AA6agR4KaEjgJLCg9cauwHeq7/qjr0V2Z6uqXYwBwJye2ASABcsJzU2+ElUKIL6nTTyk5mi2953fouHvrUfvKHOYv2s= X-Received: by 2002:a67:ac45:0:b0:388:a1ff:7e89 with SMTP id n5-20020a67ac45000000b00388a1ff7e89mr8039050vsh.42.1660620963635; Mon, 15 Aug 2022 20:36:03 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20220813.015426.809710797578801280.yasu@FreeBSD.org> <20220814.063440.1883565953618972371.yasu@FreeBSD.org> <20220816.120142.317069615425604393.yasu@FreeBSD.org> In-Reply-To: <20220816.120142.317069615425604393.yasu@FreeBSD.org> From: Warner Losh Date: Mon, 15 Aug 2022 21:35:52 -0600 Message-ID: Subject: Re: Updating EFI boot loader results in boot hangup To: Yasuhiro Kimura Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000a4f89805e6537251" X-Rspamd-Queue-Id: 4M6GyX3Lydz3LW7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=PfwjW9G3; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::e29) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::e29:from]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[bsdimp.com]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com] X-ThisMailContainsUnwantedMimeParts: N --000000000000a4f89805e6537251 Content-Type: text/plain; charset="UTF-8" On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > From: Yasuhiro Kimura > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST) > > > From: Yasuhiro Kimura > > Subject: Updating EFI boot loader results in boot hangup > > Date: Sat, 13 Aug 2022 01:54:26 +0900 (JST) > > > >> I made regular update of my 14-CURRENT amd64 system from > >> main-n257134-a69c0964625 to main-n257316-9d16275c65b. I also updated > >> EFI boot loader (/boot/efi/efi/freebsd/loader.efi) but it results in > >> boot hangup as following. > >> > >> > https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64-20220813-boot-hangup.png > >> > >> If I restore previous loader file (that is, loader.efi of > >> main-n257134-a69c0964625 and kernel of main-n257316-9d16275c65b), then > >> system boots successfully. > > > > I submitted the problem to FreeBSD Bugzilla. > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265825 > > > > Best Regards. > > d98de744050 is committed. So I tested it with following steps. > > 1. Check out the commit. > 2. cd /usr/src/stand > 3. make > 4. make install > 5. install -m 755 -p /boot/loader.efi /boot/efi/efi/freebsd > 6. shutdown -r now > > And system boots successfully. But while efi loader is workding a lot > of messages are displayed as following. > > > https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64.20220816.efi-loader-message.png Would you be able to share camcontrol devlist output? Privately if need be. And have any of these disks ever held ufs filesystems?? Warner > --- > Yasuhiro Kimura > > --000000000000a4f89805e6537251 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura <yasu@freebsd.org> wrote:
From: Yasuhiro Kimura <yasu@FreeBSD.org>=
Subject: Re: Updating EFI boot loader results in boot hangup
Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST)

> From: Yasuhiro Kimura <yasu@FreeBSD.org>
> Subject: Updating EFI boot loader results in boot hangup
> Date: Sat, 13 Aug 2022 01:54:26 +0900 (JST)
>
>> I made regular update of my 14-CURRENT amd64 system from
>> main-n257134-a69c0964625 to main-n257316-9d16275c65b. I also updat= ed
>> EFI boot loader (/boot/efi/efi/freebsd/loader.efi) but it results = in
>> boot hangup as following.
>>
>> https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64-20220813-boot-h= angup.png
>>
>> If I restore previous loader file (that is, loader.efi of
>> main-n257134-a69c0964625 and kernel of main-n257316-9d16275c65b), = then
>> system boots successfully.
>
> I submitted the problem to FreeBSD Bugzilla.
>
> https://bugs.freebsd.org/b= ugzilla/show_bug.cgi?id=3D265825
>
> Best Regards.

d98de744050 is committed. So I tested it with following steps.

1. Check out the commit.
2. cd /usr/src/stand
3. make
4. make install
5. install -m 755 -p /boot/loader.efi /boot/efi/efi/freebsd
6. shutdown -r now

And system boots successfully. But while efi loader is workding a lot
of messages are displayed as following.

= https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64.20220816.efi-load= er-message.png

Would you be able to share camcontrol devlist output? Private= ly if need be. And have any of these disks ever held ufs filesystems??

Warner=C2=A0


---
Yasuhiro Kimura

--000000000000a4f89805e6537251--