Date: Sun, 14 Aug 2022 13:57:05 -0600 From: Warner Losh <imp@bsdimp.com> To: Pete Wright <pete@nomadlogic.org> Cc: Stefan Esser <se@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, Yasuhiro Kimura <yasu@freebsd.org>, Oleg Lelchuk <oleglelchuk@gmail.com> Subject: Re: Updating EFI boot loader results in boot hangup Message-ID: <CANCZdfqgQ9ufhaBZ-FRjOAnFQtGJVtVoO4%2BJYgCU3eH_QExDqg@mail.gmail.com> In-Reply-To: <20220814192609.wyfcogl3dwzteuva@colony.nomadlogic.org> References: <20220814.095721.849461222067829352.yasu@FreeBSD.org> <CA%2BGqWgsMYEp4goeLBO4%2BufDU_ap5Opmf4udL_WSd-NZU1Q3dog@mail.gmail.com> <CANCZdfp4Har%2BrLV5kg94EWO_Uc767K7ga9AKLTznvqoC2JvQXw@mail.gmail.com> <20220814.110850.1703361053728529792.yasu@FreeBSD.org> <CA%2BGqWguOkHegLmijD2BAYhj7t9qCVY%2BmYNLN1_tJGp%2Bi=mNn6g@mail.gmail.com> <45007308-136a-8938-33d0-bb2509ee6ae7@FreeBSD.org> <20220814192609.wyfcogl3dwzteuva@colony.nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000000fd23405e638ec97 Content-Type: text/plain; charset="UTF-8" On Sun, Aug 14, 2022 at 1:26 PM Pete Wright <pete@nomadlogic.org> 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 <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Sun, Aug 14, 2022 at 1:26 PM Pete = Wright <<a href=3D"mailto:pete@nomadlogic.org">pete@nomadlogic.org</a>&g= t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p= x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sun= , Aug 14, 2022 at 10:26:32AM +0200, Stefan Esser wrote:<br> > Am 14.08.22 um 04:20 schrieb Oleg Lelchuk:<br> > > Yes, Yasuhiro and I have the same error.<br> > <br> > Just a "me too", also on ZFS, on a Ryzen 3 based system.<br> > <br> > Booting the latest USB snapshot image worked, but not when I copy<br> > the whole of /boot from that USB stick to my ZFS boot partition.<br> > <br> > The system is usable if I boot from USB and manually mount the ZFS<br> > file systems over the USB boot image.<br> ><br> <br> adding my voice to the chorus here of "me too". ryzen5/uefi/zfs s= etup.<br> <br> has anyone else who has been impacted by this been able to recover?=C2=A0 i= <br> can boot into a memstick image, and access my uefi shell via the bios -<br> but i've never had to hack on btx like this before.<br> <br> any links or pointers would be appreciated!<br></blockquote><div><br></div>= <div>I think I broke it with my latest updates. I don't have a good ZFS= testing setup</div><div>so I'm spending a little time enhancing the bo= otable image generator to have</div><div>one that I can easily test boot wi= th qemu.</div><div><br></div><div>Warner=C2=A0</div></div></div> --0000000000000fd23405e638ec97--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqgQ9ufhaBZ-FRjOAnFQtGJVtVoO4%2BJYgCU3eH_QExDqg>