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 17:57:01 +0000 [thread overview]
Message-ID: <fe09869c2d853bde8ce0feb537c4dab09014f5d9@craftyguy.net> (raw)
In-Reply-To: <CAMj1kXFmnv+FGRMnnJMJejj5yvSybgZTNEYZz0hxb6K9VAeo1Q@mail.gmail.com>
March 22, 2024 at 9:51 AM, "Ard Biesheuvel" <ardb@kernel.org> wrote:
> > As I mentioned initially, I bisected my failure to e2ab9eab32. Does that give
> >
> > any hint about what might be the problem?
> >
>
> Not at all, unfortunately. What we might try is to back out the
>
> changes step by step. I can prepare a branch for you if you like.
Yeah sure, if you don't mind! I'd be happy to test changes in a branch to try and figure out what is causing this.
-Clayton
next prev parent reply other threads:[~2024-03-22 17:57 UTC|newest]
Thread overview: 19+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2024-03-21 21:45 Clayton Craft
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=fe09869c2d853bde8ce0feb537c4dab09014f5d9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.