From: Lijo Antony <lijo.kernel@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
daniel.vetter@ffwll.ch, 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: Wed, 09 Jan 2013 11:28:18 +0400 [thread overview]
Message-ID: <50ED1C12.2090608@gmail.com> (raw)
In-Reply-To: <CAPM=9tyB4aKK2Z3-h9yEXLWvrnKGjxH2DaOHp8uA0mNNZQiVWQ@mail.gmail.com>
On 01/09/2013 09:31 AM, Dave Airlie wrote:
> On Wed, Jan 9, 2013 at 2:25 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>> On Wed, Jan 09, 2013 at 01:42:39PM +1000, Dave Airlie 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.
>>>>
>>> Welcome to sink hole that is
>>> https://bugs.freedesktop.org/show_bug.cgi?id=55984
>>>
>>> 3 months and ticking, Intel guys are all running away from it saying
>>> they can't reproduce, everyone else on planet seems to reproduce quite
>>> easily.
>>>
>>> Its generally considered a bug in the relocation/shrinker/no idea category,
>>
>> Ugh, what a mess.
>>
>>> Assuming you have an Ironlake machine which I'm going to guess you do.
>>
>> I don't know, it's an old i5 machine that has never had any video
>> problems for many years now. How do I tell?
>
> lspci -nn probably an 8086:0046 device.
>
> Old i5 probably means original i5 which means ironlake.
>
I have also seen this a couple of times on 3.7 and 3.8-rc1.
Most of the times I was watching youtube video in chrome. Nothing
crashed though(I am not running gnome shell). System recovered after few
seconds.
I didn't see this on 3.8-rc2 yet, probably because I haven't watched any
video.
-lijo
next prev parent reply other threads:[~2013-01-09 7:28 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
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 [this message]
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=50ED1C12.2090608@gmail.com \
--to=lijo.kernel@gmail.com \
--cc=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--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