From: Ted Phelps Subject: On SNB: Hangcheck timer elapsed... GPU hung Date: Mon, 14 Feb 2011 23:18:53 +1000 Message-ID: <201102141318.p1EDIr2l006067@gnusto.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from laika.gnusto.com (laika.gnusto.com [207.44.178.75]) by gabe.freedesktop.org (Postfix) with ESMTP id DCC499E772 for ; Mon, 14 Feb 2011 05:38:05 -0800 (PST) Received: from gnusto.com (orpheus.ipv6.gnusto.com [IPv6:2001:44b8:72d8:1a0:201:2ff:fe8f:d6a4]) by laika.gnusto.com (8.14.3/8.14.3) with ESMTP id p1EDIurP010709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 Feb 2011 07:18:59 -0600 Received: from orpheus.gnusto.com (localhost [127.0.0.1]) by gnusto.com (8.14.4/8.14.4) with ESMTP id p1EDIr2l006067 for ; Mon, 14 Feb 2011 23:18:54 +1000 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org Apologies if this is a known issue, but I haven't been able to convince myself that someone is looking after it. I've been seeing this issue with Linux kernel 2.6.37, 2.6.38-rc4 and the most recent merge of Linus's git tree and drm-intel-fixes. I'm happy to provide more information, apply patches, run tools, read code, as requested. I have a Core i7 2600K CPU (yay me!) on a DH67CL motherboard, and I'm trying to use the on-board graphics. Typically this set-up works well for about 10-30 minutes. Then I get an error of the form: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung after which, my cursor no longer changes shape, anti-aliased fonts misbehave (mostly they just aren't't rendered) and 3-D applications no longer start up. I haven't found any obvious trigger for this -- I don't need to be interacting with the machine for it to happen -- but it happens pretty reliably. I've just now managed to catch this with the drm.debug parameter set to 7. Things seem ok initially... ... various cmd/nr/dev/auth entries logged ... Feb 14 22:47:50 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0xc010645b, nr=0x5b, dev 0xe200, auth=1 Feb 14 22:47:50 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0x400c645f, nr=0x5f, dev 0xe200, auth=1 Then there's this worrying-looking message: Feb 14 22:47:50 orpheus kernel: [drm:intel_prepare_page_flip], preparing flip with no unpin work? Feb 14 22:47:50 orpheus kernel: [drm:drm_ioctl], ret = fffffe00 The cmd/nr/dev/auth fields are then repeated for a couple of seconds: Feb 14 22:47:50 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0x400c645f, nr=0x5f, dev 0xe200, auth=1 Feb 14 22:47:50 orpheus kernel: [drm:drm_ioctl], ret = fffffe00 Feb 14 22:47:50 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0x400c645f, nr=0x5f, dev 0xe200, auth=1 Feb 14 22:47:50 orpheus kernel: [drm:drm_ioctl], ret = fffffe00 Feb 14 22:47:50 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0x400c645f, nr=0x5f, dev 0xe200, auth=1 Feb 14 22:47:50 orpheus kernel: [drm:drm_ioctl], ret = fffffe00 ... repeat many, many times ... Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0x400c645f, nr=0x5f, dev 0xe200, auth=1 Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], ret = fffffe00 Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0x400c645f, nr=0x5f, dev 0xe200, auth=1 And finally, the hangcheck timer expires: Feb 14 22:47:52 orpheus kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], ret = fffffe00 Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0x400c645f, nr=0x5f, dev 0xe200, auth=1 Feb 14 22:47:52 orpheus kernel: [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 300039 at 300025, next 300040) Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], ret = fffffff5 Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0x400c645f, nr=0x5f, dev 0xe200, auth=1 Feb 14 22:47:52 orpheus kernel: [drm:i915_error_work_func], resetting chip Feb 14 22:47:52 orpheus kernel: [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged! Feb 14 22:47:52 orpheus kernel: [drm:i915_reset] *ERROR* Failed to reset chip. Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], ret = fffffffb Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], pid=2180, cmd=0x4020645d, nr=0x5d, dev 0xe200, auth=1 Feb 14 22:47:52 orpheus kernel: [drm:drm_ioctl], ret = fffffffb After that, the system limps along as described above. I haven't delved into trying to understand what this means; I'm hoping that the above trace rings bells for someone. I can provide a more complete log if someone reckons that'd be useful. Thanks for your time! -Ted