From: Greg KH <gregkh@linuxfoundation.org>
To: Chris Wilson <chris@chris-wilson.co.uk>, daniel.vetter@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: i915_hangcheck_hung problem with 3.8-rc2+ (Linus's latest tree)
Date: Tue, 8 Jan 2013 16:38:24 -0800 [thread overview]
Message-ID: <20130109003824.GA21075@kroah.com> (raw)
In-Reply-To: <20130108223611.GA19672@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Tue, Jan 08, 2013 at 02:36:11PM -0800, Greg KH wrote:
> Hi all,
>
> I've hit this 3 times today on Linus's latest 3.8-rc2+ tree:
>
> [11868.414648] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
> [11868.414655] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
> [11870.408342] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
> [11870.408412] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
> [11870.408414] [drm:i915_reset] *ERROR* Failed to reset chip.
> [11883.083225] gnome-shell[19396]: segfault at 218 ip 00007feef5f32333 sp 00007ffffc1dc930 error 4 in i965_dri.so[7feef5ecb000+d0000]
I just hit this again. And, as the kernel was asking for it, attached
is the i915_error_state file, compressed due to the size of it.
thanks,
greg k-h
[-- Attachment #2: i915_error_state.gz --]
[-- Type: application/x-gzip, Size: 200230 bytes --]
next prev parent reply other threads:[~2013-01-09 0:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 22:36 i915_hangcheck_hung problem with 3.8-rc2+ (Linus's latest tree) Greg KH
2013-01-09 0:38 ` Greg KH [this message]
2013-01-09 3:42 ` Dave Airlie
2013-01-09 4:25 ` Greg KH
2013-01-09 5:31 ` Dave Airlie
2013-01-09 7:28 ` Lijo Antony
2013-01-09 19:44 ` Dave Kleikamp
2013-01-09 20:12 ` Dave Kleikamp
2013-01-09 21:08 ` Greg KH
2013-01-10 0:40 ` Greg KH
2013-01-10 1:07 ` Chris Wilson
2013-01-10 1:19 ` Dave Airlie
2013-01-11 17:26 ` Nikola Pajkovsky
2013-01-11 18:42 ` Daniel Vetter
2013-01-14 6:58 ` Nikola Pajkovsky
2013-01-14 9:06 ` Daniel Vetter
2013-01-14 9:49 ` Nikola Pajkovsky
2013-01-14 12:47 ` Chris Wilson
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=20130109003824.GA21075@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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