From: Chris Wilson <chris@chris-wilson.co.uk>
To: Alexey Fisher <bug-track@fisher-privat.net>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable buffer
Date: Wed, 20 Oct 2010 10:15:34 +0100 [thread overview]
Message-ID: <c6d829$p9me0q@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1287565640.7548.2.camel@zwerg>
On Wed, 20 Oct 2010 11:07:20 +0200, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> Hallo all,
>
> I get fallowing error in my log:
> [ 6657.465805] [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap
> a purgeable buffer
> [ 6657.465851] [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap
> a purgeable buffer
> [ 6657.465907] [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap
> a purgeable buffer
>
> das it mean any thing for you? do i need to bisect it?
> I use current 2.6.36-rc8-01141-ga5ffe0a from intel drm next.
It's warning that userspace is breaking the rules and trying to use a
buffer it has declared no longer in use. The challenge is to find the
scenario that is triggering this *userspace* bug.
Currently, purgeable is usually only set on the userspace bo cache, so
this means that we are continuing to use a freed buffer. Disabling (or
marking the cache as NO_ACCESS) and valgrinding would be a useful step.
Or just kill the userspace cache and implement a kernel uncached page
cache... Less code, more performance, everyone is happy...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-10-20 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 9:07 [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable buffer Alexey Fisher
2010-10-20 9:15 ` Chris Wilson [this message]
2010-10-20 10:03 ` Alexey Fisher
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='c6d829$p9me0q@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=bug-track@fisher-privat.net \
--cc=intel-gfx@lists.freedesktop.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