All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel@lists.freedesktop.org,
	Francesco Allertsen <fallertsen@gmail.com>
Subject: Re: Intel i915 freeze on latest git
Date: Wed, 9 Feb 2011 09:50:47 -0800	[thread overview]
Message-ID: <20110209095047.506b4372@jbarnes-desktop> (raw)
In-Reply-To: <1bdc18$jhlg3k@fmsmga002.fm.intel.com>

On Wed, 09 Feb 2011 17:09:10 +0000
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> On Wed, 9 Feb 2011 13:52:38 +0100, Francesco Allertsen <fallertsen@gmail.com> wrote:
> > On Wed, Feb 02, 2011 at 09:59:54AM +0000, Chris Wilson wrote:
> > > 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]
> > 
> > Ping?
> 
> I was optimistic that we might spot the real issue... However, you appear
> to be not alone and so I've pushed a disabling patch onto -fixes:
> 
> commit ac66808814036b4c33dd98091b2176ae6157f1a8
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Wed Feb 9 16:15:32 2011 +0000
> 
>     drm/i915: Disable RC6 on Ironlake
>     
>     The automatic powersaving feature is once again causing havoc, with 100%
>     reliable hangs on boot and resume on affected machines.
>     
>     Reported-by: Francesco Allertsen <fallertsen@gmail.com>
>     Reported-by: Gui Rui <chaos.proton@gmail.com>
>     Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=28582
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> That should work its way upstream shortly.

reverting the cleanup wasn't sufficient?

Francesco, if you revert the cleanup patch you bisected to, what
does /sys/kernel/debug/dri/0/i915_drpc_info report?

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2011-02-09 17:50 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
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 [this message]
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=20110209095047.506b4372@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=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.