[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130108223611.GA19672@kroah.com>
Date: Tue, 8 Jan 2013 14:36:11 -0800
From: Greg KH <gregkh@...uxfoundation.org>
To: Chris Wilson <chris@...is-wilson.co.uk>, daniel.vetter@...ll.ch
Cc: intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: i915_hangcheck_hung problem with 3.8-rc2+ (Linus's latest tree)
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]
When it happens, gnome-shell dies a horrible death and it requires a
reboot in order to get xorg working properly again (probably because
gnome-shell is hosed.)
The machine does still work to do other things from a text console (I'm
writing this on the machine after the last time this happened.)
It seems to happen when doing a "stressful" thing on the machine (i.e.
multiple kernel builds at the same time).
I also seem to be able to hit this on 3.7.1, but not as regularly, and
not at all on 3.6.y.
Any hints or ideas of what to try out?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists