mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Ryan Richter <ryan@tau.solarneutrino.net>
Cc: keithp@keithp.com, dri-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: Intel 965G: i915_dispatch_cmdbuffer failed (2.6.19-rc2)
Date: Sat, 14 Oct 2006 11:15:23 -0700	[thread overview]
Message-ID: <1160849723.3943.41.camel@neko.keithp.com> (raw)
In-Reply-To: <20061013194516.GB19283@tau.solarneutrino.net>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

On Fri, 2006-10-13 at 15:45 -0400, Ryan Richter wrote:
> I have a new Intel 965G board, and I'm trying to get DRI working.
> Direct rendering is enabled, but all GL programs crash immediately.
> The message 'DRM_I830_CMDBUFFER: -22' is printed on the tty, and the
> kernel says:
> 
> [drm:i915_cmdbuffer] *ERROR* i915_dispatch_cmdbuffer failed

The 915 DRM validates commands sent to the card from the application to
ensure they aren't directing the card to access memory outside of the
graphics area. At present the module validates only 915/945 commands
correctly and the 965 uses slightly different commands. I haven't walked
over the entire GL library, but it seems possible that this error is
being caused by the mis-validation of the command stream. We need to
update the DRM driver to reflect the new commands, but in the meanwhile,
you might try disabling the validation in the kernel (which will expose
your system to a local root compromise) and seeing if that doesn't
eliminate this message.

-- 
keith.packard@intel.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-10-14 18:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 19:45 Ryan Richter
2006-10-14  8:55 ` Keith Whitwell
2006-10-14  9:49   ` Arjan van de Ven
2006-10-14  9:58     ` Keith Whitwell
2006-10-14 10:55 ` Avi Kivity
2006-10-14 18:15 ` Keith Packard [this message]
2006-10-17 17:40   ` Ryan Richter
2006-10-17 22:27     ` Keith Packard
2006-10-17 23:56       ` Ryan Richter
2006-10-18  6:54       ` Keith Whitwell
2006-10-18  7:01         ` Dave Airlie
2006-10-19 17:31         ` Ryan Richter
2006-10-20 11:43           ` Keith Whitwell
2006-10-20 16:40             ` Ryan Richter
2006-10-20 17:51               ` Keith Whitwell
2006-10-20 18:03                 ` Ryan Richter
2006-10-20 18:09                   ` Keith Whitwell
2006-10-24 12:21               ` Avi Kivity
2006-10-24 14:07                 ` Ryan Richter

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=1160849723.3943.41.camel@neko.keithp.com \
    --to=keithp@keithp.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan@tau.solarneutrino.net \
    /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

Powered by JetHome