mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Zou Nan hai <nanhai.zou@intel.com>,
	Xiang Hai hao <haihao.xiang@intel.com>,
	Eric Anholt <eric@anholt.net>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: i915 completely broken with KMS off
Date: Tue, 18 Jan 2011 09:16:46 -0800	[thread overview]
Message-ID: <20110118091646.73a5014c@jbarnes-desktop> (raw)
In-Reply-To: <20110118115701.GA11952@gondor.apana.org.au>

On Tue, 18 Jan 2011 22:57:01 +1100
Herbert Xu <herbert@gondor.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@intel.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

  reply	other threads:[~2011-01-18 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 11:57 Herbert Xu
2011-01-18 17:16 ` Jesse Barnes [this message]
2011-01-18 17:24 ` [PATCH] drm/i915: Correctly test for an initialised ring for dri1 Chris Wilson
2011-01-19  3:24   ` Herbert Xu
2011-01-19  9:53     ` [PATCH] drm/i915: Initialise ring vfuncs for old DRI paths Chris Wilson
2011-01-19 10:31       ` Herbert Xu
2011-01-20  7:05       ` Herbert Xu
2011-01-20  9:56         ` [PATCH] drm/i915: Don't kick-off hangcheck after a DRI interrupt Chris Wilson
2011-01-20 10:10           ` Herbert Xu
2011-01-20 11:00             ` [PATCH] drm/i915: Dont " Chris Wilson
2011-01-20 11:35               ` Herbert Xu

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=20110118091646.73a5014c@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=eric@anholt.net \
    --cc=haihao.xiang@intel.com \
    --cc=herbert@gondor.hengli.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nanhai.zou@intel.com \
    /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

all inboxes | Powered by JetHome®