public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: GTT full but LRU empty
Date: Mon, 26 Jan 2009 14:38:32 -0800	[thread overview]
Message-ID: <1233009512.4876.3.camel@gaiman> (raw)
In-Reply-To: <497DFC8B.9040405@gmail.com>

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

On Mon, 2009-01-26 at 19:10 +0100, Jacek Luczak wrote:
> Hi Eric,
> 
> Are those errors known?
> 
> [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
> [drm:i915_gem_object_pin] *ERROR* Failure to bind:
> -12<3>[drm:i915_gem_evict_something] *ERROR* inactive empty 1 request empty 1
> flushing empty 1
> [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
> [drm:i915_gem_object_pin] *ERROR* Failure to bind:
> -12<3>[drm:i915_gem_evict_something] *ERROR* inactive empty 1 request empty 1
> flushing empty 1
> [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
> [drm:i915_gem_object_pin] *ERROR* Failure to bind:
> -12<3>[drm:i915_gem_execbuffer] *ERROR* Failed to pin buffers -12
> [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
> [drm:i915_gem_object_pin] *ERROR* Failure to bind:
> -12<3>[drm:i915_gem_evict_something] *ERROR* inactive empty 1 request empty 1
> flushing empty 1
> [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
> [drm:i915_gem_object_pin] *ERROR* Failure to bind:
> -12<3>[drm:i915_gem_execbuffer] *ERROR* Failed to pin buffers -12
> 
> They appeared once and no more, but I've changed my configuration in between
> (switched to UXA, removed IntelFB from kernel).

Those messages occur when a client asks the kernel to exec a batchbuffer
that the kernel can't fit into the unpinned aperture space.  Userland is
supposed to be tracking how much space its stuff uses and flushing
before that time, but certain bad things could break that by violating
the assumption that the amount of pinned space doesn't change.  Our XV
code today, for example.  I've been working on cleaning up the remaining
bad userland bits, but it's painful work.  Luckily, other than dmesg
spam warning that some rendering just go dropped on the floor, and some
rendering not occurring, nothing else harmful should be happening.

-- 
Eric Anholt
eric@anholt.net                         eric.anholt@intel.com



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

  reply	other threads:[~2009-01-26 22:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 18:10 GTT full but LRU empty Jacek Luczak
2009-01-26 22:38 ` Eric Anholt [this message]
2009-01-27  8:07   ` Jacek Luczak

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=1233009512.4876.3.camel@gaiman \
    --to=eric@anholt.net \
    --cc=difrost.kernel@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