All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Francesco Allertsen <fallertsen@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Intel i915 freeze on latest git
Date: Wed, 02 Feb 2011 09:59:54 +0000	[thread overview]
Message-ID: <1bdc18$jfb1or@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <20110202095656.GA2202@fujiko>

On Wed, 2 Feb 2011 10:56:57 +0100, Francesco Allertsen <fallertsen@gmail.com> wrote:
> On Tue, Feb 01, 2011 at 04:57:37PM +0000, Chris Wilson wrote:
> > So, if this is the issue, then simply commenting out the tweaking of
> > RSTDBYCTL in ironlake_enable_rc6() should prevent the hang.
> 
> I've tried the following patch
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index d7f237d..7769768 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -6527,7 +6527,6 @@ void ironlake_enable_rc6(struct drm_device *dev)
>  	ADVANCE_LP_RING();
>  
>  	I915_WRITE(PWRCTXA, dev_priv->pwrctx->gtt_offset | PWRCTX_EN);
> -	I915_WRITE(RSTDBYCTL, I915_READ(RSTDBYCTL) & ~RCX_SW_EXIT);
>  }
>  
>  /* Set up chip specific display functions */
> 
> And it still hangs.

Hmm, that was the only change I could spot between the two patches. Care
to disable that function and see what happens? [i.e. put a return before
we write anything to the ring]
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2011-02-02 10:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 11:22 Intel i915 freeze on latest git Francesco Allertsen
2011-02-01 12:05 ` Chris Wilson
2011-02-01 12:29   ` Francesco Allertsen
2011-02-01 13:16     ` Chris Wilson
2011-02-01 14:07       ` Francesco Allertsen
2011-02-01 16:31         ` Jesse Barnes
2011-02-01 16:57           ` Chris Wilson
2011-02-01 17:37             ` Jesse Barnes
2011-02-02  9:56             ` Francesco Allertsen
2011-02-02  9:59               ` Chris Wilson [this message]
2011-02-02 11:46                 ` Francesco Allertsen
2011-02-09 12:52                 ` Francesco Allertsen
2011-02-09 17:09                   ` Chris Wilson
2011-02-09 17:50                     ` Jesse Barnes
2011-02-09 17:53                       ` Jesse Barnes
2011-02-09 17:59                         ` Jesse Barnes
2011-02-09 18:06                       ` Chris Wilson
2011-02-10 12:10                     ` Francesco Allertsen
2011-02-10 18:34                       ` Jesse Barnes
2011-02-10 23:23                         ` Francesco Allertsen
2011-02-10 23:25                           ` Jesse Barnes
2011-02-11  7:28                             ` Francesco Allertsen
2011-02-11 17:16                               ` Jesse Barnes
2011-02-12  3:14                                 ` Grissiom
2011-02-13 16:53                                 ` Francesco Allertsen
2011-02-01 13:00   ` Francesco Allertsen
2011-02-01 13:18     ` Chris Wilson

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='1bdc18$jfb1or@fmsmga002.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fallertsen@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.