Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1034125AbcJ0WZe (ORCPT ); Thu, 27 Oct 2016 18:25:34 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:45178 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1034039AbcJ0WZa (ORCPT ); Thu, 27 Oct 2016 18:25:30 -0400 Date: Fri, 28 Oct 2016 00:22:28 +0200 (CEST) From: Thomas Gleixner To: =?ISO-8859-15?Q?Ville_Syrj=E4l=E4?= cc: Len Brown , feng.tang@intel.com, Steven Rostedt , Sebastian Andrzej Siewior , Rik van Riel , "Srivatsa S. Bhat" , Peter Zijlstra , Arjan van de Ven , Rusty Russell , Oleg Nesterov , Tejun Heo , Andrew Morton , Paul McKenney , Linus Torvalds , Paul Turner , "Zhang, Rui" , "Rafael J . Wysocki" , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-acpi@vger.kernel.org Subject: Re: [PATCH] intel_idle: Don't use on Lenovo Ideapad S10-3t In-Reply-To: <1477591814-10985-1-git-send-email-ville.syrjala@linux.intel.com> Message-ID: References: <1446499360-31984-1-git-send-email-ville.syrjala@linux.intel.com> <1477591814-10985-1-git-send-email-ville.syrjala@linux.intel.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="8323329-1647712833-1477606950=:4913" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1441 Lines: 36 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1647712833-1477606950=:4913 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT On Thu, 27 Oct 2016, ville.syrjala@linux.intel.com wrote: > From: Ville Syrjälä > > 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. > > I sent this patch originally about one year ago, at which time I was > asked to file a bug, which I did [1], which was mostly a waste of time > since no one actually did anything to fix the problem. In the > meantime even acpi-idle got broken and then fixed again [2], so at > least there's still a working alternative. As intel_idle has never > worked on this machine, and it looks like no one has any real > intention to fix it, I'm going to suggest *again* that we simply > disable intel_idle on this machine and get on with life. Please put that patch on hold. We have some new data on this. Thanks, tglx --8323329-1647712833-1477606950=:4913--