From: Jiri Slaby <jirislaby@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Jiri Slaby <jslaby@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, daniel@ffwll.ch
Subject: new GPU hang [was: g33: GPU hangs]
Date: Tue, 24 Jan 2012 15:51:26 +0100 [thread overview]
Message-ID: <4F1EC56E.6040608@gmail.com> (raw)
In-Reply-To: <20120118114308.GA4002@phenom.ffwll.local>
On 01/18/2012 12:43 PM, Daniel Vetter wrote:
>>> From 2b76187d2f5fc2352e391914b1828f91f93bb356 Mon Sep 17 00:00:00 2001
>>> From: Chris Wilson <chris@chris-wilson.co.uk>
>>> Date: Tue, 29 Nov 2011 15:12:16 +0000
>>> Subject: [PATCH] drm/i915: Only clear the GPU domains upon a successful
>>> finish
>>
>> Hi, do you plan to push this patch upstream? Or am I supposed to not use
>> it anymore?
>
> It's on track to get merged to drm-intel-next. I'll probably pick it up in a week
> or so.
OK, thanks.
Even though I use the patch, today another hang occurred:
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
[drm] capturing error event; look for more information in
/debug/dri/0/i915_error_state
[drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting
910502 at 910475, next 910519)
[drm:i915_reset] *ERROR* Failed to reset chip.
I was cruising through a map at openstreetmaps.org. This was
3.2.0-next-20120118_64+. FWIW I updated to 3.3.0-rc1-next-20120124_64+
right now.
Is it related to the bug I reported at:
https://bugs.freedesktop.org/show_bug.cgi?id=43427
?
dmesg:
http://www.fi.muni.cz/~xslaby/sklad/panics/915_error_state.dmesg
error_state:
http://www.fi.muni.cz/~xslaby/sklad/panics/915_error_state
thanks,
--
js
prev parent reply other threads:[~2012-01-24 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 12:30 g33: GPU hangs Jiri Slaby
2011-12-01 12:47 ` Chris Wilson
2011-12-03 22:58 ` Jiri Slaby
2012-01-18 9:31 ` Jiri Slaby
2012-01-18 11:43 ` Daniel Vetter
2012-01-24 14:51 ` Jiri Slaby [this message]
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=4F1EC56E.6040608@gmail.com \
--to=jirislaby@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jslaby@suse.cz \
--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