Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752191AbdCHJnv (ORCPT ); Wed, 8 Mar 2017 04:43:51 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:45761 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751309AbdCHJmf (ORCPT ); Wed, 8 Mar 2017 04:42:35 -0500 Date: Wed, 8 Mar 2017 09:25:16 +0100 (CET) From: Thomas Gleixner To: Bart Van Assche cc: "torvalds@linux-foundation.org" , "mingo@kernel.org" , "linux-kernel@vger.kernel.org" , "hpa@zytor.com" , "akpm@linux-foundation.org" Subject: Re: [GIT pull] CPU hotplug updates for 4.9 In-Reply-To: <1488925949.2739.3.camel@sandisk.com> Message-ID: References: <1488851515.6858.2.camel@sandisk.com> <1488925949.2739.3.camel@sandisk.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 Content-Length: 1047 Lines: 27 Bart, On Tue, 7 Mar 2017, Bart Van Assche wrote: > On Tue, 2017-03-07 at 10:30 +0100, Thomas Gleixner wrote: > > That's odd. There was no change related to the hotplug stuff post 4.10 > > neither in the core nor in that particular driver. > > > > I have no immediate clue what to look for aside of asking you whether you > > could do a bisect between 4.10 and 4.11-rc1. > > I will keep trying to find the commit that introduced this behavior. The > bisect I ran this morning yielded a commit that only changes ARM code which > does not make sense since I ran the bisect on an x86 system. I guess that > means that during one of the bisect steps I did not wait long enough to see > whether or not the hang occurs and hence that I provided incorrect input to > the bisect process. Before you proceed with bisecting, could you try Linus head first, especially commit: fa3aa7a54fe6 ("jiffies: Revert bogus conversion of NSEC_PER_SEC to TICK_NSEC") which fixes: 93825f2ec736 ("jiffies: Reuse TICK_NSEC instead of NSEC_PER_JIFFY") Thanks, tglx