From nobody Sun Aug 14 19:57:05 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 4M5Sqf0jmlz4Z2r9 for ; Sun, 14 Aug 2022 19:57:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (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 4M5Sqd2pR0z3V7f for ; Sun, 14 Aug 2022 19:57:17 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x933.google.com with SMTP id 5so2224787uay.5 for ; Sun, 14 Aug 2022 12:57:17 -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=0HWI2hp9h+SI1P4zL43ImzK1/E+eKMJbSd1aqXOxYeY=; b=Rjcbb9QQGOKP/SdU74fybNH/2PXUi/N52Gg69j0eZbj+uoofX3WG7iFudRkzFhZAzc b0nP246S3KB/zDkxidFyHZNQETZEtd0XJTXoLGXe7TD2YV5nmF0l3BSAFITfEj2apimL 3DqXQ3frA0vjxPrG1hbAB/fgmDVy6hgFqVLzA6r9j7I94qn9iJH0fbJmmn8e9y4xf1/I phG9NEwHLUMg4Nh/P7iwK7pF3S39me3guj4O4Q+EtkalO9lWgisELVaI7LHb7/94VqoH PCVN095zKCXIqOXksyq6kWA2RLYZE6uLAa8HGX4KRYq+PiorUpdxc33Jqj2elnk4RiL9 SYWQ== 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=0HWI2hp9h+SI1P4zL43ImzK1/E+eKMJbSd1aqXOxYeY=; b=DW3JT3fGiXM99csOVBIw6SOrxx263+sWyPfkI9sZ3T7SmqgRUOo+zjUoZREWPvljzG p/d6Q90Zaf4GnoMD8CseTVH8dJeZ1Bpi+LEBTdo8RsjXiXmOyD7I+iJQbTFAR2q6jN29 UM4xdXv7fixapRyOEwcYHBe8ITVCfyJxk3aN4IgkXMejCiQJCj7I8w3wONq76dYbOEVo Ph3vIO9CEw16qTXuJvo/dqCJa/vaW7OB4r42x7w2CQpS+6vCcBvosFuonkjPv9CABEB/ VJi7McyWw42zXSVLiskMMTihYqcBBOGi4s5+4q7bHzJM98aoawii5k9vPaz5IqOVzEHg iIUQ== X-Gm-Message-State: ACgBeo0Z6wybjgBhjvGMA00EcmFBcA8rCgvUewbEXJp+ebPOE9ydJsn9 sWTGIB2KwQz4JHxQXkTqTu1SLZXts6ZBhTNrT3bhvg== X-Google-Smtp-Source: AA6agR6+dki/wYMP06q5eyagyYtzmFzkmu3G00xWxeIK2cif8qVUo/qDMDbNeZjI/XieUurdHbRh3lMDZec3nzzLmvQ= X-Received: by 2002:a9f:2067:0:b0:387:984d:4a8e with SMTP id 94-20020a9f2067000000b00387984d4a8emr5176562uam.60.1660507036564; Sun, 14 Aug 2022 12:57:16 -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: <20220814.095721.849461222067829352.yasu@FreeBSD.org> <20220814.110850.1703361053728529792.yasu@FreeBSD.org> <45007308-136a-8938-33d0-bb2509ee6ae7@FreeBSD.org> <20220814192609.wyfcogl3dwzteuva@colony.nomadlogic.org> In-Reply-To: <20220814192609.wyfcogl3dwzteuva@colony.nomadlogic.org> From: Warner Losh Date: Sun, 14 Aug 2022 13:57:05 -0600 Message-ID: Subject: Re: Updating EFI boot loader results in boot hangup To: Pete Wright Cc: Stefan Esser , FreeBSD Current , Yasuhiro Kimura , Oleg Lelchuk Content-Type: multipart/alternative; boundary="0000000000000fd23405e638ec97" X-Rspamd-Queue-Id: 4M5Sqd2pR0z3V7f X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=Rjcbb9QQ; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::933) 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]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::933:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; R_SPF_NA(0.00)[no SPF record]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_FIVE(0.00)[5]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEMAIL_CC(0.00)[freebsd.org,gmail.com] X-ThisMailContainsUnwantedMimeParts: N --0000000000000fd23405e638ec97 Content-Type: text/plain; charset="UTF-8" On Sun, Aug 14, 2022 at 1:26 PM Pete Wright wrote: > On Sun, Aug 14, 2022 at 10:26:32AM +0200, Stefan Esser wrote: > > Am 14.08.22 um 04:20 schrieb Oleg Lelchuk: > > > Yes, Yasuhiro and I have the same error. > > > > Just a "me too", also on ZFS, on a Ryzen 3 based system. > > > > Booting the latest USB snapshot image worked, but not when I copy > > the whole of /boot from that USB stick to my ZFS boot partition. > > > > The system is usable if I boot from USB and manually mount the ZFS > > file systems over the USB boot image. > > > > adding my voice to the chorus here of "me too". ryzen5/uefi/zfs setup. > > has anyone else who has been impacted by this been able to recover? i > can boot into a memstick image, and access my uefi shell via the bios - > but i've never had to hack on btx like this before. > > any links or pointers would be appreciated! > I think I broke it with my latest updates. I don't have a good ZFS testing setup so I'm spending a little time enhancing the bootable image generator to have one that I can easily test boot with qemu. Warner --0000000000000fd23405e638ec97 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Aug 14, 2022 at 1:26 PM Pete = Wright <pete@nomadlogic.org&g= t; wrote:
On Sun= , Aug 14, 2022 at 10:26:32AM +0200, Stefan Esser wrote:
> Am 14.08.22 um 04:20 schrieb Oleg Lelchuk:
> > Yes, Yasuhiro and I have the same error.
>
> Just a "me too", also on ZFS, on a Ryzen 3 based system.
>
> Booting the latest USB snapshot image worked, but not when I copy
> the whole of /boot from that USB stick to my ZFS boot partition.
>
> The system is usable if I boot from USB and manually mount the ZFS
> file systems over the USB boot image.
>

adding my voice to the chorus here of "me too". ryzen5/uefi/zfs s= etup.

has anyone else who has been impacted by this been able to recover?=C2=A0 i=
can boot into a memstick image, and access my uefi shell via the bios -
but i've never had to hack on btx like this before.

any links or pointers would be appreciated!

=
I think I broke it with my latest updates. I don't have a good ZFS= testing setup
so I'm spending a little time enhancing the bo= otable image generator to have
one that I can easily test boot wi= th qemu.

Warner=C2=A0
--0000000000000fd23405e638ec97--