From: Thomas Gleixner <tglx@linutronix.de>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dou Liyang <douly.fnst@cn.fujitsu.com>
Subject: Re: [x86-tip] strange nr_cpus= boot regression
Date: Mon, 26 Sep 2016 13:36:47 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1609261327340.5483@nanos> (raw)
In-Reply-To: <1474892945.9232.23.camel@gmail.com>
CC'ed: Dou Liyang
On Mon, 26 Sep 2016, Mike Galbraith wrote:
> I've encountered a strange regression in tip, symptom is that if you
> boot with nr_cpus=nr_you_have, what actually boots is nr_you_have/2.
> Do not pass nr_cpus=, and all is well.
What's the number of possible cpus in your system?
> Bisection repeatedly goes as below, pointing to the nodeid merge,
> despite both timers/core and x86/apic (nodeid) being fine. Take tip
> HEAD, extract all of the commits from nodeid (plus the fix), and revert
> them in a quilt tree, the tree remains busted.
So you remove all the nodeid commits from tip/master and it's still broken?
> Checkout the timers/core merge commit, and merge nodeid with that, it is
> indeed bad.
> Bisecting takes you right the merge commit, with no commit
> being 'bad', see logs.
That's more than strange. An empty merge commit being the culprit.
Thanks,
tglx
next prev parent reply other threads:[~2016-09-26 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 12:29 Mike Galbraith
2016-09-26 12:39 ` Mike Galbraith
2016-09-26 13:40 ` Borislav Petkov
2016-09-26 14:15 ` Borislav Petkov
2016-09-26 14:27 ` Mike Galbraith
2016-09-26 17:36 ` Thomas Gleixner [this message]
2016-09-26 17:52 ` Thomas Gleixner
2016-09-26 19:35 ` Thomas Gleixner
2016-09-26 19:56 ` Thomas Gleixner
2016-09-27 3:13 ` Mike Galbraith
2016-09-27 4:09 ` Borislav Petkov
2016-09-27 2:07 ` Dou Liyang
2016-09-27 12:16 ` Thomas Gleixner
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=alpine.DEB.2.20.1609261327340.5483@nanos \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=douly.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=umgwanakikbuti@gmail.com \
/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®