From: Nadav Amit <nadav.amit@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [BUG] GPF on reboot of box
Date: Fri, 6 Oct 2017 19:21:26 -0700 [thread overview]
Message-ID: <90068838-FBC3-4492-9D50-293509574617@gmail.com> (raw)
In-Reply-To: <20171006213956.0b33cf61@gandalf.local.home>
Steven Rostedt <rostedt@goodmis.org> wrote:
> Starting with v4.14-rc1 my box crashes during a reboot. All I get is
> the following:
>
> [ 250.615793] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [ 250.635639] reboot: Restarting system
> [ 250.639671] reboot: machine restart
> [ 250.643842] general protection fault: 0000 [#1] PREEMPT SMP KASAN
>
> Then nothing. No reboot, it just hangs there.
>
> I bisected it down to this commit:
>
> 660da7c9228f ("x86/mm: Enable CR4.PCIDE on supported systems")
>
> If I comment out the setting of X86_CR4_PCIDE in that commit, it boots
> fine. But...
>
> I noticed that commit c7ad5ad29 ("x86/mm/64: Initialize CR4.PCIDE
> early") moved the problem code from arch/x86/kernel/cpu/common.c to
> arch/x86/mm/init.c
>
> If I comment it out in v4.14-rc1, it crashes on boot up.
>
> It appears that my box doesn't like having X86_CR4_PCIDE set. it causes
> reboot to fail. But it also appears that setting that is required for
> some other code to work.
IIRC, there was a problem in rc1, which should be resolved in newer rcs.
If you need to run rc1, you can try to use the kernel parameter “nopcid".
Nadav
next prev parent reply other threads:[~2017-10-07 2:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 1:39 Steven Rostedt
2017-10-07 2:21 ` Nadav Amit [this message]
2017-10-07 3:13 ` Steven Rostedt
2017-10-07 13:36 ` Steven Rostedt
2017-10-07 22:49 ` Andy Lutomirski
2017-10-08 18:59 ` Steven Rostedt
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=90068838-FBC3-4492-9D50-293509574617@gmail.com \
--to=nadav.amit@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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®