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:	Mon, 28 Mar 2011 20:09:13 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Pekka Enberg <penberg@...nel.org>, Dave Airlie <airlied@...ux.ie>
Cc:	torvalds@...ux-foundation.org,
	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] drm fixes for -rc1

On Mon, 28 Mar 2011 21:53:32 +0300, Pekka Enberg <penberg@...nel.org> wrote:
> On Mon, Mar 28, 2011 at 9:43 PM, Pekka Enberg <penberg@...nel.org> wrote:
> > On Thu, Mar 24, 2011 at 1:34 PM, Dave Airlie <airlied@...ux.ie> wrote:
> >> It should have the fix for your i915 in the intel patches, along with
> >> a couple of radeon fixes, and the vblank change + fix.
> >
> > I'm seeing some laptop screen flicker during boot and a while after I
> > log in (it then seems to go away). It's my trusty old Macbook with
> > i915 and Ubuntu 10.04. I see this in dmesg:
> >
> > [    1.782046] [drm] initialized overlay support
> > [    1.782075] [drm] capturing error event; look for more information
> > in /debug/dri/0/i915_error_state
> > [    1.782889] render error detected, EIR: 0x00000010
> > [    1.782933] page table error
> > [    1.782970]   PGTBL_ER: 0x00000102
> > [    1.783009] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck:
> > 0x00000010, masking
> > [    1.783063] render error detected, EIR: 0x00000010
> > [    1.783106] page table error
> > [    1.783143]   PGTBL_ER: 0x00000102
> >
> > I'm attaching the full dmesg, i915_error_state, and .config.

Right, looks like we have an issue with setting up the hardware for
KMS/GEM whilst it is still active. As we disable the outputs anyway for
the KMS takeover, we can arrange to do so first and so prevent this bug.
The side-effect will be that initial screen blanking will last a little
bit longer.

> I'm also seeing these errors now which seem to be new from 2.6.38-final:
> 
> [  437.566022] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a
> purgeable buffer
> [  437.566187] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a
> purgeable buffer
> [  437.566232] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a
> purgeable buffer
> [  437.566275] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a
> purgeable buffer
> [  437.566318] [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a
> purgeable buffer

That's an old userspace bug, which so far no one has been able to
reproduce on the upstream ddx.
-Chris

-- 
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ