From: Chris Wilson <chris@chris-wilson.co.uk>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: "xorg-devel@lists.x.org Development" <xorg-devel@lists.x.org>,
linux-kernel@vger.kernel.org
Subject: Re: drm_gem_create_mmap_offset / intel_uxa_prepare_access bo problems
Date: Thu, 22 Nov 2012 15:37:23 +0000 [thread overview]
Message-ID: <84c8a8$6kot4e@orsmga001.jf.intel.com> (raw)
In-Reply-To: <50AE44C4.1060606@t-online.de>
On Thu, 22 Nov 2012 16:29:08 +0100, Knut Petersen <Knut_Petersen@t-online.de> wrote:
> Hi Chris!
>
> Problem:
> =======
> Slowdown of system, missing icons after 16 days kernel uptime and 12 days Xserver uptime.
> Xorg log: flooded with "(WW) intel(0): intel_uxa_prepare_access: bo map (use gtt? 1, access 1) failed: No space left on device" lines
> dmesg: flooded with "[drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0" entries
>
>
> Hardware
> =======
> AOpen i915GMm-hfs, Pentium-M Dothan
>
> Software:
> =======
> linux kernel 3.6.6
> full Xorg git master, fetch/build 10 November 2012,
> video-intel: git f5d79b202dd448e61ab6ffce26fe9cbf9051d770
> xserver: git 011f8458805e443ac9130865d2840a929a00cabf
> rest of system openSuSE 12.1
>
> Any idea?
Well you kernel and drm has all the latest protections, which is good
because it's usually a bo leak of some sort. First stop is to check
xrestop, /sys/kernel/debug/dri/0/i915_gem_objects and
intel-gpu-tools/scripts/who.sh
That will undoubtably reveal a large number of objects being held by the
X server...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-11-22 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 15:29 drm_gem_create_mmap_offset / intel_uxa_prepare_access bo problems Knut Petersen
2012-11-22 15:37 ` Chris Wilson [this message]
2012-11-23 8:46 ` Knut Petersen
2012-12-04 11:08 ` Knut Petersen
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='84c8a8$6kot4e@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=Knut_Petersen@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xorg-devel@lists.x.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