On 07/09/06, Catalin Marinas <[email protected]> wrote:
On 07/09/06, Michal Piotrowski <[email protected]> wrote:
> On 07/09/06, Catalin Marinas <[email protected]> wrote:
> > 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).
>
> CONFIG_DEBUG_MEMLEAK=y
> CONFIG_DEBUG_MEMLEAK_HASH_BITS=8
> CONFIG_DEBUG_MEMLEAK_TRACE_LENGTH=12
> CONFIG_DEBUG_MEMLEAK_PREINIT_OBJECTS=512
> # CONFIG_DEBUG_MEMLEAK_SECONDARY_ALIASES is not set
> # CONFIG_DEBUG_MEMLEAK_TASK_STACKS is not set
> # CONFIG_DEBUG_MEMLEAK_ORPHAN_FREEING is not set
> CONFIG_DEBUG_MEMLEAK_REPORTS_NR=100
> # CONFIG_DEBUG_KEEP_INIT is not set
> # CONFIG_DEBUG_MEMLEAK_TEST is not set
>
> I still get a panic
Is it in the same place? What does the panic text say?
It's the same "kmemleak: cannot allocate the pointer hash" panic.
BTW, you should probably enable SECONDARY_ALIASES and TASK_STACKS
above to reduce the number of false positives.
--
Catalin
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
-
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]
