From: Prarit Bhargava <prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
Cc: Lenny Szubowicz
<lszubowi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Ard Biesheuvel
<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: ESRT failures ... was Re: [PATCH 04/11] efi: Add efi_memmap_init_late() for permanent EFI memmap
Date: Tue, 26 Jul 2016 07:33:56 -0400 [thread overview]
Message-ID: <57974AA4.7090907@redhat.com> (raw)
In-Reply-To: <57963289.2090805-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 07/25/2016 11:38 AM, Prarit Bhargava wrote:
>
>
> On 07/25/2016 11:13 AM, Matt Fleming wrote:
>> On Mon, 25 Jul, at 11:11:31AM, Prarit Bhargava wrote:
>>>
>>>
>>> On 07/25/2016 10:44 AM, Matt Fleming wrote:
>>>> On Fri, 22 Jul, at 09:31:20AM, Prarit Bhargava wrote:
>>>>>
>>>>> Hmm ... maybe just a Dell specific quirk?
>>>>
>>>> Quirks are best avoided at all costs, platform-specific quirks doubly
>>>> so because there are just so many in the EFI arena that maintaining
>>>> them all would be a nightmare.
>>>>
>>>> Where possible we adopt a "most buggy implementation" approach to
>>>> compatibility, as a least common denominator.
>>>>
>>>> Could you try this patch out? It's not a final version, but I'd just
>>>> like to see if anything else explodes when we start returning reserved
>>>> regions.
>>>>
>>>> ---
>>>>
>>>> diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
>>>> index 05509f3aaee8..9857796c4cd4 100644
>>>> --- a/drivers/firmware/efi/efi.c
>>>> +++ b/drivers/firmware/efi/efi.c
>>>> @@ -299,7 +299,8 @@ int __init efi_mem_desc_lookup(u64 phys_addr, efi_memory_desc_t *out_md)
>>>>
>>>> if (!(md->attribute & EFI_MEMORY_RUNTIME) &&
>>>> md->type != EFI_BOOT_SERVICES_DATA &&
>>>> - md->type != EFI_RUNTIME_SERVICES_DATA) {
>>>> + md->type != EFI_RUNTIME_SERVICES_DATA &&
>>>> + md->type != EFI_RESERVED_TYPE) {
>>>
>>> I had tried this fix earlier FWIW and it causes the boot to hang.
>>
>> Do you know where it hangs? earlyprintk=efi might shed some light on
>> that if you don't have a serial console setup.
>>
>
> Nope, nothing else is displayed with "earlyprintk=efi" as a kernel parameter (I
> already had that as a kernel parameter).
I was ping'd by a Dell engineer who says that Dell is taking a look at this.
Most likely a BIOS fix will be released.
... I think that means I should drop the issue :)
P.
>
> P.
>
next prev parent reply other threads:[~2016-07-26 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 17:49 ESRT failures ... was Re: [PATCH 04/11] efi: Add efi_memmap_init_late() for permanent EFI memmap Prarit Bhargava
[not found] ` <57867F32.8040001-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-21 12:11 ` Matt Fleming
[not found] ` <20160721121136.GF26504-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-07-21 14:44 ` Prarit Bhargava
[not found] ` <5790DFD0.4020806-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-22 13:11 ` Matt Fleming
[not found] ` <20160722131101.GJ26504-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-07-22 13:31 ` Prarit Bhargava
[not found] ` <57922028.7070103-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-25 14:44 ` Matt Fleming
[not found] ` <20160725144431.GA31759-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-07-25 15:11 ` Prarit Bhargava
[not found] ` <57962C23.5090705-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-25 15:13 ` Matt Fleming
[not found] ` <20160725151344.GB31759-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-07-25 15:38 ` Prarit Bhargava
[not found] ` <57963289.2090805-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-26 11:33 ` Prarit Bhargava [this message]
[not found] ` <57974AA4.7090907-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-26 14:26 ` Matt Fleming
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=57974AA4.7090907@redhat.com \
--to=prarit-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lszubowi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
--cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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).