All of lore.kernel.org
 help / color / mirror / Atom feed
From: "justinmattock@gmail.com" <justinmattock@gmail.com>
To: "Daniel Vetter" <daniel@ffwll.ch>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Date: Tue, 23 Oct 2012 11:15:32 -0700	[thread overview]
Message-ID: <5086dec3.c855420a.2496.ffffc3aa@mx.google.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2040 bytes --]

Sure.. seems this error is happening frequently to gather the debug info(will send out as soon as it hits). As for the bisect it is doable when I get the time. Just need a reliable recreation of the error so the bisect is correct.

Justin P. Mattock

----- Reply message -----
From: "Daniel Vetter" <daniel@ffwll.ch>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Date: Tue, Oct 23, 2012 10:40 am


On Tue, Oct 23, 2012 at 10:06:52AM -0700, Justin P. Mattock wrote:
> This is happening both with MAINLINE and NEXT.
> 
> basically system is running fine, then under load system becomes
> really sluggish and unresponsive. I was able to get dmesg of the
> error..:
> 
> [ 7745.007008] ath9k 0000:05:00.0 wlan0: disabling VHT as WMM/QoS is
> not supported by the AP
> [ 7745.007736] wlan0: associate with 68:7f:74:b8:05:82 (try 1/3)
> [ 7745.011456] wlan0: RX AssocResp from 68:7f:74:b8:05:82
> (capab=0x411 status=0 aid=5)
> [ 7745.011529] wlan0: associated
> [ 8120.812482] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer
> elapsed... GPU hung
> [ 8120.812642] [drm] capturing error event; look for more
> information in /debug/dri/0/i915_error_state
> [ 8122.328682] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer
> elapsed... GPU hung
> [ 8122.328845] [drm:i915_reset] *ERROR* GPU hanging too fast,
> declaring wedged!
> [ 8122.328850] [drm:i915_reset] *ERROR* Failed to reset chip.
> 
> full log is here: http://fpaste.org/7xH8/
> 
> as for good kernels from what I remember 3.6.0-rc1. I can try a
> bisect on this once I get the time. or if anybody has a patch I can
> test.

Can you please rehand your machine, and then grab the i915_error_state
from debugfs? That contains the gpu hang dump we need to diagnose things.

And the bisect would obviously be awesome.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

[-- Attachment #1.2: Type: text/html, Size: 2318 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2012-10-23 18:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 18:15 justinmattock [this message]
     [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
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
  -- 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=5086dec3.c855420a.2496.ffffc3aa@mx.google.com \
    --to=justinmattock@gmail.com \
    --cc=daniel@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 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.