The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Leandro Lucarella <luca@llucax.com.ar>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	David Airlie <airlied@linux.ie>,
	intel-gfx@lists.freedesktop.org
Subject: Re: Graphic corruption with i915 (2.6.39.1)
Date: Thu, 16 Jun 2011 13:18:03 -0300	[thread overview]
Message-ID: <20110616161803.GQ20487@llucax.com.ar> (raw)
In-Reply-To: <013811$g9fu7@fmsmga002.fm.intel.com>

Chris Wilson, el 16 de junio a las 17:01 me escribiste:
> On Thu, 16 Jun 2011 11:58:42 -0300, Leandro Lucarella <luca@llucax.com.ar> wrote:
> > Hi, I've been experiencing sporadic graphic corruption since a few
> > stable kernel versions and I always thought "maybe is fixed in the next
> > release", so I upgrade, but I usually experience a different problem
> > then. This problems are exposed very rarely, maybe I have no problems
> > like for a month or so.
> > 
> > Now I'm using kernel 2.6.39.1 and I experience one of this problem so
> > I though it was time to report it. This is what I got in dmesg:
> > 
> > [368693.756008] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> > [368693.756014] render error detected, EIR: 0x00000010
> > [368693.756017]   IPEIR: 0x00000000
> > [368693.756019]   IPEHR: 0x02000004
> > [368693.756020]   INSTDONE: 0xcc8fffff
> > [368693.756022]   INSTPS: 0x8001e025
> > [368693.756024]   INSTDONE1: 0xbfffffbf
> > [368693.756026]   ACTHD: 0x00715128
> > [368693.756027] page table error
> > [368693.756029]   PGTBL_ER: 0x00000002
> > [368693.756038] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 17700193 at 17700192, next 17700196)
> > [368694.258010] [drm:i915_reset] *ERROR* Failed to reset chip.
> 
> If you look in /sys/kernel/debug/dri/0/i915_error_state we can see what
> garbage the DDX [xf86-video-intel] fed the gpu.

cannot access /sys/kernel/debug/dri/0/i915_error_state: No such file or directory

The debug directory is not present, should I boot or compile with some
particular option to enable it?

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Refalar: acto de mover el peso de la masa hacia un lugar equivocado pero
concreto. Todo refalo es, por cierto, una sucesión de pequeñísimos
movimientos a los que un centímetro es la proporción aumentada de miles
de porciones de espacio, que, al estar el piso mojado, refala.
	-- Ricardo Vaporeso

  parent reply	other threads:[~2011-06-16 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 14:58 Graphic corruption with i915 (2.6.39.1) Leandro Lucarella
     [not found] ` <013811$g9fu7@fmsmga002.fm.intel.com>
2011-06-16 16:18   ` Leandro Lucarella [this message]
2011-06-16 16:39     ` Chris Wilson
2011-06-16 16:57       ` Leandro Lucarella
2011-06-16 18:24         ` Raúl Benencia
2011-07-30 15:02       ` Leandro Lucarella

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=20110616161803.GQ20487@llucax.com.ar \
    --to=luca@llucax.com.ar \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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