Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Sep 2024 13:26:07 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Thomas Laus <lausts@acm.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: New console output at boot?
Message-ID:  <CANCZdfpvC0EtV0wdn2zF=z3HnyCn-zewLxSX50Cjxs4ESAsXQg@mail.gmail.com>
In-Reply-To: <CANCZdfrW3kqaFPAH1caDyLWdVXSoZ-rEn=Dv2KexwTJa1o%2B13A@mail.gmail.com>
References:  <CAN6yY1unczee8d4jkiok4KObGg%2BJkCShU_1WgpKbMPX2SWkX_g@mail.gmail.com> <CANCZdfqWm6ynaB4h2KwWOrvCxCe-j8iowuZoLdv2j_x3eXygeA@mail.gmail.com> <5ee4b852-f2a3-4c87-bcaa-7341e34f8bfe@acm.org> <CANCZdfrW3kqaFPAH1caDyLWdVXSoZ-rEn=Dv2KexwTJa1o%2B13A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000dab9a20622e27aba
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 24, 2024, 11:55=E2=80=AFAM Warner Losh <imp@bsdimp.com> wrote:

>
>
> On Tue, Sep 24, 2024, 11:47=E2=80=AFAM Thomas Laus <lausts@acm.org> wrote=
:
>
>> On 9/24/24 11:04, Warner Losh wrote:
>> > On Sun, Sep 22, 2024 at 6:21=E2=80=AFPM Kevin Oberman <rkoberman@gmail=
.com
>> > <mailto:rkoberman@gmail.com>> wrote:
>> >
>> >     Since an update to current a couple of weeks ago, I now see severa=
l
>> >     lines (6 or 7) early in the boot. I'm not sure whether it is from
>> >     one of the boots or the loader, but it comes out so quickly (and s=
o
>> >     briefly) but it vanishes on my display before I can read it. I'm
>> >     guessing that some part of the boot. I'm guessing it is a warning =
to
>> >     update one or more of the files.
>> >
>> >     I'm running main-n272093-705583b76f3f on an amd64 system with UEFI
>> >     boot of a UFS2 file system. So far, I've seen nothing in UPDATING
>> >     that references it.
>> >
>> >
>> > I'll have to look at UPDATING.
>> >
>> > tl;dr: It's telling you your loader.efi is too old and needs to be
>> > updated. Too old here is somewhat too strict (since
>> > it requires a version bump recently, not the actual commits that
>> > introduced the compat code that I'd like to remove).
>> > It's harmless, at the moment, but is warning of potential problems in
>> > the future,
>> >
>> I see this same issue when 'gptzfsboot' on a non UEFI system is booted
>> and before the startup menu is displayed and have for over a month.
>> I've updated my boot partition to:
>>
>> FreeBSD 15.0-CURRENT #13 1c6bb4c57
>>
>
> Impossible. Gptzfsboot is an earlier phase than the new message. It can't
> produce a mismatch. Only loader/loader.efi vs /boot/lua/* can cause this.
> And usually in this setup both are updated as a pair.
>

Thinking about it, I found a hole. If gptzfsboot picked the wrong BE this
could happen. And updating it might fix a bug that's causing it. Knowing
when your system last updated the gptzfsboot would be useful...

Warner

Ps sorry for the strong absolute tone...

Warner
>
>
> Tom
>>
>>
>>
>> --
>> Public Keys:
>> PGP KeyID =3D 0x5F22FDC1
>> GnuPG KeyID =3D 0x620836CF
>>
>>

--000000000000dab9a20622e27aba
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Tue, Sep 24, 2024, 11:55=E2=80=AFAM Warner Losh &lt=
;<a href=3D"mailto:imp@bsdimp.com">imp@bsdimp.com</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex"><div dir=3D"auto"><div><br><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Sep 24, 2024, 11=
:47=E2=80=AFAM Thomas Laus &lt;<a href=3D"mailto:lausts@acm.org" target=3D"=
_blank" rel=3D"noreferrer">lausts@acm.org</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">On 9/24/24 11:04, Warner Losh wrote:<br>
&gt; On Sun, Sep 22, 2024 at 6:21=E2=80=AFPM Kevin Oberman &lt;<a href=3D"m=
ailto:rkoberman@gmail.com" rel=3D"noreferrer noreferrer" target=3D"_blank">=
rkoberman@gmail.com</a> <br>
&gt; &lt;mailto:<a href=3D"mailto:rkoberman@gmail.com" rel=3D"noreferrer no=
referrer" target=3D"_blank">rkoberman@gmail.com</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Since an update to current a couple of weeks ago, I=
 now see several<br>
&gt;=C2=A0 =C2=A0 =C2=A0lines (6 or 7) early in the boot. I&#39;m not sure =
whether it is from<br>
&gt;=C2=A0 =C2=A0 =C2=A0one of the boots or the loader, but it comes out so=
 quickly (and so<br>
&gt;=C2=A0 =C2=A0 =C2=A0briefly) but it vanishes on my display before I can=
 read it. I&#39;m<br>
&gt;=C2=A0 =C2=A0 =C2=A0guessing that some part of the boot. I&#39;m guessi=
ng it is a warning to<br>
&gt;=C2=A0 =C2=A0 =C2=A0update one or more of the files.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0I&#39;m running main-n272093-705583b76f3f on an amd=
64 system with UEFI<br>
&gt;=C2=A0 =C2=A0 =C2=A0boot of a UFS2 file system. So far, I&#39;ve seen n=
othing in UPDATING<br>
&gt;=C2=A0 =C2=A0 =C2=A0that references it.<br>
&gt; <br>
&gt; <br>
&gt; I&#39;ll have to look at UPDATING.<br>
&gt; <br>
&gt; tl;dr: It&#39;s telling you your loader.efi is too old and needs to be=
 <br>
&gt; updated. Too old here is somewhat too strict (since<br>
&gt; it requires a version bump recently, not the actual commits that <br>
&gt; introduced the compat code that I&#39;d like to remove).<br>
&gt; It&#39;s harmless, at the moment, but is warning of potential problems=
 in <br>
&gt; the future,<br>
&gt;<br>
I see this same issue when &#39;gptzfsboot&#39; on a non UEFI system is boo=
ted <br>
and before the startup menu is displayed and have for over a month. <br>
I&#39;ve updated my boot partition to:<br>
<br>
FreeBSD 15.0-CURRENT #13 1c6bb4c57<br></blockquote></div></div><div dir=3D"=
auto"><br></div><div dir=3D"auto">Impossible. Gptzfsboot is an earlier phas=
e than the new message. It can&#39;t produce a mismatch. Only loader/loader=
.efi vs /boot/lua/* can cause this. And usually in this setup both are upda=
ted as a pair.</div></div></blockquote></div></div><div dir=3D"auto"><br></=
div><div dir=3D"auto">Thinking about it, I found a hole. If gptzfsboot pick=
ed the wrong BE this could happen. And updating it might fix a bug that&#39=
;s causing it. Knowing when your system last updated the gptzfsboot would b=
e useful...</div><div dir=3D"auto"><br></div><div dir=3D"auto">Warner</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Ps sorry for the strong absol=
ute tone...</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><div dir=
=3D"auto">Warner</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">
Tom<br>
<br>
<br>
<br>
-- <br>
Public Keys:<br>
PGP KeyID =3D 0x5F22FDC1<br>
GnuPG KeyID =3D 0x620836CF<br>
<br>
</blockquote></div></div></div>
</blockquote></div></div></div>

--000000000000dab9a20622e27aba--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpvC0EtV0wdn2zF=z3HnyCn-zewLxSX50Cjxs4ESAsXQg>