From nobody Tue Sep 24 19:26:07 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 4XCqbf6gwFz5YCHZ for ; Tue, 24 Sep 2024 19:26:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (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 4XCqbd5GZVz4qqG for ; Tue, 24 Sep 2024 19:26:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=19lCO5Su; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::102c) smtp.mailfrom=wlosh@bsdimp.com Received: by mail-pj1-x102c.google.com with SMTP id 98e67ed59e1d1-2da4e84c198so4156446a91.0 for ; Tue, 24 Sep 2024 12:26:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1727205979; x=1727810779; 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=YAl3i9wtVQez0sag4nsy2HUeRq18n5GkiMQWtQ2Tgqo=; b=19lCO5SubTPWcwnSws2Bv9yobz4tKT0Ou0xtSR6lzFiBJ6IsNzhy/OZI4VihDnMAk8 t1RDgD98Rx9lrX3rLYig0ZtKIYKovAVLBmLD2RPTjKkYlrsxzxqXwHa/KQS2As4PTKdW xUvYsIpjD64z0M6hp1j7GrwrxHjx2tYyruc606mqYGLYEKwKAqd9MdaIRAsWItsLRBBe IzmK4bX3IpRSnOp4Mqn7FIg7ok5qSdMd79+fxQv4/E6fth1Sih5I0/5IQU8w/pZvlBzE yNXZcdqXG+bK2hiJaWjGNjwxs12nLM3lJ9rL1J8AfwuWTKSPT77AKStwxj0iRiAi8Cua RTVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727205979; x=1727810779; 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=YAl3i9wtVQez0sag4nsy2HUeRq18n5GkiMQWtQ2Tgqo=; b=EClou4E+HQnTOlea5t25x8KZIlkCSXET4li+0PieqmSK1IO8oLtRPdaeo3YI9ZMc13 +FkgU6sKI0g6RS5hi7/+gtEikhSV60K3VRwhy35urwKBPcEmVcqgnVaMAKNmvk8Q5sNB reiBBN7vDxWJ7muj4B0KnDBp6OMHwwx6uWiKg8O9TuWoKmdkVz5DvY1heTx08mbctAcJ p4rp0qFX0U+yK8In9XxyC/C8VZkCBK3sEwDyMfPYiLVyHOknALP/FxzClUdWp7m7CI// wArqfvGqY3vdEVON5FG5iWrE/q1aVDgnWn4j6V5YsQ9KxifuyB1Haf/VIjbxfK2w1DVp 8Qtw== X-Gm-Message-State: AOJu0YzCRdk/DmIN08bEYWXeHpdymlOKLdXlOW0vtM9egyyRg1WcMHB3 VLxs4KgqS+GPdmpGud5ErNys/aiRrXt3gt/E+82clJkU21ygkUJ/ytr/jmX1aKomr/d4dKdPma3 awRw3255EmYcKoL2BiQ3lk+Iu4dFhY+iZm35vH6cWTnGO6Ac4 X-Google-Smtp-Source: AGHT+IEvYdiz4dgybtggAgq3Eb7fPVCHcDffRxcn6th4t4oUyCzN+dKOatj6WsbtMfC8mPlvL/xEpwu2znVAAQTblMo= X-Received: by 2002:a17:90b:50cf:b0:2da:da85:b705 with SMTP id 98e67ed59e1d1-2e06ae5e950mr280236a91.14.1727205979363; Tue, 24 Sep 2024 12:26:19 -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: From: Warner Losh Date: Tue, 24 Sep 2024 13:26:07 -0600 Message-ID: Subject: Re: New console output at boot? To: Thomas Laus Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000dab9a20622e27aba" X-Spamd-Result: default: False [-2.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::102c:from]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4XCqbd5GZVz4qqG X-Spamd-Bar: - --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 wrote: > > > 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 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


On Tue, Sep 24, 2024, 11:55=E2=80=AFAM Warner Losh <= ;imp@bsdimp.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">


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:
>
>=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.

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'= ;s causing it. Knowing when your system last updated the gptzfsboot would b= e useful...

Warner
=

Ps sorry for the strong absol= ute tone...

Warner


Tom



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

--000000000000dab9a20622e27aba--