dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [v3.7-rcx] drm/i915: *ERROR* Timed out waiting for forcewake old ack to clear
Date: Tue, 27 Nov 2012 16:45:57 +0000	[thread overview]
Message-ID: <eeac1e$554nr0@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <CADDKRnDBHhqDzZVgB-8gv366OWKkamM9wR0+OcyfdX0kp_fKdA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

On Tue, 27 Nov 2012 17:29:36 +0100, Jörg Otte <jrg.otte@gmail.com> wrote:
> At boot-up with newer kernels (at least v3.6.x, v3.7-rc) I always see
> following on the bootup-display:
> 
> 3.7-rcx: [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting
> for forcewake old ack to clear.
> 3.6.x:    [drm:__gen6_gt_force_wake_mt_get] *ERROR* Force wake wait timed out

This is harmless error, just reporting a one-time conflict with the
state leftover by the BIOS. The fix is queued for 3.8.

commit 16995a9fe140802c026c2ce17bf7e232f86d57ab
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Oct 18 11:46:10 2012 +0100

    drm/i915: Clear FORCEWAKE when taking over from BIOS
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2012-11-27 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 16:29 [v3.7-rcx] drm/i915: *ERROR* Timed out waiting for forcewake old ack to clear Jörg Otte
2012-11-27 16:45 ` Chris Wilson [this message]
2012-12-01 13:40   ` Jörg Otte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='eeac1e$554nr0@AZSMGA002.ch.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox