From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161745AbcIZRzA (ORCPT ); Mon, 26 Sep 2016 13:55:00 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:48258 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161042AbcIZRy6 (ORCPT ); Mon, 26 Sep 2016 13:54:58 -0400 Date: Mon, 26 Sep 2016 13:52:08 -0400 (EDT) From: Thomas Gleixner To: Mike Galbraith cc: Ingo Molnar , LKML , Borislav Petkov , Dou Liyang Subject: Re: [x86-tip] strange nr_cpus= boot regression In-Reply-To: Message-ID: References: <1474892945.9232.23.camel@gmail.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mike, On Mon, 26 Sep 2016, Thomas Gleixner wrote: > 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? Can you please provide your .config and the dmesg of a bad and a good run? Thanks, tglx