* Doug Smythies <dsmyth...@telus.net> wrote: > On 2015.05.14 10:48 Ingo Molnar wrote: > > > * Juri Lelli <juri.le...@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.
So the way you could have picked it up is something like: # pick up 533445c6e533 git fetch git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/urgent git cherry-pick 533445c6e533 or pick up all pending scheduler fixes, amongst them 533445c6e533: git pull git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/urgent Or to export just that single one as a patch: git fetch git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/urgent git log --pretty=email --stat -p -1 533445c6e533 > Juri kindly sent me the patch. > > With the patch applied to an otherwise unmodified Kernel 4.1RC3, > Resume from suspend is working fine again. Great, thanks for testing! Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/