diff options
author | Daniel Drake | 2017-02-07 20:08:23 +0100 |
---|---|---|
committer | Ard Biesheuvel | 2017-03-17 19:53:12 +0100 |
commit | 822f5845f710e57d7e2df1fd1ee00d6e19d334fe (patch) | |
tree | 5fe3e4692fb8375faf8e1aeea1c2eae38c342250 /usr | |
parent | Linux 4.11-rc2 (diff) | |
download | kernel-qcow2-linux-822f5845f710e57d7e2df1fd1ee00d6e19d334fe.tar.gz kernel-qcow2-linux-822f5845f710e57d7e2df1fd1ee00d6e19d334fe.tar.xz kernel-qcow2-linux-822f5845f710e57d7e2df1fd1ee00d6e19d334fe.zip |
efi/esrt: Cleanup bad memory map log messages
The Intel Compute Stick STCK1A8LFC and Weibu F3C platforms both
log 2 error messages during boot:
efi: requested map not found.
esrt: ESRT header is not in the memory map.
Searching the web, this seems to affect many other platforms too.
Since these messages are logged as errors, they appear on-screen during
the boot process even when using the "quiet" boot parameter used by
distros.
Demote the ESRT error to a warning so that it does not appear on-screen,
and delete the error logging from efi_mem_desc_lookup; both callsites
of that function log more specific messages upon failure.
Out of curiosity I looked closer at the Weibu F3C. There is no entry in
the UEFI-provided memory map which corresponds to the ESRT pointer, but
hacking the code to map it anyway, the ESRT does appear to be valid with
2 entries.
Signed-off-by: Daniel Drake <drake@endlessm.com>
Cc: Matt Fleming <matt@codeblueprint.co.uk>
Acked-by: Peter Jones <pjones@redhat.com>
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions