dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Allertsen <fallertsen@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	David Airlie <airlied@linux.ie>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Intel i915 freeze on latest git
Date: Tue, 1 Feb 2011 12:22:02 +0100	[thread overview]
Message-ID: <20110201112200.GA2349@fujiko> (raw)

Hi Chris and all,

I have tried the latest git (-rc3) and I get a complete freeze when X
starts.

I've bisected it and the first bad commit is this:

commit d5bb081b027b520f9e59b4fb8faea83a136ec15e
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Wed Jan 5 12:01:26 2011 -0800

    drm/i915: cleanup rc6 code
    
    Cleanup several aspects of the rc6 code:
      - misnamed intel_disable_clock_gating function (was only about rc6)
      - remove commented call to intel_disable_clock_gating
      - rc6 enabling code belongs in its own function (allows us to move the
        actual clock gating enable call back into restore_state)
      - allocate power & render contexts up front, only free on unload
        (avoids ugly lazy init at rc6 enable time)
    
    Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
    [ickle: checkpatch cleanup]
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

I've tried to revert it on top of -rc3 and everything works great.

I don't know which part of the code is wrong, could you please check it?
If you need more information just ask.

Thanks.

Bye
Francesco

             reply	other threads:[~2011-02-01 11:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 11:22 Francesco Allertsen [this message]
2011-02-01 12:05 ` Intel i915 freeze on latest git 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
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=20110201112200.GA2349@fujiko \
    --to=fallertsen@gmail.com \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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