From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757219Ab3AIEZG (ORCPT ); Tue, 8 Jan 2013 23:25:06 -0500 Received: from mail-pa0-f47.google.com ([209.85.220.47]:36979 "EHLO mail-pa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756568Ab3AIEZF (ORCPT ); Tue, 8 Jan 2013 23:25:05 -0500 Date: Tue, 8 Jan 2013 20:25:33 -0800 From: Greg KH To: Dave Airlie Cc: Chris Wilson , daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, Jesse Barnes Subject: Re: i915_hangcheck_hung problem with 3.8-rc2+ (Linus's latest tree) Message-ID: <20130109042533.GA9164@kroah.com> References: <20130108223611.GA19672@kroah.com> <20130109003824.GA21075@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? thanks, greg k-h