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:	Tue, 18 Jan 2011 09:16:46 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Zou Nan hai <nanhai.zou@...el.com>,
	Xiang Hai hao <haihao.xiang@...el.com>,
	Eric Anholt <eric@...olt.net>,
	Chris Wilson <chris@...is-wilson.co.uk>
Subject: Re: i915 completely broken with KMS off

On Tue, 18 Jan 2011 22:57:01 +1100
Herbert Xu <herbert@...dor.apana.org.au> wrote:

> Hi:
> 
> I just upgraded my kernel on a machine with i915 and it has
> started crashing constantly with messages like this:
[snip]
> The cause is this changeset:
> 
> commit 8187a2b70e34c727a06617441f74f202b6fefaf9
> Author: Zou Nan hai <nanhai.zou@...el.com>
> Date:   Fri May 21 09:08:55 2010 +0800
> 
>     drm/i915: introduce intel_ring_buffer structure (V2)
> 
> This changeset completely broke i915 without KMS because the new
> intel_ring_buffer structure is never initialised with KMS off,
> unless the ioctl I915_GEM_ENTERVT is invoked.
> 
> So without invoking that ioctl, the kernel will always crash
> whenever the i915 driver dereferences pointers on the render_ring
> data structure.
> 
> Or is this a hint to get people to convert to KMS :)

Heh, well that would be one option for you. :)

The breakage was unintentional though; I imagine Chris will have an
idea of how to fix it quickly for you.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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