From: Laura Abbott <labbott@redhat.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: "x86@kernel.org" <x86@kernel.org>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
Justin Forbes <jforbes@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [REGRESSION] EFI mixed mode patch triggers boot failure
Date: Wed, 19 Oct 2016 13:04:36 -0700 [thread overview]
Message-ID: <dc0bc031-f20e-9ad0-57f4-cfa1e04f8f05@redhat.com> (raw)
Hi,
Fedora received a bug report https://bugzilla.redhat.com/show_bug.cgi?id=1384238
of a bootup failure with stable 4.7.6. efi=noruntime fixed the bootup problem.
1297667083d5442aafe3e337b9413bf02b114edb was linked as the cause
of the problem.
x86/efi: Only map RAM into EFI page tables if in mixed-mode
Waiman reported that booting with CONFIG_EFI_MIXED enabled on his
multi-terabyte HP machine results in boot crashes, because the EFI
region mapping functions loop forever while trying to map those
regions describing RAM.
While this patch doesn't fix the underlying hang, there's really no
reason to map EFI_CONVENTIONAL_MEMORY regions into the EFI page tables
when mixed-mode is not in use at runtime.
Reported-by: Waiman Long <waiman.long@hpe.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
CC: Theodore Ts'o <tytso@mit.edu>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Scott J Norton <scott.norton@hpe.com>
Cc: Douglas Hatch <doug.hatch@hpe.com>
Cc: <stable@vger.kernel.org> # v4.6+
Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk>
I made a request in the bugzilla for the reporter to
give a bootlog with efi=debug which I'm still waiting on.
Any ideas?
Thanks,
Laura
next reply other threads:[~2016-10-19 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 20:04 Laura Abbott [this message]
2016-10-19 21:13 ` [REGRESSION] EFI mixed mode patch triggers boot failure Laura Abbott
[not found] ` <7af87cde-ce79-d6e8-0797-54069a77f42b-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-20 12:03 ` Matt Fleming
[not found] ` <20161020120357.GB19876-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-10-24 19:54 ` Laura Abbott
[not found] ` <e34311e8-fe39-3b65-bd6d-8f1594e56336-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-27 22:34 ` Matt Fleming
[not found] ` <20170127223441.GJ31613-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2017-01-28 8:35 ` Laura Abbott
2017-01-30 13:10 ` Jiri Kosina
[not found] ` <alpine.LSU.2.20.1701301409270.25515-YHPUNQjx9ReKbouaWp301Q@public.gmane.org>
2017-02-01 17:35 ` Laura Abbott
[not found] ` <1208352f-ab6a-4489-d6b1-2f3e537f5e60-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-02-23 20:34 ` Jiri Kosina
[not found] ` <alpine.LSU.2.20.1702232132360.24579-YHPUNQjx9ReKbouaWp301Q@public.gmane.org>
2017-02-23 23:02 ` Laura Abbott
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=dc0bc031-f20e-9ad0-57f4-cfa1e04f8f05@redhat.com \
--to=labbott@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=jforbes@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=x86@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).