From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel@vger.kernel.org,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: kmemleak disabled itself in 2.6.36
Date: Thu, 28 Oct 2010 15:13:25 +0200 [thread overview]
Message-ID: <201010281513.26185.toralf.foerster@gmx.de> (raw)
In-Reply-To: <1288254789.10238.5.camel@e102109-lin.cambridge.arm.com>
Catalin Marinas wrote at 10:33:09
> On Wed, 2010-10-27 at 20:12 +0100, Toralf Förster wrote:
> > I'm unsure whether this happens due to a
> > $> sudo su -c "echo clear > /sys/kernel/debug/kmemleak"
> > or while regular scanning, but anyway seems not to be normal, or ?
> >
> > 2010-10-27T20:42:21.697+02:00 n22 kernel: flush-254:0: page allocation
> > failure. order:0, mode:0x0
>
> [...]
>
> > 2010-10-27T20:42:21.699+02:00 n22 kernel: kmemleak: Cannot allocate a
> > kmemleak_object structure 2010-10-27T20:42:21.699+02:00 n22 kernel: Pid:
> > 15475, comm: flush-254:0 Not tainted 2.6.36 #2
>
> [...]
>
> > 2010-10-27T20:42:21.700+02:00 n22 kernel: kmemleak: Kernel memory leak
> > detector disabled
>
> Are you running out of memory on your system? Kmemleak tried to allocate
> a structure but the slab allocator failed to get page. Kmemleak disables
> itself in such situations but the problem is somewhere else (not enough
> memory?).
>
> Catalin
I don't think so - no big load to that system, no excessive compiler runs ...
--
MfG/Kind regards
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next prev parent reply other threads:[~2010-10-28 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 19:12 Toralf Förster
2010-10-28 8:33 ` Catalin Marinas
2010-10-28 13:13 ` Toralf Förster [this message]
2010-10-28 13:33 ` Catalin Marinas
2010-10-29 8:31 ` Toralf Förster
2010-11-29 17:28 ` Toralf Förster
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=201010281513.26185.toralf.foerster@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrodriguez@atheros.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
all inboxes | Powered by JetHome®