From: Ard Biesheuvel <ardb@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: linux-efi <linux-efi@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Issue] EFI runtime-wrapper is broken
Date: Fri, 28 Oct 2022 11:39:22 +0200 [thread overview]
Message-ID: <CAMj1kXFUfAE6bGTxTFDQe9HxAZAuAOXenU+GC-39QJfaBOt4tA@mail.gmail.com> (raw)
In-Reply-To: <d469f6b9-d23a-abe6-27b7-f58f9de12a45@redhat.com>
On Fri, 28 Oct 2022 at 11:38, Gavin Shan <gshan@redhat.com> wrote:
>
> Hi Ard,
>
> On 10/28/22 5:21 PM, Ard Biesheuvel wrote:
> > On Fri, 28 Oct 2022 at 11:10, Gavin Shan <gshan@redhat.com> wrote:
> >> I ran into the following crash with v6.1.rc2. I'm not sure if it's known
> >> issue. Last good version is v6.0.rc6/rc7. The kernel configuration is attached.
> >
> > This is probably related to the patch below. It means the firmware is
> > buggy, and does not work as it should if the firmware never calls
> > SetVirtualAddressMap() [and doing so is explicitly described as
> > OPTIONAL by the EFI specification].
> >
> > The problem here is that other EFI implementations (primarily the
> > Qualcomm ones used on Windows-on-ARM laptops) are buggy too, and don't
> > tolerate SetVirtualAddressMap().
> >
> > Can you try whether reverting the patch below helps?
> >
>
> I ran into the issue on server, equipped with Ampere CPUs. With d3549a938b73
> reverted, the crash disappeared.
>
Thanks for confirming
Can you please share the complete boot log and the DMI/SMBIOS data? Thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-10-28 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d799b60c-ff4e-44ae-84be-d9ade761ec6d@redhat.com>
2022-10-28 9:21 ` [Issue] EFI runtime-wrapper is broken Ard Biesheuvel
2022-10-28 9:38 ` Gavin Shan
2022-10-28 9:39 ` Ard Biesheuvel [this message]
2022-11-08 12:26 ` Thorsten Leemhuis
2022-11-08 13:57 ` Ard Biesheuvel
2022-11-09 15:45 ` [Issue] EFI runtime-wrapper is broken #forregzbot Thorsten Leemhuis
2022-11-13 18:31 ` Thorsten Leemhuis
2022-10-28 9:45 ` [Issue] EFI runtime-wrapper is broken Ard Biesheuvel
2022-10-30 16:49 ` [Issue] EFI runtime-wrapper is broken #forregzbot Thorsten Leemhuis
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=CAMj1kXFUfAE6bGTxTFDQe9HxAZAuAOXenU+GC-39QJfaBOt4tA@mail.gmail.com \
--to=ardb@kernel.org \
--cc=gshan@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@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;
as well as URLs for NNTP newsgroup(s).