From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: wzab@ise.pw.edu.pl
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: i915 drm GPU hung errors with kernel 2.6.38.2 on 82865G chipset
Date: Fri, 15 Apr 2011 23:50:15 +0200 [thread overview]
Message-ID: <20110415235015.1e315688@neptune.home> (raw)
In-Reply-To: <4DA8B3A7.3010807@ise.pw.edu.pl>
Hi Wojtek,
Your best chance to see the bugs fixed is to report a bug following
guidelines at http://intellinuxgraphics.org/how_to_report_bug.html
For GPU hangs, collecting the error state (while GPU is hung) under
debugfs is very helpful.
Report contents of (as well as details on your software stack and
if know what kind of action triggered the hung):
/sys/kernel/debug/dri/0/i915_error_state
Also you should CC intel-gfx@lists.freedesktop.org and Chris Wilson
<chris@chris-wilson.co.uk> for all issues regarding intel GPUs as
thats the place it has better chance of being seen by someone who
can help out. (intel-gfx is subscribers-only but at least part of the
thread would reach it)
Regards,
Bruno
On Fri, 15 April 2011 wzab <wzab@ise.pw.edu.pl> wrote:
> Today I have experienced two "GPU hungs" on machine with 82865G chipset
> working with 2.6.38.2 kernel
> In the /var/log/syslog I have found the following errors:
>
> Apr 15 22:50:51 wzab kernel: [drm:i915_hangcheck_elapsed] *ERROR*
> Hangcheck timer elapsed... GPU hung
> Apr 15 22:50:51 wzab kernel: [drm:i915_do_wait_request] *ERROR*
> i915_do_wait_request returns -11 (awaiting 1352947 at 1352942, next 1352948)
> Apr 15 22:50:51 wzab kernel: [drm:init_ring_common] *ERROR* failed to
> set render ring head to zero ctl 00000000 head 3280a54c tail 00000000
> start 00000000
> Apr 15 22:50:51 wzab kernel: [drm:init_ring_common] *ERROR* render ring
> initialization failed ctl 0001f003 head 3280a54c tail 00000000 start
> 00000000
> Apr 15 22:50:52 wzab kernel: [drm:i915_hangcheck_elapsed] *ERROR*
> Hangcheck timer elapsed... GPU hung
> Apr 15 22:50:52 wzab kernel: [drm:i915_do_wait_request] *ERROR*
> i915_do_wait_request returns -11 (awaiting 1353049 at 1352942, next 1353050)
>
> After reboot:
>
> Apr 15 22:56:41 wzab kernel: [drm:i915_hangcheck_elapsed] *ERROR*
> Hangcheck timer elapsed... GPU hung
> Apr 15 22:56:41 wzab kernel: [drm:i915_do_wait_request] *ERROR*
> i915_do_wait_request returns -11 (awaiting 29134 at 29129, next 29135)
>
next prev parent reply other threads:[~2011-04-15 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 21:07 wzab
2011-04-15 21:38 ` Sitsofe Wheeler
2011-04-15 21:50 ` Bruno Prémont [this message]
2011-04-16 6:07 ` Chris Wilson
2011-04-16 12:52 ` wzab
2011-04-16 9:26 Martin
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=20110415235015.1e315688@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wzab@ise.pw.edu.pl \
/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
all inboxes | Powered by JetHome®