lkml.org 
[lkml]   [2016]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [x86-tip] strange nr_cpus= boot regression
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

\
 
 \ /
  Last update: 2016-09-26 19:40    [W:0.101 / U:0.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site