From: Mike Krinkin <krinkin.m.u-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org,
ricardo.neri-calderon-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org,
pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
scott.lawson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Cannot load linux after recent efi-related changes
Date: Sat, 17 Sep 2016 19:24:00 +0300 [thread overview]
Message-ID: <20160917162357.GA4122@gmail.com> (raw)
Hello,
after commit 3dad6f7f6975 ("x86/efi: Defer efi_esrt_init until after
memblock_x86_fill") kernel hits BUG_ON __efi_enter_virtual_mode because
efi.systab is NULL. With older kernel versions i face the problem with
efi_mem_reserve described in the commit.
AFAICS, get_systab_virt_addr called from efi_map_regions should set
efi.systab, but i dumped memory desciptors in efi_map_regions and
apparently none of them describes region that contains efi_phys.systab,
so efi.systab remains unset.
WARNING: multiple messages have this Message-ID (diff)
From: Mike Krinkin <krinkin.m.u@gmail.com>
To: mingo@kernel.org, tglx@linutronix.de, hpa@zytor.com,
ricardo.neri-calderon@linux.intel.com, ard.biesheuvel@linaro.org,
matt@codeblueprint.co.uk, pjones@redhat.com,
scott.lawson@intel.com
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Cannot load linux after recent efi-related changes
Date: Sat, 17 Sep 2016 19:24:00 +0300 [thread overview]
Message-ID: <20160917162357.GA4122@gmail.com> (raw)
Hello,
after commit 3dad6f7f6975 ("x86/efi: Defer efi_esrt_init until after
memblock_x86_fill") kernel hits BUG_ON __efi_enter_virtual_mode because
efi.systab is NULL. With older kernel versions i face the problem with
efi_mem_reserve described in the commit.
AFAICS, get_systab_virt_addr called from efi_map_regions should set
efi.systab, but i dumped memory desciptors in efi_map_regions and
apparently none of them describes region that contains efi_phys.systab,
so efi.systab remains unset.
next reply other threads:[~2016-09-17 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 16:24 Mike Krinkin [this message]
2016-09-17 16:24 ` Cannot load linux after recent efi-related changes Mike Krinkin
[not found] ` <20160917162357.GA4122-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-18 1:14 ` Mike Krinkin
2016-09-18 1:14 ` Mike Krinkin
2016-09-19 11:14 ` Matt Fleming
[not found] ` <20160919111424.GB2892-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-09-19 11:36 ` Mike Krinkin
2016-09-19 11:36 ` Mike Krinkin
2016-09-19 11:41 ` 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=20160917162357.GA4122@gmail.com \
--to=krinkin.m.u-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
--cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=ricardo.neri-calderon-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=scott.lawson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.