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: dri-devel@lists.freedesktop.org
Subject: Re: Intel i915 freeze on latest git
Date: Tue, 1 Feb 2011 08:31:12 -0800	[thread overview]
Message-ID: <20110201083112.3cfefc3a@jbarnes-desktop> (raw)
In-Reply-To: <20110201140754.GA2229@fujiko>

On Tue, 1 Feb 2011 15:07:55 +0100
Francesco Allertsen <fallertsen@gmail.com> wrote:

> On Tue, Feb 01, 2011 at 01:16:01PM +0000, Chris Wilson wrote:
> > Useful for me. Just confirms that you have an equivalent machine to
> > this Lenovo x201s, on which those patches were tested after receiving
> > from Jesse. :|
> 
> Yes, I have a Lenovo x201s :-P.
> 
> > The dmesg would have been useful to know whether the i915.ko module is
> > loaded during X startup, and so reveal some information about the sequence
> > of function calls (i.e. whether the modified routines were running at the
> > time of the hang, or whether they had completed much earlier during boot).
> > The drm.debug dmesg is usually a gold mine of information.
> 
> Attacched there is the full dmesg log.
> 
> > Another useful test is whether i915.powersave=0 also prevents the hang?
> 
> No, it doesn't have any effect.

Yeah I don't think we use that flag for rc6, though we probably should.

The bisect is interesting, I'd have expected a failure when we
re-enabled rc6 on ILK or when we fixed up the ring buffer init.

The cleanup patch should be just that, but at least reverting it
shouldn't cause any trouble.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2011-02-01 16:31 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 [this message]
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=20110201083112.3cfefc3a@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --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