From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: x86-tip.today (4cdf573) early instaboot
Date: Tue, 10 Apr 2018 14:37:57 +0200 [thread overview]
Message-ID: <1523363877.4942.2.camel@gmx.de> (raw)
In-Reply-To: <20180410085917.bo526ueprf7zfare@gmail.com>
On Tue, 2018-04-10 at 10:59 +0200, Ingo Molnar wrote:
> * Mike Galbraith <efault@gmx.de> wrote:
>
> > Hi Ingo,
> >
> > FYI, my i4790 box reboots immediately.. or close enough to it that you
> > see nothing at all before again meeting the bios splash. Master with
> > the ~same config works fine. I haven't poked around yet (work).
>
> Hm, so there's been a few 'dangerous' pieces of work merged yesterday-ish.
>
> Prime suspects would be:
>
> triton:~/tip> gll linus..x86/pti
>
> 0564258fb2cf: x86/pti: Leave kernel text global for !PCID
> a5df4f1f0d78: x86/pti: Never implicitly clear _PAGE_GLOBAL for kernel image
> e0bb456e3250: x86/pti: Enable global pages for shared areas
> efad2b415152: x86/mm: Do not forbid _PAGE_RW before init for __ro_after_init
> 4ddee6efdcd0: x86/mm: Comment _PAGE_GLOBAL mystery
> e71e836f463d: x86/mm: Remove extra filtering in pageattr code
> 64c80759408f: x86/mm: Do not auto-massage page protections <== WOOF
> 6baf4bec02db: x86/espfix: Document use of _PAGE_GLOBAL
> 8a57f4849f4f: x86/mm: Introduce "default" kernel PTE mask
> 606c7193d5fb: x86/mm: Undo double _PAGE_PSE clearing
> d1440b23c922: x86/mm: Factor out pageattr _PAGE_GLOBAL setting
> ee1400dda318: Merge branch 'linus' into x86/pti to pick up upstream changes
> 071ccc966ba5: x86/entry/64: Drop idtentry's manual stack switch for user entries
> 9820e1c3376c: x86/uapi: Fix asm/bootparam.h userspace compilation errors
>
> ... which you could test via 0564258fb2cf: if that insta-reboots too then
> 9820e1c3376c^1 is expected to work and 4 bisection steps should pinpoint the
> guilty commit ...
Thanks. I already had a full bisect running, so ended up doing more
than 4 steps, but ended up at the above.
-Mike
next prev parent reply other threads:[~2018-04-10 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 8:12 x86-tip.today (4cdf573) early instaboot Mike Galbraith
2018-04-10 8:59 ` Ingo Molnar
2018-04-10 12:37 ` Mike Galbraith [this message]
2018-04-10 14:06 ` Tom Lendacky
2018-04-10 15:48 ` Mike Galbraith
2018-04-12 7:09 ` Ingo Molnar
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=1523363877.4942.2.camel@gmx.de \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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