Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753474AbdCIKXI (ORCPT ); Thu, 9 Mar 2017 05:23:08 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:50215 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752511AbdCIKXE (ORCPT ); Thu, 9 Mar 2017 05:23:04 -0500 Date: Thu, 9 Mar 2017 11:22:53 +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: <1489001551.2813.3.camel@sandisk.com> Message-ID: References: <1488851515.6858.2.camel@sandisk.com> <1488925949.2739.3.camel@sandisk.com> <1489001551.2813.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: 1085 Lines: 29 Bart, On Wed, 8 Mar 2017, Bart Van Assche wrote: > Sorry but the cpuhp_issue_call() still occurs with Linus' latest tree > (commit ec3b93ae0bf4 / Merge branch 'x86-urgent-for-linus' of > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip). > > This morning I discovered that the hang only occurs if I/O AT support is > enabled in the BIOS. I had enabled I/O AT support in the BIOS on February > 23rd. With I/O AT support enabled the following warning appears during boot: That's interesting, but I have no idea how that's related. > WARNING: CPU: 8 PID: 596 at drivers/dma/ioat/dca.c:342 ioat_dca_init+0x185/0x190 [ioatdma] > ioatdma 0000:00:04.0: APICID_TAG_MAP set incorrectly by BIOS, disabling DCA .. > In contrast with previous tests this morning I have been able to reproduce > this hang with kernel v4.10. So it's not a kernel v4.10 regression. But the > hang did not occur in a test with kernel v4.9.7. I assume this means that > the regression got introduced between the v4.9 and v4.10 kernels. Is it always the x86_pkg_thermal init which locks up? Thanks, tglx