From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Kees Cook <keescook@chromium.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>, Len Brown <lenb@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Tony Luck <tony.luck@intel.com>, Jiri Kosina <jkosina@suse.cz>,
Bob Moore <robert.moore@intel.com>,
Erik Schmauss <erik.schmauss@intel.com>
Subject: Re: [GIT PULL] x86/topology changes for v5.3
Date: Wed, 10 Jul 2019 12:03:23 +0200 [thread overview]
Message-ID: <5258816.hjoiAQk5RS@kreacher> (raw)
In-Reply-To: <alpine.DEB.2.21.1907100039540.1758@nanos.tec.linutronix.de>
On Wednesday, July 10, 2019 1:00:32 AM CEST Thomas Gleixner wrote:
> On Wed, 10 Jul 2019, Thomas Gleixner wrote:
> > On Tue, 9 Jul 2019, Linus Torvalds wrote:
> > > I also don't have any logs, because the boot never gets far enough. I
> > > assume that there was a problem bringing up a non-boot CPU, and the
> > > eventual hang ends up being due to that.
> >
> > Hrm. I just build the tip of your tree and bootet it. It hangs at:
> >
> > [ 4.788678] ACPI: 4 ACPI AML tables successfully acquired and loaded
> > [ 4.793860] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
> > [ 4.821476] ACPI: Dynamic OEM Table Load:
> >
> > That's way after the secondary CPUs have been brought up. tip/master boots
> > without problems with the same config. Let me try x86/asm alone and also a
> > revert of the CR4/CR0 stuff.
>
> x86/asm works alone
>
> revert of cr4/0 pinning on top of your tree gets stuck as well
>
> > And while writing this the softlockup detector muttered:
>
> Have not yet fully bisected it, but Jiri did and he ended up with
>
> c522ad0637ca ("ACPICA: Update table load object initialization")
>
> Reverting that on top of your tree makes it work again. Tony has the same
> issue.
I have a revert of this one queued up (with a plan to push it later today).
Cheers,
Rafael
prev parent reply other threads:[~2019-07-10 10:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 16:27 Ingo Molnar
2019-07-09 1:45 ` pr-tracker-bot
2019-07-09 21:20 ` Linus Torvalds
2019-07-09 21:26 ` Linus Torvalds
2019-07-09 21:45 ` Linus Torvalds
2019-07-09 22:00 ` Linus Torvalds
2019-07-09 22:07 ` Linus Torvalds
2019-07-09 22:27 ` Thomas Gleixner
2019-07-09 23:00 ` Thomas Gleixner
2019-07-09 23:17 ` Thomas Gleixner
2019-07-10 0:31 ` Kees Cook
2019-07-10 11:27 ` Xi Ruoyao
2019-07-10 12:01 ` Xi Ruoyao
2019-07-10 12:19 ` Thomas Gleixner
2019-07-10 12:31 ` Jiri Kosina
2019-07-10 13:21 ` Peter Zijlstra
2019-07-10 13:27 ` Jiri Kosina
2019-07-10 13:28 ` Jiri Kosina
2019-07-10 13:31 ` Xi Ruoyao
2019-07-10 13:25 ` Xi Ruoyao
2019-07-10 13:44 ` Peter Zijlstra
2019-07-10 14:03 ` Thomas Gleixner
2019-07-10 14:26 ` Thomas Gleixner
2019-07-10 14:22 ` Jiri Kosina
2019-07-10 14:26 ` Peter Zijlstra
2019-07-10 15:13 ` Thomas Gleixner
2019-07-10 15:58 ` Xi Ruoyao
2019-07-10 19:42 ` [PATCH] x86/asm: Move native_write_cr0/3() out of line Thomas Gleixner
2019-07-10 19:59 ` Kees Cook
2019-07-10 20:00 ` Thomas Gleixner
2019-07-10 20:02 ` Peter Zijlstra
2019-07-10 20:19 ` [tip:x86/urgent] x86/asm: Move native_write_cr0/4() " tip-bot for Thomas Gleixner
2019-07-10 14:44 ` [GIT PULL] x86/topology changes for v5.3 Xi Ruoyao
2019-07-11 7:11 ` Nadav Amit
2019-07-11 7:16 ` Thomas Gleixner
2019-07-11 8:01 ` Peter Zijlstra
2019-07-11 15:08 ` Kees Cook
2019-07-11 17:09 ` Nadav Amit
2019-07-10 0:59 ` Linus Torvalds
2019-07-10 1:08 ` Linus Torvalds
2019-07-10 3:21 ` Linus Torvalds
2019-07-10 5:15 ` Linus Torvalds
2019-07-10 5:33 ` Kees Cook
2019-07-10 18:40 ` Linus Torvalds
2019-07-10 10:03 ` Rafael J. Wysocki [this message]
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=5258816.hjoiAQk5RS@kreacher \
--to=rjw@rjwysocki.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=erik.schmauss@intel.com \
--cc=jkosina@suse.cz \
--cc=keescook@chromium.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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®