From: Dave Hansen <dave.hansen@intel.com>
To: Guenter Roeck <linux@roeck-us.net>, linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Michal Hocko <mhocko@suse.com>, Andi Kleen <ak@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org, Joerg Roedel <jroedel@suse.de>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: efi boot failures due to PTI with 32 bit builds and Intel CPUs
Date: Wed, 29 Aug 2018 13:28:16 -0700 [thread overview]
Message-ID: <cd62e6b9-aec4-b8a5-be71-7edc10734955@intel.com> (raw)
In-Reply-To: <20180829201659.GA29801@roeck-us.net>
On 08/29/2018 01:16 PM, Guenter Roeck wrote:
>
> I see boot failures on mainline when trying to boot x86 images with an efi
> bios on Intel CPUs in qemu. Behavior is quite unusual: qemu dies silently
> after the kernel displays "Run /sbin/init as init process". With debugging
> enabled, qemu reports a CR3 update followed by a triple fault.
My first thought would be that the EFI pgd is broken somehow.
Is 0e39b000 in your kernel binary, or was it dynamically allocated?
What was CR2 when things went bad? Could you just share a full register
dump?
next prev parent reply other threads:[~2018-08-29 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 20:16 efi boot failures due to PTI with 32 bit builds and Intel CPUs Guenter Roeck
2018-08-29 20:28 ` Dave Hansen [this message]
2018-08-29 21:12 ` Guenter Roeck
2018-08-30 7:19 ` Joerg Roedel
2018-08-30 10:11 ` Guenter Roeck
2018-08-30 11:30 ` Joerg Roedel
2018-08-30 12:20 ` Guenter Roeck
2018-08-30 18:08 ` Joerg Roedel
2018-08-30 18:21 ` Linus Torvalds
2018-08-30 18:46 ` Joerg Roedel
2018-08-30 19:24 ` Guenter Roeck
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=cd62e6b9-aec4-b8a5-be71-7edc10734955@intel.com \
--to=dave.hansen@intel.com \
--cc=ak@linux.intel.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mhocko@suse.com \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 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.