[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160511170917.GD4329@intel.com>
Date: Wed, 11 May 2016 20:09:17 +0300
From: Ville Syrjälä <ville.syrjala@...ux.intel.com>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, 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 Wed, May 11, 2016 at 08:26:58AM -0700, Arjan van de Ven 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.
>
> can you disable (in sysfs) all C states other than C0/C1 and see if that makes it go away?
> that would point at the problem pretty clearly...
No help there it seems.
However, as a sanity check I also tested that trick on the parent commit,
and disabling ACPI C2-C3 makes that one fail as well. Disabling just C3
is OK apparently.
--
Ville Syrjälä
Intel OTC
Powered by blists - more mailing lists