linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "Brown, Len" <len.brown@intel.com>,
	"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: Sun, 8 Nov 2015 17:20:16 -0200	[thread overview]
Message-ID: <20151108192016.GA7063@khazad-dum.debian.net> (raw)
In-Reply-To: <20151104162100.GT4437@intel.com>

On Wed, 04 Nov 2015, Ville Syrjälä wrote:
> 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

This is a shot in the dark, but...

The Atom N450 public errata sheet is nightmare fuel, and Ville's Ideapad is
running that hellish processor on outdated microcode.

http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/atom-processor-n400-specification-update.pdf

Ville, you might want to insure you're at the latest BIOS for the S10-3t:
http://support.lenovo.com/us/en/products/laptops-and-netbooks/ideapad-s-series-netbooks/ideapad-s10-3t/downloads/DS010786

(don't bother with changelogs to make any sort of update-or-not decisions:
Lenovo changelogs are known to often be incomplete).

I also strongly recommend that you should install your distro's microcode
update package: your microcode should have been revision 0x107 or higher, it
has been in the public microcode distribution since Q2/Q3-2010...

Now, as I said, this is all a shot in the dark, and it might not help at all
with the hangs.  But it looks like something worth trying...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2015-11-08 19:20 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ä
2015-11-08 19:20     ` Henrique de Moraes Holschuh [this message]
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=20151108192016.GA7063@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=ville.syrjala@linux.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).