public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: Ryan Richter <ryan@tau.solarneutrino.net>
Cc: 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 12:55:51 +0200	[thread overview]
Message-ID: <4530C237.6050809@argo.co.il> (raw)
In-Reply-To: <20061013194516.GB19283@tau.solarneutrino.net>

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
>

I had the same problem.  Recompiling i965_dri.so in order to insert 
debugging code "fixed" it for me.  It continued working  after a mesa 
package update so I assumed it was a miscompilation.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 19:45 Intel 965G: i915_dispatch_cmdbuffer failed (2.6.19-rc2) 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 [this message]
2006-10-14 18:15 ` Keith Packard
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=4530C237.6050809@argo.co.il \
    --to=avi@argo.co.il \
    --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