EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b

EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b

[Hans Schou]

Hi Ard

This message has start showing for 3 seconds when booting:
EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b

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.

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.

-- 

./hans

Re: EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b

[zhang]

Hi Hans Schou.

I just searched online for your situation and found a post describing a
very similar problem.

Here is the link to this post:
https://forums.opensuse.org/t/efi-stub-warning-failed-to-measure-data-for-event-1-0x800000000000000b/187812/30

One comment in the original post reads as follows:

"i was having the same issue, the fix i found was going into the BIOS and
turning on secure boot then in the key managent setting of secure boot
clicking the reset to setup mode option then turning secure boot off and
then save and exit, if this does not work try restore to default key
option."

I think you can try this method; it might help you.

The original poster suggested enabling the Secure Boot option, which is the
operation described in your email (step 2).

If your kernel version is 6.16.4 or higher, that problem should disappear.

-- 
the-essence-of-life

Re: EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b

[Hans Schou]

Hi Zhang

> If your kernel version is 6.16.4 or higher, that problem should
disappear.

That sounds like the right solution.

I have now build and tried 6.18.9 but that did not solve the problem. I
still got exactly the same message.

> I just searched online for your situation and found a post describing a
very similar problem.

Yes there are several work a rounds to this problem as I wrote in my first
post, like enabling secure boot. But I don't see these work a rounds as
solutions. The warning disappear but the problem is still there.

I got rid of the warning by removing 15 old kernels from /boot which I
didn't use. But if I for some strange reason needed to have 19 kernels
installed
(I have now reinstalled all old kernels to see if I could reproduce the
warning with 6.18.9 which I could)

./hans

Re: EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b

[Ard Biesheuvel]

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.

Re: EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b

[Hans Schou]

On Wed, 8 Apr 2026, Ard Biesheuvel wrote:

> This is a harmless warning from the TPM code in your BIOS.

Yes I guess so. The reason why I posted this message was that I saw a lot
of questions on the same topic in several forums. The T thought it was
time to report it.

Just for the record: I tried to so how many kernels I should have
installed for the message to appear:
7 kernels and you see it
6 kernels and there is no message seen

As a lot of distros only have 2 or 4 of the latest kernels installed most
people will not see it.

Thanks for looking into it and I will leave it with that.
Case closed.

-- 

./hans