From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Harrigan Subject: Re: slow graphics after Suspend to RAM Date: Thu, 17 Mar 2011 09:32:39 -0600 Message-ID: <20110317153239.GA6274@2530p.rmtc.fedex.com> References: <20110316235920.GA392@ink.rmtc.fedex.com> <1bdc18$jt7ta9@fmsmga002.fm.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx18.infosec.fedex.com (mx18.infosec.fedex.com [199.81.216.54]) by gabe.freedesktop.org (Postfix) with ESMTP id 29EED9E738 for ; Thu, 17 Mar 2011 08:32:18 -0700 (PDT) Received: from netsvr20.prod.fedex.com (netsvr20.prod.fedex.com [199.81.10.128]) by inet04.prod.fedex.com (8.12.11/8.12.11) with ESMTP id p2HFWFW6029389 for ; Thu, 17 Mar 2011 10:32:15 -0500 (CDT) Content-disposition: inline Received: from localhost ([199.82.94.58]) by emmsvr20.prod.fedex.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTP id <0LI700BEQKHQC810@emmsvr20.prod.fedex.com> for intel-gfx@lists.freedesktop.org; Thu, 17 Mar 2011 10:32:15 -0500 (CDT) In-reply-to: <1bdc18$jt7ta9@fmsmga002.fm.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org * chris@chris-wilson.co.uk (Mar 17, 2011 @ 07:51+0000): > On Wed, 16 Mar 2011 17:59:20 -0600, John Harrigan wrote: > > I have a Lenovo X201 laptop with an i7-620M processor. After I resume > > from a Suspend to RAM the graphics are very slow. Suspend to Disk does > > not cause the same problem and doing a Suspend to Disk after a Suspend > > to RAM fixes the problem. > > Known problem. The PAT lose the WC bits for the GTT aperture on resume. > There is a workaround that we can do: recreate the ioremapping upon > resume. (But the root cause is not a gfx driver bug.) Thanks. Is there an existing bug report somewhere where I should supply logs and debug info?