Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964846AbbENOmB (ORCPT ); Thu, 14 May 2015 10:42:01 -0400 Received: from cmta7.telus.net ([209.171.16.80]:36687 "EHLO cmta7.telus.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751090AbbENOl6 (ORCPT ); Thu, 14 May 2015 10:41:58 -0400 X-Authority-Analysis: v=2.0 cv=T4tSuY2Q c=1 sm=2 a=zJWegnE7BH9C0Gl4FFgQyA==:17 a=kj9zAlcOel0A:10 a=aatUQebYAAAA:8 a=Pyq9K9CWowscuQLKlpiwfMBGOR0=:19 a=7CQSdrXTAAAA:8 a=JfrnYn6hAAAA:8 a=pGLkceISAAAA:8 a=VwQbUJbxAAAA:8 a=eGN2DmW6xlieljihFh0A:9 a=CjuIK1q_8ugA:10 a=zJWegnE7BH9C0Gl4FFgQyA==:117 X-Telus-Outbound-IP: 173.180.45.4 From: "Doug Smythies" To: , , "'Ingo Molnar'" Cc: , "Doug Smythies" Subject: On resume from suspend only CPU 0 comes back on-line [REGRESSION][BISECTED] Date: Thu, 14 May 2015 07:41:54 -0700 Message-ID: <004801d08e54$20d5bd60$62813820$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdCOVB6rWv0vDkfKQaSp9ev/6jlorw== Content-Language: en-ca Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1986 Lines: 43 As of, or about, Kernel 4.1RC1 on resume from suspend only CPU 0 comes back on-line. The issue persists through Kernel 4.1RC3. This is on my test computer with an i7-2600K. I do not normally use suspend on this computer, but was doing so while working on a bug report. The kernel was bisected, and this is the result: 3c18d447b3b36a8d3c90dc37dfbd363cdb685d0a is the first bad commit commit 3c18d447b3b36a8d3c90dc37dfbd363cdb685d0a Author: Juri Lelli Date: Tue Mar 31 09:53:37 2015 +0100 sched/core: Check for available DL bandwidth in cpuset_cpu_inactive() Hotplug operations are destructive w.r.t. cpusets. In case such an operation is performed on a CPU belonging to an exlusive cpuset, the DL bandwidth information associated with the corresponding root domain is gone even if the operation fails (in sched_cpu_inactive()). For this reason we need to move the check we currently have in sched_cpu_inactive() to cpuset_cpu_inactive() to prevent useless cpusets reconfiguration in the CPU_DOWN_FAILED path. Signed-off-by: Juri Lelli Signed-off-by: Peter Zijlstra (Intel) Cc: Juri Lelli Link: http://lkml.kernel.org/r/1427792017-7356-2-git-send-email-juri.lelli@arm.com Signed-off-by: Ingo Molnar :040000 040000 10f8d81afdc8e625f8e6720883d3eb42c28d452b c08264528890941bad35d5d4cc134c03f259c534 M kernel Since I sometimes mess up using git bisect, and end up at some random result, the above was double checked manually: 3c18d447b3b36a8d3c90dc37dfbd363cdb685d0a has the issue. 4cd57f97135840f637431c92380c8da3edbe44ed (the previous commit) does not have the issue. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/