dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Norbert Preining <preining@logic.at>
Cc: Dave Airlie <airlied@gmail.com>,
	linux-kernel@vger.kernel.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org
Subject: Re: drm i915 hangs on heavy io load
Date: Sun, 28 Oct 2012 11:10:12 +0000	[thread overview]
Message-ID: <eeac1e$4q1mqm@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <20121028024753.GA4254@gamma.logic.tuwien.ac.at>

On Sun, 28 Oct 2012 11:47:53 +0900, Norbert Preining <preining@logic.at> wrote:
> I pulled the whole branch into my compile branch, and removed everything
> from kernel cmd line regarding rc6, and got the
> 	[drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
> 	[drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
> 	[drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
> 	[drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
> 	[drm:i915_reset] *ERROR* Failed to reset chip.
> new i915_error_state.gz at the same place.
> 
> So it seems that the patches in the ilk-wa-pile branch do not help.

Yeah, looks like we have another issue to contend with, so can you
please file a bug on bugzilla.freedesktop.org (or bugzilla.kernel.org)
so that we don't lose track of it.

If your have the option, can you switch the ddx between using SNA and
UXA. They stress different paths through the driver which may provide a
lue. Thanks,
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-10-28 11:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121023053830.GA30776@gamma.logic.tuwien.ac.at>
2012-10-23  6:56 ` drm i915 hangs on heavy io load Dave Airlie
2012-10-23  6:56 ` Dave Airlie
2012-10-23  9:17 ` Chris Wilson
     [not found] ` <CAPM=9txr4TzuG-BbL0bXeEK6AzkOK9pH0kh-nP=Njv53sgFZew@mail.gmail.com>
2012-10-23  7:24   ` Norbert Preining
2012-10-24  0:36   ` Norbert Preining
2012-10-24  8:11     ` Chris Wilson
2012-10-28  2:47       ` Norbert Preining
2012-10-28 11:10         ` Chris Wilson [this message]
2012-10-28 12:32           ` Norbert Preining
2012-10-29  7:17             ` Tino Keitel
2012-10-30  0:49               ` Norbert Preining
2012-10-30  0:55                 ` Dave Airlie
2012-10-30  1:01                   ` Norbert Preining
2012-10-30  1:37                     ` Ben Widawsky
2012-10-30  3:13                       ` Norbert Preining
2012-11-04  0:44                   ` Norbert Preining
2012-11-04  6:08                     ` Dave Airlie
2012-11-05  0:33                       ` Norbert Preining
2012-11-05 20:29                       ` [bisected] " Lekensteyn
2012-10-30  0:39           ` Norbert Preining
2012-10-30 10:02             ` Chris Wilson
2012-10-23  5:38 Norbert Preining
  -- strict thread matches above, loose matches on Subject: below --
2012-10-23  5:38 Norbert Preining
2012-10-23  5:38 Norbert Preining

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='eeac1e$4q1mqm@AZSMGA002.ch.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preining@logic.at \
    /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;
as well as URLs for NNTP newsgroup(s).