From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.? Date: Wed, 17 Oct 2012 23:58:21 +0100 Message-ID: <275ffc$71lqji@fmsmga002.fm.intel.com> References: <507E4D8F.4080901@fisher-privat.net> <20121017154454.00004e7c@unknown> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by gabe.freedesktop.org (Postfix) with ESMTP id A4AC19E776 for ; Wed, 17 Oct 2012 15:58:42 -0700 (PDT) In-Reply-To: <20121017154454.00004e7c@unknown> 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: Ben Widawsky , Oleksij Rempel Cc: intel-gfx@lists.freedesktop.org, Mika Kuoppala List-Id: intel-gfx@lists.freedesktop.org On Wed, 17 Oct 2012 15:44:54 -0700, Ben Widawsky wrote: > On Wed, 17 Oct 2012 08:17:51 +0200 > Oleksij Rempel wrote: > > > Hallo all, > > > > i get on Asus Zenbook UX32A [IVB] fallowing errors: > > [ 4.464893] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out > > waiting for forcewake old ack to clear. > > [ 6678.604211] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out > > waiting for forcewake old ack to clear. > > [ 9144.381337] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out > > waiting for forcewake old ack to clear. > > [ 9189.374375] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out > > waiting for forcewake old ack to clear. > > > > I get it after resume from suspend to ram. > > Is it some thing you need to know? > > Is this a regression? No, the issue appears to be that we do not sanitise the forcewake upon takeover from BIOS and as such we leave it with RC6 suspended and no pending clear of the forcewake. The timeout of the first wait after boot/resume is to be expected. I believe Mika Kuoppala was volunteered to write a small patch to address this... -Chris -- Chris Wilson, Intel Open Source Technology Centre