From: Clayton Craft <clayton@craftyguy.net>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-efi@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
regressions@lists.linux.dev
Subject: Re: x86_64 32-bit EFI mixed mode boot broken
Date: Thu, 21 Mar 2024 17:06:41 -0700 [thread overview]
Message-ID: <20240321170641.GK8211@craftyguy.net> (raw)
In-Reply-To: <CAMj1kXGzH4TiwvSF3bZsJpuuWf04Ri_852fUMTdH8pLRaH3+Yg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
On Thu, 21 Mar 2024 23:48:09 +0100 Ard Biesheuvel <ardb@kernel.org> wrote:
> > v6.8 fails for me, and presumably so does everything back to v6.2. v6.1 is able
> > to boot OK on these platforms with mixed mode, and it looks like there are a lot
> > of changes from 6.1..6.2 for EFI/mixed mode booting.
>
> v6.1 just received some EFI related backports, so please check the
> latest v6.1.y as well.
I just gave v6.1.82 a try, and it fails to boot for me. That seems to be a
regression from the 6.1.0 that I tested previously.
> I usually test on 32-bit OVMF built with LOAD_X64_ON_IA32_ENABLE,
> which allows the use of the compat entry point. This is different from
> the EFI handover protocol, and I am not sure which one you are using.
I should have mentioned this previously, here's the EFI-related kconfig that I
am using. If there's anything missing then please let me know:
CONFIG_EFI=y
CONFIG_EFI_EARLYCON=y
CONFIG_EFI_ESRT=y
# CONFIG_EFI_HANDOVER_PROTOCOL is not set
CONFIG_EFI_MIXED=y
CONFIG_EFI_RUNTIME_WRAPPERS=y
CONFIG_EFI_STUB=y
CONFIG_EFI_VARS_PSTORE=m
CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=y
Note that the EFI handover protocol support is disabled, I was under the
impression that it's not required for mixed mode.
Please let me know if there's any more information I can provide about my
testing / setup.
-Clayton
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-22 0:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 22:05 Clayton Craft
2024-03-21 22:48 ` Ard Biesheuvel
2024-03-22 0:06 ` Clayton Craft [this message]
2024-03-22 12:52 ` Ard Biesheuvel
2024-03-22 16:18 ` Clayton Craft
2024-03-22 16:51 ` Ard Biesheuvel
2024-03-22 17:57 ` Clayton Craft
2024-03-22 18:30 ` Ard Biesheuvel
2024-03-22 19:34 ` Clayton Craft
2024-03-23 12:39 ` Ard Biesheuvel
2024-03-23 17:18 ` Ard Biesheuvel
2024-03-24 5:53 ` Clayton Craft
2024-03-24 14:49 ` Hans de Goede
2024-03-24 17:43 ` Ard Biesheuvel
2024-03-24 20:45 ` Clayton Craft
2024-03-24 20:53 ` Ard Biesheuvel
2024-04-01 22:44 ` Clayton Craft
2024-04-02 6:25 ` Ard Biesheuvel
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=20240321170641.GK8211@craftyguy.net \
--to=clayton@craftyguy.net \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@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®