From: Constantin Baranov <const@mimas.ru>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Maciej Rutecki <maciej.rutecki@gmail.com>,
Tarkan Erimer <tarkane@netone.com.tr>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] Linux-2.6.32-git10 drm_i915 error
Date: Sun, 10 Jan 2010 23:37:03 +0400 [thread overview]
Message-ID: <20100110233703.9060e075.const@mimas.ru> (raw)
In-Reply-To: <201001101933.39683.rjw@sisk.pl>
On Sun, 10 Jan 2010 19:33:39 +0100 "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> On Sunday 10 January 2010, Maciej Rutecki wrote:
> > 2009/12/14 Tarkan Erimer <tarkane@netone.com.tr>:
> > > Frequently, I hit this bug on Linux-2.6.32-git10. It's always
> > > re-producible for me on my i945 video device equipped HP machine. When
> > > hit this bug, it crashes the X server and screen goes black. But,
> > > possible to switch to console. Here is the error log, I had in dmesg:
> > >
> > > [ 2596.328132] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
> > > elapsed... GPU hung
> > > [ 2596.328146] render error detected, EIR: 0x00000000
> > > [ 2596.328167] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request
> > > returns -5 (awaiting 694588 at 694584)
> > > [ 2596.439006] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
> > > elapsed... GPU hung
> > > [ 2596.439013] render error detected, EIR: 0x00000000
> > >
> > > Tarkan
> >
> > I confirm this. A observed this on 2.6.33-rc3-git3 after resume from suspend:
> >
> > Jan 10 08:51:31 gumis kernel: [ 486.880045]
> > [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU
> > hung
> > Jan 10 08:51:31 gumis kernel: [ 486.880063] render error detected,
> > EIR: 0x00000000
> > Jan 10 08:51:31 gumis kernel: [ 486.880107]
> > [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (
> > awaiting 60107 at 60105)
> > Jan 10 08:51:32 gumis kernel: [ 487.276302] [drm:i915_gem_execbuffer]
> > *ERROR* i915_gem_do_execbuffer returns -5
> > Jan 10 08:51:32 gumis kernel: [ 487.276799] [drm:i915_gem_execbuffer]
> > *ERROR* i915_gem_do_execbuffer returns -5
> > Jan 10 08:51:32 gumis kernel: [ 487.277230] [drm:i915_gem_execbuffer]
> > *ERROR* i915_gem_do_execbuffer returns -5
> > Jan 10 08:51:32 gumis kernel: [ 487.278308] [drm:i915_gem_execbuffer]
> > *ERROR* i915_gem_do_execbuffer returns -5
> > Jan 10 08:51:32 gumis kernel: [ 487.278533] [drm:i915_gem_execbuffer]
> > *ERROR* i915_gem_do_execbuffer returns -5
> >
> > 2.6.33-rc2 works fine.
>
> http://bugzilla.kernel.org/show_bug.cgi?id=15026 perhaps?
I have caught this bug in 2.6.31.9, 2.6.32.2, 2.6.33-rc3 and 2.6.33-rc3-git3
on my Acer Aspire 1410T with Intel GM45 chipset. It is not needed to perform
suspend and resume to reproduce the bug. The bug appears for me at startup
of the Stellarium (trunk version).
next prev parent reply other threads:[~2010-01-10 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 12:50 [BUG] Linux-2.6.32-git10 drm_i915 error Tarkan Erimer
2010-01-10 14:20 ` Maciej Rutecki
2010-01-10 18:33 ` Rafael J. Wysocki
2010-01-10 19:37 ` Constantin Baranov [this message]
2010-01-10 20:41 ` Rafael J. Wysocki
2010-01-10 20:13 ` Maciej Rutecki
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=20100110233703.9060e075.const@mimas.ru \
--to=const@mimas.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
--cc=tarkane@netone.com.tr \
/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