From: Norbert Preining <preining@logic.at>
To: Chris Wilson <chris@chris-wilson.co.uk>
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: Tue, 30 Oct 2012 09:39:43 +0900 [thread overview]
Message-ID: <20121030003942.GC6539@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <eeac1e$4q1mqm@AZSMGA002.ch.intel.com>
Hi Chris,
On So, 28 Okt 2012, Chris Wilson 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.
I have seen this here:
https://bugs.freedesktop.org/show_bug.cgi?id=55984
does it make sense to start a new bug for that?
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
SCREMBY (n.)
The dehydrated felt-tip pen attached by a string to the 'Don't Forget'
board in the kitchen which has never worked in living memory but which
no one can be bothered to throw away.
--- Douglas Adams, The Meaning of Liff
next prev parent reply other threads:[~2012-10-30 0:39 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
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 [this message]
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=20121030003942.GC6539@gamma.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).