From: Chris Wilson <chris@chris-wilson.co.uk>
To: Peter Clifton <pcjc2@cam.ac.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: Regression since 53984635a659e360f206a81ada4ae813152d72f1 (drm/i915: use the complete gtt)
Date: Tue, 09 Nov 2010 18:56:40 +0000 [thread overview]
Message-ID: <b9dded$h19jbc@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1289326968.2289.4.camel@pcjc2lap>
On Tue, 09 Nov 2010 18:22:48 +0000, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> Since the above commit, my GL app will crash after a period of sustained
> graphics activity. It appears to use quite a lot of small BOs for
> uploading changed VBO data with glBufferSubData, and I don't think these
> are being purged until the GTT is full.
>
> For some reason, with gtt size != mappable size, the GPU will hang after
> a while. I had thought that we were missing a guard page from
> mappable_size, but subtracting a PAGE_SIZE did not help. Only resetting
> gtt_size to mappable_size (still subtracting a guard page) helped.
>
> Adding some instrumentation shows:
>
> Prealloc size 33550336, gtt size 2147479552, mappable size 268435456
/sys/kernel/debug/dri/0/i915_gem_objects
> This is an GM45 on a HP 6730b laptop.
>
> Any hints as to where to look now?
>
> Are things being put into unmappable GTT space when they need to be
> mappable?
This is the likely suspect. Check /sys/kernel/debug/dri/0/i915_error_state.
Do you have a test case that I can run? I've been beating upon this using
i945, pnv, q35 and g45 for quite some time and found it to be stable (for
my uses at least).
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-09 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 18:22 Regression since 53984635a659e360f206a81ada4ae813152d72f1 (drm/i915: use the complete gtt) Peter Clifton
2010-11-09 18:49 ` Peter Clifton
2010-11-09 18:56 ` Chris Wilson [this message]
2010-11-09 19:09 ` Peter Clifton
2010-11-09 19:43 ` Chris Wilson
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='b9dded$h19jbc@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pcjc2@cam.ac.uk \
/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