public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Christoph Lameter <cl@linux.com>, David Airlie <airlied@linux.ie>
Cc: David Rientjes <rientjes@google.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: DRM-related kmalloc-32 memory leak in 2.6.35
Date: Wed, 25 Aug 2010 15:59:09 -0500	[thread overview]
Message-ID: <1282769949.3007.7.camel@calx> (raw)
In-Reply-To: <alpine.DEB.2.00.1008241036250.344@router.home>

On Tue, 2010-08-24 at 10:37 -0500, Christoph Lameter wrote:
> On Tue, 24 Aug 2010, Matt Mackall wrote:
> 
> > kmalloc-32        1113344 1113344     32  128    1 : tunables    0    0
> > 0 : slabdata   8698   8698      0
> >
> > That's /proc/slabinfo on my laptop with SLUB. It looks like my last
> > reboot popped me back to 2.6.33 so it may also be old news, but I
> > couldn't spot any reports with Google.
> 
> Boot with "slub_debug" as a kernel parameter
> 
> and then do a
> 
> cat /sys/kernel/slab/kmalloc-32/alloc_calls
> 
> to find the caller allocating the objets.

Still present in 2.6.35. Appears to be DRM:

    845 drm_vm_open_locked+0x72/0x109 age=43/37572/59269 pid=2089
cpus=0-1

That's after about a minute of uptime. Grows to 100k in about a day.

dmesg bits:
[    0.834653] [drm] Initialized drm 1.1.0 20060810
[    0.834986] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    0.834995] pci 0000:00:02.0: setting latency timer to 64
[    1.002572] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
[    1.002580] [drm] MTRR allocation failed.  Graphics performance may suffer.
[    1.019880] acpi device:03: registered as cooling_device2
[    1.021520] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3
[    1.021543] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    1.021855] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

This is with:

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 03)

-- 
Mathematics is the supreme nostalgia of our time.



       reply	other threads:[~2010-08-25 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.00.1008221615350.29062@chino.kir.corp.google.com>
     [not found] ` <1282623994.10679.921.camel@calx>
     [not found]   ` <alpine.DEB.2.00.1008232134480.25742@chino.kir.corp.google.com>
     [not found]     ` <1282663241.10679.958.camel@calx>
     [not found]       ` <alpine.DEB.2.00.1008241036250.344@router.home>
2010-08-25 20:59         ` Matt Mackall [this message]
2010-09-27 18:52           ` DRM-related kmalloc-32 memory leak in 2.6.35 Andrew Morton
2010-09-27 20:08             ` [PATCH] drm: Prune GEM vma entries Chris Wilson
2010-09-27 20:08               ` Andrew Morton
2010-09-27 20:28                 ` Chris Wilson
2010-10-02  0:09               ` Matt Mackall
2010-10-03 18:59                 ` Paul Rolland
2010-10-04  7:07               ` Paul Rolland
2010-09-27 20:40             ` DRM-related kmalloc-32 memory leak in 2.6.35 David Rientjes

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=1282769949.3007.7.camel@calx \
    --to=mpm@selenic.com \
    --cc=airlied@linux.ie \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=rientjes@google.com \
    /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