From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753725AbbCBIzH (ORCPT ); Mon, 2 Mar 2015 03:55:07 -0500 Received: from mga01.intel.com ([192.55.52.88]:36315 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753665AbbCBIy7 (ORCPT ); Mon, 2 Mar 2015 03:54:59 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,674,1418112000"; d="scan'208";a="659091129" Date: Mon, 2 Mar 2015 10:55:08 +0200 From: David Weinehall To: Imre Deak Cc: intel-gfx@lists.freedesktop.org, =?iso-8859-1?Q?Bj=F8rn?= Mork , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, stable@vger.kernel.org, Daniel Vetter Subject: Re: [Intel-gfx] [PATCH] drm/i915: fix failure to power off after hibernate Message-ID: <20150302085508.GA12778@boom> Mail-Followup-To: Imre Deak , intel-gfx@lists.freedesktop.org, =?iso-8859-1?Q?Bj=F8rn?= Mork , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, stable@vger.kernel.org, Daniel Vetter References: <87bnkjcqjt.fsf@nemi.mork.no> <1424789904-26699-1-git-send-email-bjorn@mork.no> <1424794340.15554.3.camel@intel.com> <878ufnjfrr.fsf@nemi.mork.no> <1424889214.5991.4.camel@intel.com> <87bnkhqan8.fsf@nemi.mork.no> <1424976648.17078.1.camel@intel.com> <20150226200127.GU24485@phenom.ffwll.local> <20150227121504.GA30560@boom> <1425061421.14060.22.camel@ideak-mobl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1425061421.14060.22.camel@ideak-mobl> X-Editor: Vi Improved X-Accept-Language: Swedish, English X-GPG-Fingerprint: ED69 8CF5 6102 21B9 AFD1 9DB7 0B27 96FD 15DA A404 X-GPG-Key: http://www.acc.umu.se/~tao/files/pub_15daa404.gpg.asc User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 27, 2015 at 08:23:41PM +0200, Imre Deak wrote: > We've checked today with Ville a few machines we've found from GEN2 to > GEN5+. There was one Thinkpad x61s (GEN4) where I could reproduce the > exact same problem and get rid of it using the same workaround. All the > others were non-Lenovo (including GEN4) mobile and desktop platforms and > none of these had the problem. I also tried it on a Lenovo IVB > ultrabook, which also works fine. So the current theory is that it's > related to GEN4 Thinkpad BIOSes, and so we need to change the condition > to match that at least. If you need more ThinkPads to test with I have a few at home :) Kind regards, David