All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: Norbert Preining <preining@logic.at>
Subject: Re: drm i915 hangs on heavy io load
Date: Tue, 23 Oct 2012 10:17:48 +0100	[thread overview]
Message-ID: <6c3329$6sai31@orsmga002.jf.intel.com> (raw)
In-Reply-To: <20121023053830.GA30776@gamma.logic.tuwien.ac.at>

On Tue, 23 Oct 2012 14:38:30 +0900, Norbert Preining <preining@logic.at> wrote:
> Hi everyone,
> 
> (please Cc)
> 
> I am running 3.7-rc2 and got recently hit a few times (under rc1, too)
> by hanging drm i915 while doing large io operations.
[snip]
> 
> I captured the i915_error_state and uploaded it here:
> 	http://www.logic.at/people/preining/drm_i915_error_state.gz
> 
> The hangs have been normally initiated on svn up in a very big
> repository, or git checkout on a very big repository or so.
> 
> Other system is Debian/unstable. The above output and error state is
> from after a reboot without any suspends or other tricks inbetween,
> uptime 3.5h.

Looks like fallout from a missing ILK rc6 workaround - it looks like the
write to the ring tail never landed and so the command streamer hung.

See https://bugs.freedesktop.org/show_bug.cgi?id=55984 and
http://cgit.freedesktop.org/~danvet/drm/log/?h=ilk-wa-pile of which I
think
http://cgit.freedesktop.org/~danvet/drm/commit/?h=ilk-wa-pile&id=0d5fed2de763b49bb1a90140758153481f043757
is the missing ingredient.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  parent reply	other threads:[~2012-10-23  9:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  5:38 drm i915 hangs on heavy io load Norbert Preining
2012-10-23  6:56 ` Dave Airlie
2012-10-23  7:24   ` Norbert Preining
2012-10-24  0:36   ` Norbert Preining
2012-10-24  8:11     ` Chris Wilson
2012-10-24  8:11       ` Chris Wilson
2012-10-28  2:47       ` Norbert Preining
2012-10-28 11:10         ` Chris Wilson
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  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  6:56 ` Dave Airlie
2012-10-23  6:56 ` Dave Airlie
2012-10-23  9:17 ` Chris Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-23  5:38 Norbert Preining
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='6c3329$6sai31@orsmga002.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.