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: Fri, 22 Mar 2024 19:34:12 +0000 [thread overview]
Message-ID: <8a64ba697d719bc9750e6fffc268e194dfde16e5@craftyguy.net> (raw)
In-Reply-To: <CAMj1kXEH4CTnQ3d+Z-TnqNUhFaFc1yH+Eaa6cHk9-vZ_geQ2nw@mail.gmail.com>
March 22, 2024 at 11:30 AM, "Ard Biesheuvel" <ardb@kernel.org> wrote:
>
> On Fri, 22 Mar 2024 at 19:57, Clayton Craft <clayton@craftyguy.net> wrote:
>
> I have pushed a branch below that reverts the patch you identified in
>
> 4 separate steps. Could you please check which step makes your system
>
> boot again?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton
>
Thanks a lot for doing this, I really appreciate the help!
It looks like if I build from 868a7245, booting breaks again on my Bay Trail systems. If I put back 00e85ab5, they boot again.
-Clayton
next prev parent reply other threads:[~2024-03-22 19:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 22:05 x86_64 32-bit EFI mixed mode boot broken Clayton Craft
2024-03-21 22:48 ` Ard Biesheuvel
2024-03-22 0:06 ` Clayton Craft
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 [this message]
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=8a64ba697d719bc9750e6fffc268e194dfde16e5@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