All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: "'Ingo Molnar'" <mingo@kernel.org>, "'Juri Lelli'" <juri.lelli@arm.com>
Cc: <peterz@infradead.org>, <linux-kernel@vger.kernel.org>
Subject: RE: On resume from suspend only CPU 0 comes back on-line [REGRESSION][BISECTED]
Date: Thu, 14 May 2015 15:12:24 -0700	[thread overview]
Message-ID: <007601d08e93$0fdca700$2f95f500$@net> (raw)
In-Reply-To: <20150514174804.GA19586@gmail.com>

On 2015.05.14 10:48 Ingo Molnar wrote:

> * Juri Lelli <juri.lelli@arm.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.



  reply	other threads:[~2015-05-14 22:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 14:41 On resume from suspend only CPU 0 comes back on-line [REGRESSION][BISECTED] Doug Smythies
2015-05-14 15:01 ` Juri Lelli
2015-05-14 17:48   ` Ingo Molnar
2015-05-14 22:12     ` Doug Smythies [this message]
2015-05-15  6:51       ` Ingo Molnar
2015-05-15  8:50       ` Juri Lelli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='007601d08e93$0fdca700$2f95f500$@net' \
    --to=dsmythies@telus.net \
    --cc=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.