From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>,
"Justin P. Mattock" <justinmattock@gmail.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Date: Thu, 25 Oct 2012 09:47:29 +0100 [thread overview]
Message-ID: <84c8a8$68qvdl@orsmga001.jf.intel.com> (raw)
In-Reply-To: <CAKMK7uFMaf=ohEKyWKNsd-mSQkW__0BUww_iYLNFo347mEYAMg@mail.gmail.com>
On Thu, 25 Oct 2012 10:16:08 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, Oct 25, 2012 at 7:22 AM, Justin P. Mattock
> <justinmattock@gmail.com> wrote:
> >
> > here is a link to the file..: intel_error_decode
> > http://www.filefactory.com/file/22bypyjhs4mx
>
> I haven't figured out how to access this thing. Can you please file a
> bug report on bugs.freedesktop.org and attach it there?
No worries, it is another ILK hang similar to the ones reported earlier
- it just seems the ring stops advancing. Hopefully it is a missing w/a
from http://cgit.freedesktop.org/~danvet/drm/log/?h=ilk-wa-pile
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-10-25 8:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2b9aabdc-6f44-40cc-ad0b-4180101570c7@mail.android.htc.com>
2012-10-25 5:22 ` [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung Justin P. Mattock
2012-10-25 8:16 ` Daniel Vetter
2012-10-25 8:47 ` Chris Wilson [this message]
2012-10-26 4:43 ` Justin P. Mattock
2012-10-26 8:05 ` Daniel Vetter
2012-10-26 17:35 ` Justin P. Mattock
2012-10-26 20:57 ` Justin P. Mattock
2012-10-27 13:56 ` Daniel Vetter
2012-10-27 13:56 ` Daniel Vetter
2012-10-27 19:11 ` Justin P. Mattock
2012-10-23 18:15 justinmattock
-- strict thread matches above, loose matches on Subject: below --
2012-10-23 17:06 Justin P. Mattock
2012-10-23 17:06 ` Justin P. Mattock
2012-10-23 17:40 ` Daniel Vetter
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='84c8a8$68qvdl@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=justinmattock@gmail.com \
--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 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.