public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ted Phelps <phelps@gnusto.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Pekka Enberg <penberg@kernel.org>,
	Gu Rui <chaos.proton@gmail.com>,
	intel-gfx@lists.freedesktop.org,
	Francesco Allertsen <fallertsen@gmail.com>
Subject: Re: [PATCH] drm/i915: Try enabling RC6 by default (again)
Date: Fri, 05 Aug 2011 11:41:09 +1000	[thread overview]
Message-ID: <30203.1312508469@orpheus.gnusto.com> (raw)
In-Reply-To: Your message of Thu, 04 Aug 2011 17:51:44 +0200. <CAKMK7uFt2foTnOhrWs36tQyECDQJGwppEae2TGV=4Y0TdYMSMA@mail.gmail.com>

Daniel Vetter writes:
> On Thu, Aug 4, 2011 at 16:05, Ted Phelps <phelps@gnusto.com> wrote:
> > I saw a bunch of stack traces like the one below, alternating between
> > ring_put and ring_get, before the GPU was declared wedged.
> 
> How much time happens between the first wait_for_fifo backtrace and
> the final gpu hang report?

About 6 seconds.  All 20 ring_put/ring_get failures happen in the same
second, then there's a 4 second pause before the GPU is first declared
hung, and another couple of seconds before the GPU is declared wedged:

Aug  4 23:37:02 orpheus kernel: ------------[ cut here ]------------
...
Aug  4 23:37:06 orpheus kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
...
Aug  4 23:37:08 orpheus kernel: [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
Aug  4 23:37:08 orpheus kernel: [drm:i915_reset] *ERROR* Failed to reset chip.


> If it's short (order of a second or less) can you rehang your gpu with
> kernel log timestamping switched on?

I'm happy to re-hang the GPU with kernel log timestamping enabled, but I
won't be able to do so until Sunday night.

Cheers,
-Ted

  reply	other threads:[~2011-08-05  1:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04  3:23 [PATCH] drm/i915: Try enabling RC6 by default (again) Keith Packard
2011-08-04 14:05 ` Ted Phelps
2011-08-04 15:51   ` Daniel Vetter
2011-08-05  1:41     ` Ted Phelps [this message]
2011-08-08  3:44       ` Ted Phelps
     [not found] ` <20110804051027.GA3176@fujiko>
2011-08-04 18:05   ` Keith Packard
2011-08-05  4:54     ` Francesco Allertsen
     [not found]   ` <CALC6sNDujob+qGu40pDMBVXo8K752-MsN4Y9KNkTvmd3bD3DHg@mail.gmail.com>
2011-08-04 18:08     ` Keith Packard

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=30203.1312508469@orpheus.gnusto.com \
    --to=phelps@gnusto.com \
    --cc=chaos.proton@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=fallertsen@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=penberg@kernel.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