linux-kernel - Re: render error detected, EIR: 0x00000010

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 13 May 2010 23:46:30 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
	dri-devel@...ts.freedesktop.org, Dave Airlie <airlied@...ux.ie>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: render error detected, EIR: 0x00000010

On Fri, 14 May 2010 03:59:08 +0530, Jaswinder Singh Rajput <jaswinderlinux@...il.com> wrote:
> Hello Chris,
> 
> I am also getting display error on another PC :
> 
> [   34.198957] render error detected, EIR: 0x00000010
> [   34.198972] [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
> [   34.198998] render error detected, EIR: 0x00000010

Wow. Things are really amiss there. MI_SET_CONTEXT (the first instruction
in the batch) was removed in

  commit 45f45c73469f1bd46a1b6fb206f2e9e5e4fd66b3
  Author: Eric Anholt <eric@...olt.net>
  Date:   Mon Dec 29 11:26:11 2008 -0800

      Remove logical context setup.

which explains why the destination bo is not on the active list, you
have a pre-GEM UMS xf86-video-intel (so the batchbuffer is using absolute
addressing rather than relocs and the kernel memory manager). The hardware
is reporting a PTE error (in the overlay plane!) and the single active
command is to clear the absolute buffer. As it is not being tracked by the
kernel, I can't tell you what's wrong with the buffer, but most probably
either the size or its stride is illegal in the context of that command.
Or maybe even the GTT hasn't been fully initialised for the buffer, it is
impossible to tell.

In short, you can trade this bug against the risk of GTT incoherency that
is endemic on i8xx by updating your driver.

-- 
Chris Wilson, Intel Open Source Technology Centre
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/