public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: zhang <zhangweize9@gmail.com>
To: chlor@schou.dk
Cc: ardb@kernel.org, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b
Date: Sun, 5 Apr 2026 08:49:47 +0800	[thread overview]
Message-ID: <d5415782-362c-40d0-a7df-6533c0cb0a86@gmail.com> (raw)
In-Reply-To: <7648e713-ddb5-e42f-c715-73c097d196d8@schou.dk>

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

  reply	other threads:[~2026-04-05  0:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04 10:58 EFI stub: WARNING: Failed to measure data for event 1: 0x800000000000000b Hans Schou
2026-04-05  0:49 ` zhang [this message]
     [not found] <76B4E7D1-5977-4E40-B68B-801306630B62@gmail.com>
2026-04-05  7:57 ` Hans Schou
     [not found] <CAApBw345j80D3hvYzc47Wc9aDpr+HBJPQDpyeVZhvQ4b98a3QA@mail.gmail.com>
2026-04-08 11:50 ` Ard Biesheuvel
2026-04-09 16:42   ` Hans Schou

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=d5415782-362c-40d0-a7df-6533c0cb0a86@gmail.com \
    --to=zhangweize9@gmail.com \
    --cc=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