[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170515143601.GF2935@codeblueprint.co.uk>
Date: Mon, 15 May 2017 15:36:01 +0100
From: Matt Fleming <matt@...eblueprint.co.uk>
To: Shuah Khan <shuahkh@....samsung.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net,
patches@...nelci.org, ben.hutchings@...ethink.co.uk,
stable@...r.kernel.org, Ard Biesheuvel <ard.biesheuvel@...aro.org>,
linux-efi@...r.kernel.org
Subject: Re: [PATCH 4.11 00/28] 4.11.1-stable review
On Fri, 12 May, at 10:01:41AM, Shuah Khan wrote:
>
> Greg/Matt,
>
> I started seeing this maybe since 4.11, so it isn't really a 4.11.1
> issue, however sounds like this shouldn't be an error message, since
> it is showing up on an older platform.
>
> efi: EFI_MEMMAP is not enabled.
> efi: Failed to lookup EFI memory descriptor for 0x00000000d9e0f018
>
>
> From 816e76129ed5fadd28e526c43397c79775194b5c Mon Sep 17 00:00:00 2001
> From: Matt Fleming <matt@...eblueprint.co.uk>
> Date: Mon, 29 Feb 2016 21:22:52 +0000
> Subject: [PATCH] efi: Allow drivers to reserve boot services forever
>
> This change was introduced in Commit: 816e76129ed5fadd28e526c43397c79775194b5c
>
> Matt!
>
> Shouldn't this be a debug message?? Is this a really an error??
Yes, it's most likely an error. We shouldn't be trying to reserve
EFI regions if we can't find them in the memory map.
Can you provide the full dmesg, please?
Powered by blists - more mailing lists