From: Andrew Morton <akpm@linux-foundation.org>
To: Paolo Ornati <ornati@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [2.6.38-rc6] G965: i915 Hangcheck timer elapsed... GPU hung (not reproducible)
Date: Wed, 2 Mar 2011 15:56:48 -0800 [thread overview]
Message-ID: <20110302155648.421f0292.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110227101041.6b864352@gmail.com>
(cc dri-devel)
A post-2.6.37 regression.
On Sun, 27 Feb 2011 10:10:41 +0100
Paolo Ornati <ornati@gmail.com> wrote:
> Today I got this while starting a video in SMplayer (MPlayer) with
> 2.6.38-rc6-00113-g4662db4:
>
> [ 830.880014] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> [ 830.880736] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 174895 at 174857, next 174896)
> [ 830.881093] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 00000000 head 00000000 tail 00000000 start 00000000
> [ 831.379079] [drm:i915_do_wait_request] *ERROR* something (likely vbetool) disabled interrupts, re-enabling
> [ 831.399099] [drm:i915_do_wait_request] *ERROR* something (likely vbetool) disabled interrupts, re-enabling
> ...
> [ 837.392012] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> [ 837.392038] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 175016 at 174857, next 175022)
> [ 837.392491] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 00000000 head 00000000 tail 00000000 start 00000000
> [ 837.537479] [drm:i915_do_wait_request] *ERROR* something (likely vbetool) disabled interrupts, re-enabling
> [ 837.543285] [drm:i915_do_wait_request] *ERROR* something (likely vbetool) disabled interrupts, re-enabling
> ...
> [ 839.040011] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> [ 839.040034] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 175022 at 174857, next 175122)
> [ 839.040364] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
> [ 839.040367] [drm:i915_reset] *ERROR* Failed to reset chip.
>
> Screen was almost freezed, cursor was stuck but the machine was alive
> and I was able to use SysRq to kill X and try to restart it (but that
> didn't help).
>
> I don't remember anything similar in recent kernels (<= 2.6.37) and got
> this only once with 2.6.38-rcX.
>
> Environment at the time of the GPU crash:
> KDE4 (without "Desktop Effects")
> Chromium
> Claws Mail
> Dolphin
> ccached make -j3 on a just pulled linux-tree (so I/O bound)
> SMPlayer/Mplayer (just launched)
>
> Assorted logs attached.
>
next prev parent reply other threads:[~2011-03-02 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 9:10 [2.6.38-rc6] G965: i915 Hangcheck timer elapsed... GPU hung (not reproducible) Paolo Ornati
2011-03-02 23:56 ` Andrew Morton [this message]
2011-03-03 0:43 ` Nick Bowler
2011-03-03 20:01 ` Paolo Ornati
2011-03-14 19:20 ` Paolo Ornati
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=20110302155648.421f0292.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@gmail.com \
/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