dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Francesco Allertsen <fallertsen@gmail.com>
Cc: Gui Rui <chaos.proton@gmail.com>, dri-devel@lists.freedesktop.org
Subject: Re: Intel i915 freeze on latest git
Date: Fri, 11 Feb 2011 09:16:33 -0800	[thread overview]
Message-ID: <20110211091633.1c63fa46@jbarnes-desktop> (raw)
In-Reply-To: <20110211072837.GA2454@fujiko>

On Fri, 11 Feb 2011 08:28:37 +0100
Francesco Allertsen <fallertsen@gmail.com> wrote:

> On Thu, Feb 10, 2011 at 03:25:33PM -0800, Jesse Barnes wrote:
> > Does this kernel have the problem patch included?  Or is it reverted?
> 
> That was without the patch reverted, now I've reverted it and this is
> the output:
> 
> ---
> HD boost: yes
> Boost freq: 3
> HW control enabled: no
> SW control enabled: yes
> Gated voltage change: no
> Starting frequency: P9
> Max P-state: P0
> Min P-state: P9
> RS1 VID: 0
> RS2 VID: 8
> Render standby enabled: yes
> Current RS state: RS2 (RC6)
> RSTDBYCTL: 0x474c3000
> ---
> 
> It seems the same.

Interesting, so your RSTDBYCTL is the same and you're still in RC6.  So
something else in the cleanup patch is causing trouble.

Francesco, if you revert d5bb081b027b520f9e59b4fb8faea83a136ec15e do
both the hangs at X startup and suspend/resume go away?

Gui, same question for you.  And can you try this patch and dump
the contents of /sys/kernel/debug/dri/0/i915_drpc_info as well?  Your
settings are probably the same but I want to double check.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2011-02-11 17:16 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
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 [this message]
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=20110211091633.1c63fa46@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=chaos.proton@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox