On 07/09/06, Michal Piotrowski <[email protected]> wrote:
I get a kernel panic
http://www.stardust.webpages.pl/files/o_bugs/kmemleak-0.10/panic.jpg
http://www.stardust.webpages.pl/files/o_bugs/kmemleak-0.10/kml-config
Well, you set CONFIG_DEBUG_MEMLEAK_HASH_BITS to 32, this means that
kmemleak needs to allocate (sizeof(void*) * 2^32) which is 16GB of
RAM. I think a maximum of 20 should be enough (I got acceptable
results with 16 hash bits, the default value, and it seemed to do
better with 18).
--
Catalin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
