[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjh+h_-fd-gJz=wor42ZNmqq46QnB90jyfzqmKLsLFWOg@mail.gmail.com>
Date: Tue, 9 Jul 2019 22:15:21 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Ingo Molnar <mingo@...nel.org>, Kees Cook <keescook@...omium.org>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>, Len Brown <lenb@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Andrew Morton <akpm@...ux-foundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Tony Luck <tony.luck@...el.com>, Jiri Kosina <jkosina@...e.cz>,
Bob Moore <robert.moore@...el.com>,
Erik Schmauss <erik.schmauss@...el.com>
Subject: Re: [GIT PULL] x86/topology changes for v5.3
On Tue, Jul 9, 2019 at 8:21 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> Whee. It looks like it's bisecting to the same thing. Only partway
> done, but it feels very much like my desktop.
Confirmed.
With that config, I get this
c21ac93288f0 (refs/bisect/bad) Merge tag 'v5.2-rc6' into x86/asm, to
refresh the branch
8dbec27a242c (HEAD) x86/asm: Pin sensitive CR0 bits
873d50d58f67 x86/asm: Pin sensitive CR4 bits
ie those "pin sensitive bits" merge is bad, but before the commits is good.
I think there is _another_ problem too, and maybe it's the APCI one,
but this one triggers some issue before the other issue even gets to
play..
Linus
Powered by blists - more mailing lists