From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] intel_idle: Don't use on Lenovo Ideapad S10-3t
Date: Wed, 4 Nov 2015 18:21:00 +0200 [thread overview]
Message-ID: <20151104162100.GT4437@intel.com> (raw)
In-Reply-To: <1A7043D5F58CCB44A599DFD55ED4C9484693D228@fmsmsx115.amr.corp.intel.com>
On Tue, Nov 03, 2015 at 03:04:21AM +0000, Brown, Len wrote:
> > Lenovo Ideapad S10-3t hangs coming out of S3 with intel_idle.
> > The two workaround that seem to help are "intel_idle.max_cstate=0"
> > or "nohz=off highres=off".
> >
> > At a first glance quirk_tigerpoint_bm_sts() seemed promising, but
> > even when moved to early_resume it didn't do anything.
> >
> > I have no idea what's wrong here, so let's just disable intel_idle
> > for these machines using a DMI match.
>
> Ville,
>
> It is great that several workarounds have been discovered.
>
> But it would be better to get a good idea of the root-cause
> before permanently ignoring the problem via a new
> black-list in the upstream kernel.
>
> Is it possible for you to file a bug at bugzilla.kernel.org
> against Product: power-management; component: intel_idle?
https://bugzilla.kernel.org/show_bug.cgi?id=107151
>
> In it, please put the following information.
>
> If this is a regression, the oldest kernel that broke.
I'll repeat the details here just in case people are too lazy to look at
the bug:
It seems intel_idle has always been flaky with this hardware. It used to
work a little better in the past, but not perfectly.
I tried to bisect the total breakage starting from v3.11, and found the
following commit to be at fault:
commit a8d46b9e4e487301affe84fa53de40b890898604
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Tue Sep 30 02:29:01 2014 +0200
ACPI / sleep: Rework the handling of ACPI GPE wakeup from
suspend-to-idle
Before that I observed three different behaviours for S3 resume:
a) sometimes it resumed OK
b) sometimes it resumed part way, but kbd/network etc. were still
dead, but then pressing the power button made it finish the resume
somehow
c) same as the previous, except the power button press also made it
all the way to userspace and initiated a normal shutdown
The same kernel could exhibit both a) and b), or both a) and c).
After a8d46b9e4e48 it never resumes, no matter if I press the power
button or not.
> When booted with intel_idle, and then without:
>
> dmesg | grep idle
> grep . /sys/devices/system/cpu/cpu0/cpuidle/*/*
> # turbostat --debug sleep 10 2> turbostat.out
>
> # cd /sys/devices/system/clocksource/clocksource0
> grep . available_clocksource current_clocksource
>
>
> Other boot options to test:
>
> maxcpus=1
> nohpet
>
> intel_idle.max_cstate=3
> and if that fails
> intel_idle.max_cstate=2
> and if that fails
> intel_idle.max_cstate=1
None of these help.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2015-11-04 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 21:22 [PATCH] intel_idle: Don't use on Lenovo Ideapad S10-3t ville.syrjala
2015-11-03 3:04 ` Brown, Len
2015-11-04 16:21 ` Ville Syrjälä [this message]
2015-11-08 19:20 ` Henrique de Moraes Holschuh
2015-11-09 10:28 ` Ville Syrjälä
2016-10-27 18:10 ` ville.syrjala
2016-10-27 22:22 ` Thomas Gleixner
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=20151104162100.GT4437@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).