From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933951AbcI0DNu (ORCPT ); Mon, 26 Sep 2016 23:13:50 -0400 Received: from mail-lf0-f68.google.com ([209.85.215.68]:35544 "EHLO mail-lf0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752987AbcI0DNl (ORCPT ); Mon, 26 Sep 2016 23:13:41 -0400 Message-ID: <1474946017.3801.19.camel@gmail.com> Subject: Re: [x86-tip] strange nr_cpus= boot regression From: Mike Galbraith To: Thomas Gleixner Cc: Ingo Molnar , LKML , Borislav Petkov , Dou Liyang Date: Tue, 27 Sep 2016 05:13:37 +0200 In-Reply-To: References: <1474892945.9232.23.camel@gmail.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2016-09-26 at 15:35 -0400, Thomas Gleixner wrote: > On Mon, 26 Sep 2016, Thomas Gleixner wrote: > > Can you please provide your .config and the dmesg of a bad and a good run? > > Don't bother. I found it. > > It's a merge artifact. So git bisect pointing at the merge commit is > entirely correct. > > mainline moves > > > num_processors++; > > to a different place in the function. See commit c291b0151585. > > Now the nodeid patch set in x86/apic does not have this commit and so > f7c28833c2520 removes num_processors++ from the original location before > c291b0151585. Whew, no mythical creature infestation. Thanks, next encounter with such an artifact should provide markedly less entertainment. -Mike