From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: Regression with commit 0a67361dcdaa
Date: Thu, 16 Apr 2020 17:56:38 +0300 [thread overview]
Message-ID: <9ae0c751-5024-6eda-ca78-80cfd1ed066f@linux.intel.com> (raw)
In-Reply-To: <CAMj1kXGGdwuP6X5jvbqmjsP2+bZ7CoJKZ5-WVoPYEjq9HTjuDA@mail.gmail.com>
On 4/16/20 5:36 PM, Ard Biesheuvel wrote:
> On Thu, 16 Apr 2020 at 16:35, Jarkko Nikula
> <jarkko.nikula@linux.intel.com> wrote:
>>
>> Hi
>>
>> v5.7-rc1 hangs in early boot on an Intel Atom based prototype hardware
>> while v5.6 boots fine. I bisected the regression into 0a67361dcdaa
>> ("efi/x86: Remove runtime table address from kexec EFI setup data").
>>
>> v5.7-rc1 caused a reboot loop on another Intel Core based prototype HW.
>> Reboots also on top of 0a67361dcdaa but boots fine with that commit
>> reverted.
>>
>> Our test system uses kexec to boot the test kernel. These two machines
>> got regression with v5.7-rc1. We have also others that boot fine.
>>
>
> This should already be fixed in Linus's tree. Please report back
> whether that solves your problem or not.
>
Ah, I forgot to pull & test before bisecting...
Yes, both machines boot fine with the HEAD 00086336a8d9 ("Merge tag
'efi-urgent-2020-04-15' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip").
--
Jarkko
next prev parent reply other threads:[~2020-04-16 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 14:35 Regression with commit 0a67361dcdaa Jarkko Nikula
2020-04-16 14:36 ` Ard Biesheuvel
2020-04-16 14:56 ` Jarkko Nikula [this message]
2020-04-16 14:57 ` 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=9ae0c751-5024-6eda-ca78-80cfd1ed066f@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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