From nobody Tue Sep 24 17:55:40 2024 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 4XCnbJ07WJz5Y6RZ for ; Tue, 24 Sep 2024 17:55:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XCnbH3Y6Wz4cMk for ; Tue, 24 Sep 2024 17:55:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x635.google.com with SMTP id d9443c01a7336-206e614953aso57313065ad.1 for ; Tue, 24 Sep 2024 10:55:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1727200552; x=1727805352; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iKNv98xBmKC/5WIr8exx+56wGB0op3ZrBDp40Uf3B9Q=; b=digOfgn352HxXbQOQU7ZadQBmo72EsuG6DjwyYDcgenqXBT5aT+v9pwlg1vXZlWP+Z hmh8t1yyQfQ0G7PEQ1qyZ7SJcpLeS39nJPJdsF7emaoe9BzQbD25Nluo6bGOyNxeUqFy sNeHdtY86/Tsk8cRzQI8SA3kfRufPI6e+FEVDKIl+azJE6BHdkinxR5taWgJwVrX6ub1 bFwOAbsIuTtyFCsT+/ekDnsFWTe0JmhowqtxCYbpW+E/QEnZCA4dMISvffJj0vrnEzPs loCQy8HWNl0r0Zvn1hH017GrgTCS6QG1nF9Ji5A9JPK8hYBc7gCv2gZC0LV3HCqDqlo4 X9cg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727200552; x=1727805352; 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=iKNv98xBmKC/5WIr8exx+56wGB0op3ZrBDp40Uf3B9Q=; b=qRHJSLaqxVqjF4pdV2lH64Z/ywFjISQ9P0FysoMquw/8T8WaVN3H5F1E8z7dKuognx USv3p8yubvmhhpdaxuqChNdBpEvCAXqnjYPwoBYF+NGR520vSR8H2KUuR4ngVUvytEG4 /AoJ6n243dUa1+0Y/IASA/bxI4Bz6VKp8VGZ7G5dOxttg9MGRPL3oRYCSB6M0aNFlzuY 2TOJHYV99aU502CvN7vEARayCMWk2BIaBYo1nU/8gGlDUZtjORtDBCCQkZ1JzVPxWPJD JAsgMRUASa9J4Uw8ypyboHpZj59pI7BFkxngJkyM9V2sSBmaQqGJbAdVUYyFtJn38dEn eW+g== X-Gm-Message-State: AOJu0Yyj+hR+uJdIsBKRepqyM+I1XWNSnkcK52W/MwewN61d8Hkfbs9N jhXHa0ce8GKHH5NASoiWLIvQp5hOlb710EOb2b6ivWuTYuwWIlLwjEHNC33UKFLlP73/3vfZoBA qRVga5qyhku7ZtAd5nSr0+rKyebXHGDiPapx0/g== X-Google-Smtp-Source: AGHT+IFLzTkTpzjD+fRmLBH3FDuvGRDo52h4u8X4d8uNPhl7Xp8FpxRWpurOJUnm5zcwrGO8eAqeoxMS8uz1R1LeWdU= X-Received: by 2002:a17:90b:274e:b0:2d4:6ef:cb14 with SMTP id 98e67ed59e1d1-2dd7f6c1691mr20399150a91.28.1727200552491; Tue, 24 Sep 2024 10:55:52 -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: <5ee4b852-f2a3-4c87-bcaa-7341e34f8bfe@acm.org> In-Reply-To: <5ee4b852-f2a3-4c87-bcaa-7341e34f8bfe@acm.org> From: Warner Losh Date: Tue, 24 Sep 2024 11:55:40 -0600 Message-ID: Subject: Re: New console output at boot? To: Thomas Laus Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000634e570622e1378f" X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XCnbH3Y6Wz4cMk X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated --000000000000634e570622e1378f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Sep 24, 2024, 11:47=E2=80=AFAM Thomas Laus wrote: > On 9/24/24 11:04, Warner Losh wrote: > > On Sun, Sep 22, 2024 at 6:21=E2=80=AFPM Kevin Oberman > > wrote: > > > > Since an update to current a couple of weeks ago, I now see several > > 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 so > > 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 t= o > > 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. Warner Tom > > > > -- > Public Keys: > PGP KeyID =3D 0x5F22FDC1 > GnuPG KeyID =3D 0x620836CF > > --000000000000634e570622e1378f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Sep 24, 2024, 11:47=E2=80=AFAM Thomas Laus <= ;lausts@acm.org> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">On 9/24/24 11:04, Warner Losh wrote:
> On Sun, Sep 22, 2024 at 6:21=E2=80=AFPM Kevin Oberman <rkoberman@g= mail.com
> <mailto:rkoberman@gmail.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0Since an update to current a couple of weeks ago, I= now see several
>=C2=A0 =C2=A0 =C2=A0lines (6 or 7) early in the boot. I'm not sure = whether it is from
>=C2=A0 =C2=A0 =C2=A0one of the boots or the loader, but it comes out so= quickly (and so
>=C2=A0 =C2=A0 =C2=A0briefly) but it vanishes on my display before I can= read it. I'm
>=C2=A0 =C2=A0 =C2=A0guessing that some part of the boot. I'm guessi= ng it is a warning to
>=C2=A0 =C2=A0 =C2=A0update one or more of the files.
>
>=C2=A0 =C2=A0 =C2=A0I'm running main-n272093-705583b76f3f on an amd= 64 system with UEFI
>=C2=A0 =C2=A0 =C2=A0boot of a UFS2 file system. So far, I've seen n= othing in UPDATING
>=C2=A0 =C2=A0 =C2=A0that 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 boo= ted
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 phas= e 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 upda= ted as a pair.

Warner


Tom



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

--000000000000634e570622e1378f--