From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Hans Schou" <chlor@schou.dk>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b
Date: Wed, 08 Apr 2026 13:50:11 +0200 [thread overview]
Message-ID: <85ad7864-6ea6-4d78-97aa-f67cbe4eb22d@app.fastmail.com> (raw)
In-Reply-To: <CAApBw345j80D3hvYzc47Wc9aDpr+HBJPQDpyeVZhvQ4b98a3QA@mail.gmail.com>
Hello Hans,
On Sat, 4 Apr 2026, at 12:54, Hans Schou wrote:
> Hi Ard
>
> This message has start showing for 3 seconds when booting:
> EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b
>
This is a harmless warning from the TPM code in your BIOS.
> Afterwards my Linux Mint boots up normally.
>
> Linux p52 6.8.0-107-generic #107-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 13
> 19:51:50 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
>
> GRUB 2.12
>
> This warning occurs only in several different events.
> It can be eliminated in different work arounds:
> 1. Having too many kernels installed. 19 is too many. 4 is few.
> Solution: Remove some old kernels.
> 2. Enable/Disable secure boot in BIOS (if posssible)
> 3. Having Linux/Windows dual boot. Work around: add
> "CONFIG_EFI_HANDOVER_PROTOCOL=N EFI_STUB=N" to
> GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.
>
> Only "1." is my own experience.
>
3. seems implausible to me: putting those strings on the command line has no effect, those are build options that must be taken into account while compiling the kernel.
> It seems like this situation happens as a combination of GRUB and the
> kernel.
> The kernel should not be able to see I have more than 4 kernel
> installed, as at the time of reporting the warning, one of my the
> kernels are already about to boot.
> So it could be GRUB which gives some extra parameters to the kernel
> when booting. How else could the kernel know there are "too many"
> kernels installed? In that case the bug is in GRUB and the kernel is
> just reporting it.
>
> By searching internet I found:
> * First seen year 2023 (kernel version not reported)
> * OS reported used: Mint, SuSE, Ubuntu, Ubuntu MATE, Kubuntu
>
> If it's due to GRUB, I apologize for the inconvenience.
You can just ignore this warning. I wouldn't recommend turning off secure boot just for this reason.
next parent reply other threads:[~2026-04-08 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAApBw345j80D3hvYzc47Wc9aDpr+HBJPQDpyeVZhvQ4b98a3QA@mail.gmail.com>
2026-04-08 11:50 ` Ard Biesheuvel [this message]
2026-04-09 16:42 ` Hans Schou
[not found] <76B4E7D1-5977-4E40-B68B-801306630B62@gmail.com>
2026-04-05 7:57 ` Hans Schou
2026-04-04 10:58 Hans Schou
2026-04-05 0:49 ` zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85ad7864-6ea6-4d78-97aa-f67cbe4eb22d@app.fastmail.com \
--to=ardb@kernel.org \
--cc=chlor@schou.dk \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®