Messages in this thread | | | Date | Mon, 9 Nov 2015 12:28:43 +0200 | From | Ville Syrjälä <> | Subject | Re: [PATCH] intel_idle: Don't use on Lenovo Ideapad S10-3t |
| |
On Sun, Nov 08, 2015 at 05:20:16PM -0200, Henrique de Moraes Holschuh wrote: > 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
Seems to require Windows, so no can do without major pain.
Considering acpi_idle works just fine, I doubt a new BIOS version would have anything to fix this, except maybe by accident.
> (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...
[ 0.000000] microcode: CPU0 microcode updated early to revision 0x107, date = 2009-08-25 [ 0.990876] microcode: CPU0 sig=0x106ca, pf=0x4, revision=0x107 [ 0.990972] microcode: CPU1 sig=0x106ca, pf=0x4, revision=0x107
No help unfortunately.
> > 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
-- Ville Syrjälä Intel OTC
| |