linux-kernel - RE: On resume from suspend only CPU 0 comes back on-line [REGRESSION][BISECTED]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 14 May 2015 15:12:24 -0700
From:	"Doug Smythies" <dsmythies@...us.net>
To:	"'Ingo Molnar'" <mingo@...nel.org>,
	"'Juri Lelli'" <juri.lelli@....com>
Cc:	<peterz@...radead.org>, <linux-kernel@...r.kernel.org>
Subject: RE: On resume from suspend only CPU 0 comes back on-line [REGRESSION][BISECTED]

On 2015.05.14 10:48 Ingo Molnar wrote:

> * Juri Lelli <juri.lelli@....com> wrote:
>>> On 14/05/15 15:41, Doug Smythies wrote:
>>> 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:
>>> 
>> 
>> Does commit 533445c6e533 "sched/core: Fix regression in
>> cpuset_cpu_inactive() for suspend" on tip/sched/core
>> fix the bug?

> That would be sched/urgent primarily, not sched/core:
> git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/urgent
> I'll get this fix to Linus ASAP.

I could not seem to figure out how to get the patch from tip,
and any version I could find on internet would not apply properly.
 
Juri kindly sent me the patch.

With the patch applied to an otherwise unmodified Kernel 4.1RC3,
Resume from suspend is working fine again.

Thanks.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/