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 for Android: free password hash cracker in your pocket

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

Message-ID: <5733291E.80001@linux.intel.com>
Date:	Wed, 11 May 2016 05:44:14 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
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>,
	Sebastian Siewior <bigeasy@...utronix.de>,
	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 5/11/2016 3:19 AM, Ville Syrjälä wrote:

> Oh, and this was with acpi_idle. This machine already failed to
> resume from S3 with intel_idle since forever, as detailed in
> https://bugzilla.kernel.org/show_bug.cgi?id=107151
> but acpi_idle worked fine until now.

this is the important clue part afaics.

some of these very old Atom's had issues (bios?) with S3 if the cores were in a too-deep C state,
and at some point there was a workaround (I forgot where in the code) to ban those deep
C states around S3 on those cpus. I wonder if moving things around has made said workaround
ineffective.....