Re: kmemleak disabled itself in 2.6.36

[Toralf FÃrster]

Catalin Marinas wrote at 15:33:22
> On Thu, 2010-10-28 at 14:13 +0100, Toralf FÃrster wrote:
> > 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?).
> > 
> > I don't think so - no big load to that system, no excessive compiler runs
> > ...
> 
> What does /proc/meminfo say after you got this error?
> 
> Which slab allocator are you using?
> 
> Catalin

These are the settings :

tfoerste@n22 ~ $ zgrep ^CONFIG_SL.B /proc/config.gz 
CONFIG_SLAB=y
CONFIG_SLABINFO=y

I didn't took a look into  /proc/meminfo when it happened.

-- 
MfG/Kind regards
Toralf FÃrster

pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

--
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/