From: Joerg Roedel <jroedel@suse.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org,
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, Dave Hansen <dave.hansen@intel.com>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: efi boot failures due to PTI with 32 bit builds and Intel CPUs
Date: Thu, 30 Aug 2018 09:19:51 +0200 [thread overview]
Message-ID: <20180830071951.dv6wgnn6ikfhh7yt@suse.de> (raw)
In-Reply-To: <20180829201659.GA29801@roeck-us.net>
Hey Guenter,
On Wed, Aug 29, 2018 at 01:16:59PM -0700, 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.
> Here is the end of the log file:
>
> ----------------
> IN:
> 0xc75f1d1a: 66 90 nop
> 0xc75f1d1c: 0f 20 d8 movl %cr3, %eax
> 0xc75f1d1f: 0d 00 10 00 00 orl $0x1000, %eax
> 0xc75f1d24: 0f 22 d8 movl %eax, %cr3
>
> CR3 update: CR3=0e39b000
Thanks for the bug report, from a quick glance it looks like the kernel
is switching to an empty page-table. But I need to debug that further.
> qemu-system-i386 -kernel arch/x86/boot/bzImage -M q35 -cpu core2duo \
> -no-reboot -m 256 \
> -bios OVMF-pure-efi-32.fd \
> -usb -device usb-storage,drive=d0 \
> -drive file=rootfs.ext2,if=none,id=d0,format=raw \
> --append 'root=/dev/sda rw rootwait mem=256M console=ttyS0 console=tty noreboot' \
> -nographic
Can you please provide the exact OVMF-pure-efi-32.fd image and the
.config of the kernel?
Thanks a lot,
Joerg
next prev parent reply other threads:[~2018-08-30 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 20:16 Guenter Roeck
2018-08-29 20:28 ` Dave Hansen
2018-08-29 21:12 ` Guenter Roeck
2018-08-30 7:19 ` Joerg Roedel [this message]
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=20180830071951.dv6wgnn6ikfhh7yt@suse.de \
--to=jroedel@suse.de \
--cc=ak@linux.intel.com \
--cc=dave.hansen@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®