dri-devel Archive on 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: Tue, 01 Feb 2011 13:16:01 +0000	[thread overview]
Message-ID: <b9dded$hqm5n7@orsmga002.jf.intel.com> (raw)
In-Reply-To: <20110201122943.GA2011@fujiko>

On Tue, 1 Feb 2011 13:29:45 +0100, Francesco Allertsen <fallertsen@gmail.com> wrote:
> On Tue, Feb 01, 2011 at 12:05:52PM +0000, Chris Wilson wrote:
> > It would be useful to give us a few more details, such the drm.debug=0xe
> > dmesg and the Xorg.log (from when it does starts!), and explain what you
> > mean by complete freeze? Such as is the machine still accessible over the
> > network, did it die whilst oopsing, etc.
> 
> I've tried to use netconsole to get the output of dmesg, but there is
> no output.
> 
> Attached there is the Xorg.log, but I don't see any useful infomation.

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. :|

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.

Another useful test is whether i915.powersave=0 also prevents the hang?
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2011-02-01 13: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 [this message]
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='b9dded$hqm5n7@orsmga002.jf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox