From: "Breton M. Saunders" <brett@mynah-software.com>
To: intel-gfx@lists.freedesktop.org
Subject: significant ioremap leak in i915?
Date: Sun, 12 Oct 2014 10:28:24 +0100 [thread overview]
Message-ID: <543A49B8.20400@mynah-software.com> (raw)
Guys,
This might be covered elsewhere, but help me come up to speed: I am
trying to analyze a leak in i915 that occurs on a digital sinage system
that I've built. The system basically is doing a lot of
XCompositeRedirectWindow / glXBindTexImageEXT calls to render web views
and mplayer output onto opengl textures for subsequent rendering.
In my testing, I observe that an enormous block is being lost in
ioremap by looking at /proc/vmallocinfo:
<snip>
0xffffc90000200000-0xffffc90010201000 268439552
pci_mmcfg_arch_map+0x33/0x90 phys=e0000000 ioremap
<snip>
0xffffc90010f80000-0xffffc90020f81000 268439552
i915_driver_load+0x20c/0x6d0 [i915] phys=c0000000 ioremap
<snip>
So in this example 268 megabytes have been lost.
Now what is even more vexing is if I stop the software, and X11 both
blocks are still present on the vmalloc list. If I then proceed to
rmmod i915 the i915 entry vanishes, however, the pci_mmcfg_arch_map
mapping remains.
It is entirely possible that I am doing something stupid from
userland (opengl) however, my test runs reliably on an NVidia based
machine - no leaks, runs until I power it off. I also think that
whatever wrongness I may be doing in userland I shouldn't be able to
blow up the system in this way.
For clarity, my setup is:
A NUC 2820 (I.e. Haswell N2820 CPU, 2.13GHz). 1Gb physical ram.
Operating system: Ubuntu 14.04 (as shipped):
kernel version 3.13.0-37-generic (i.e. Ubuntu's build)
Xorg: X.Org X Server 1.15.1
Intel xorg module: compiled for 1.15.1, module version
= 2.99.916
Acceleration mode: uxa (although SNA shows no
difference with regards to the leak).
Any suggestions would be welcome on how to address / analyze this - in
the meantime I will be digging through the i915 source code to try to
better understand the problem.
Cheers,
-Brett
next reply other threads:[~2014-10-12 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 9:28 Breton M. Saunders [this message]
2014-10-12 10:23 ` significant ioremap leak in i915? Dave Airlie
2014-10-12 11:07 ` Breton M. Saunders
2014-10-13 1:09 ` Dave Airlie
2014-10-13 4:58 ` Breton M. Saunders
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=543A49B8.20400@mynah-software.com \
--to=brett@mynah-software.com \
--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