From: Chris Wilson <chris@chris-wilson.co.uk>
To: Stephen Clark <sclark46@earthlink.net>, sclark46@earthlink.net
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: I915 driver locks up
Date: Sat, 18 Dec 2010 21:40:00 +0000 [thread overview]
Message-ID: <5b55a1$j0av6h@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <4D0D19FF.4020600@earthlink.net>
On Sat, 18 Dec 2010 15:30:55 -0500, Stephen Clark <sclark46@earthlink.net> wrote:
> On 12/18/2010 03:09 PM, Stephen Clark wrote:
> > Hi,
> >
> > I am using 2.6.35.9-64.fc14.x86_64 running 1.3.9-1.fc14.x86_64
> > and am having my 945gma lock up in texture decompress according
> > to intel_gpu_top utility, when trying to play Myst 5.
> >
> > Any fixes on the horizon?
> >
> Additional data point with 2.6.37-0.rc6.git0.1.fc15.x86_64 from rawhide
> I get:
> [ 307.256028] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
> elapsed... GPU hung
> [ 307.258118] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request
> returns -11 (awaiting 27197 at 27195, next 27199)
> [ 307.258975] [drm:i915_reset] *ERROR* Failed to reset chip.
>
> and my X screen goes weird - have to switch to vty console.
Judging by your description, you've hit a bug in Mesa. Please verify the
bug with the current stable release (of Mesa) and file a bug report, and
be sure to include /sys/kernel/debug/dri/0/i915_error_state for the hang.
Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-12-18 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 20:09 Stephen Clark
2010-12-18 20:30 ` Stephen Clark
2010-12-18 21:40 ` Chris Wilson [this message]
2010-12-18 23:32 ` Stephen Clark
2010-12-19 11:02 ` Chris Wilson
2010-12-19 21:46 ` Stephen Clark
2010-12-21 16:16 ` Stephen Clark
2010-12-22 19:40 ` Stephen Clark
2010-12-22 19:49 ` 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='5b55a1$j0av6h@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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
Powered by JetHome