linux-kernel - Re: S3 resume regression [1cf4f629d9d2 ("cpu/hotplug: Move online calls to hotplugged cpu")]

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]

Message-ID: <57332171.8070403@linutronix.de>
Date:	Wed, 11 May 2016 14:11:29 +0200
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Ville Syrjälä <ville.syrjala@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>
Cc:	linux-arch@...r.kernel.org, Rik van Riel <riel@...hat.com>,
	Rafael Wysocki <rafael.j.wysocki@...el.com>,
	"Srivatsa S. Bhat" <srivatsa@....edu>,
	Peter Zijlstra <peterz@...radead.org>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Steven Rostedt <rostedt@...dmis.org>,
	Oleg Nesterov <oleg@...hat.com>, Tejun Heo <tj@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Paul Turner <pjt@...gle.com>, linux-kernel@...r.kernel.org,
	rui.zhang@...el.com, len.brown@...el.com
Subject: Re: S3 resume regression [1cf4f629d9d2 ("cpu/hotplug: Move online
 calls to hotplugged cpu")]

On 05/11/2016 12:19 PM, Ville Syrjälä wrote:
> Hi,
Hi,

> I have a Lenovo Ideapad S10-3t machine here (Atom N450, 1 core, 2 HT)
> which fails to resume from S3 on 4.6-rc releases. I bisected it down to
> 
> commit 1cf4f629d9d246519a1e76c021806f2a51ddba4d
> Author: Thomas Gleixner <tglx@...utronix.de>
> Date:   Fri Feb 26 18:43:39 2016 +0000
> 
>     cpu/hotplug: Move online calls to hotplugged cpu
> 
> Unfortunately that won't revert cleanly, and neither does the merge
> commit, so I was unable to see if that is the only problematic commit
> in 4.6.
> 
> Any ideas?

do you have a backtrace or anything or is it just not working and you
end up with a blank screen?

Sebastian