From: Chris Wilson <chris@chris-wilson.co.uk>
To: David Feuer <david.feuer@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: i915 drm crashes with link to relevant i915_error_state
Date: Wed, 29 Feb 2012 10:23:20 +0000 [thread overview]
Message-ID: <aefc95$3boor4@orsmga001.jf.intel.com> (raw)
In-Reply-To: <CAMgWh9tRJ45+X0iuTWXOLeohADi_fbd68e8-cAAroHr2QvyZmQ@mail.gmail.com>
On Wed, 29 Feb 2012 02:48:07 -0500, David Feuer <david.feuer@gmail.com> wrote:
> I've put up the i915_error_state at
> http://techhouse.org/~dfeuer/i915_error_state to (hopefully) allow
> this message to go through.
[snip]
> I got these two incidents running supertuxkart, which is my favorite
> way to generate drm crashes. fgfs (flight sim) and blender (3d
> graphics editor) are quite efficient for that too, though much less so
> than in previous kernel versions.
Please file a bug report against Mesa/i965 on bugzilla.freedesktop.org.
The kernel is reporting that the userspace GL driver has caused the GPU
to execute an invalid program.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2012-02-29 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 7:48 i915 drm crashes with link to relevant i915_error_state David Feuer
2012-02-29 10:23 ` Chris Wilson [this message]
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='aefc95$3boor4@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=david.feuer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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