Re: drm_gem_create_mmap_offset / intel_uxa_prepare_access bo problems

[Knut Petersen]

Hi everybody!

xrestop is functional again in xorg master, so I remembered to have a look at
the problem reported two weeks ago. It is caused by qinternet.

qinternet is a small utility  that is frequently used in opensuse systems to control
network connections. It attaches itself to the system tray of the kde panel, but it
also might be used with other desktop environments.

xrestop, proc/sys/fs/file-nr and /sys/kernel/debug/dri/0/i915_gem_objects
show that qinternet allocates one small pixmap every second. So it steadily
increases the number of inactive gem objects, the memory usage and the
number of used file descriptors. It is clear that this causes problems after
some time.

If someone at opensuse is reading this: This is an opensuse problem.
opensuse is a nice distribution, but as long as you do require people to
create a Novell acount with full address, phone number etc. to be able to
access the opensuse bugzilla I will not report bugs there.

cu,
 Knut



On 22.11.2012 16:37, Chris Wilson wrote:
> On Thu, 22 Nov 2012 16:29:08 +0100, Knut Petersen <Knut_Petersen@xxxxxxxxxxx> 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
> 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/