From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: maciej.rutecki@gmail.com
Cc: linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org,
bjorn.helgaas@hp.com, airlied@linux.ie,
Eric Anholt <eric@anholt.net>
Subject: Re: [Regresion] [2.6.34-rc1] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Date: Thu, 25 Mar 2010 21:37:12 +0100 [thread overview]
Message-ID: <201003252137.12278.rjw@sisk.pl> (raw)
In-Reply-To: <201003252104.24965.maciej.rutecki@gmail.com>
[More CCs]
On Thursday 25 March 2010, Maciej Rutecki wrote:
> Last known good: 2.6.33
> Failing kernels: 2.6.34-rc1 and 2.6.34-rc2
> Driver: Video(DRI - Intel)
>
>
> When XWindow starts I got:
> Mar 25 19:58:10 gumis kernel: [ 133.624028] [drm:i915_hangcheck_elapsed]
> *ERROR* Hangcheck timer elapsed... GPU hung
> Mar 25 19:58:10 gumis kernel: [ 133.624221] render error detected, EIR:
> 0x00000000
> Mar 25 19:58:10 gumis kernel: [ 133.624291] [drm:i915_do_wait_request]
> *ERROR* i915_do_wait_request returns -5 ( awaiting 691 at 682)
> Mar 25 19:58:11 gumis kdm[2592]: X server for display :0 terminated
> unexpectedly
>
> after this only SysRq keys work.
>
> Similar problem (older kernels):
> https://bugzilla.kernel.org/show_bug.cgi?id=15004
>
> Workaround: setting i915.modeset=1 pci=nocrs OR i915.modeset=0
>
> Dmesg with i915.modeset=1 pci=nocrs:
> http://unixy.pl/maciek/download/kernel/2.6.34-rc2/gumis/dmesg2.6.34-rc2.txt
>
> Config:
> http://unixy.pl/maciek/download/kernel/2.6.34-rc2/gumis/config-2.6.34-rc2
>
> Syslog (i915.modeset=1 -- when hangs)):
> http://unixy.pl/maciek/download/kernel/2.6.34-rc2/gumis/syslog-2.6.34-rc2
>
> lspci:
> http://unixy.pl/maciek/download/kernel/2.6.34-rc2/gumis/lspci.txt
>
> Regards
>
prev parent reply other threads:[~2010-03-25 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 20:04 Maciej Rutecki
2010-03-25 20:16 ` Maciej Rutecki
2010-03-25 20:37 ` Rafael J. Wysocki [this message]
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=201003252137.12278.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=airlied@linux.ie \
--cc=bjorn.helgaas@hp.com \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@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
all inboxes | Powered by JetHome®