From: Matt Fleming <matt@codeblueprint.co.uk>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
stable@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-efi@vger.kernel.org
Subject: Re: [PATCH 4.11 00/28] 4.11.1-stable review
Date: Mon, 15 May 2017 15:36:01 +0100 [thread overview]
Message-ID: <20170515143601.GF2935@codeblueprint.co.uk> (raw)
In-Reply-To: <efa3b911-93f6-29b4-a9ca-e0d9b480a4ef@osg.samsung.com>
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@codeblueprint.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?
next parent reply other threads:[~2017-05-15 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170511141221.109842231@linuxfoundation.org>
[not found] ` <465c70c9-1dbc-7c57-c6aa-b6df740663ed@osg.samsung.com>
[not found] ` <efa3b911-93f6-29b4-a9ca-e0d9b480a4ef@osg.samsung.com>
2017-05-15 14:36 ` Matt Fleming [this message]
2017-05-15 17:28 ` [PATCH 4.11 00/28] 4.11.1-stable review Shuah Khan
2017-05-25 11:39 ` Matt Fleming
[not found] ` <20170525113908.GC3546-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2017-05-25 20:06 ` 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=20170515143601.GF2935@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patches@kernelci.org \
--cc=shuahkh@osg.samsung.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).