From: Knut Petersen <Knut_Petersen@t-online.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
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: Fri, 23 Nov 2012 09:46:04 +0100 [thread overview]
Message-ID: <50AF37CC.8080400@t-online.de> (raw)
In-Reply-To: <84c8a8$6kot4e@orsmga001.jf.intel.com>
On 22.11.2012 16:37, Chris Wilson wrote:
> 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
As the server had to be rebooted it will probably take some days to gather more information.
cu,
Knut
next prev parent reply other threads:[~2012-11-23 8:46 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
2012-11-23 8:46 ` Knut Petersen [this message]
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=50AF37CC.8080400@t-online.de \
--to=knut_petersen@t-online.de \
--cc=chris@chris-wilson.co.uk \
--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