Re: çå: problem with kmemleak

From: Catalin Marinas
Date: Fri May 13 2011 - 10:09:12 EST


On Fri, 2011-05-13 at 10:32 +0100, ttlxzz ccc wrote:
> I have tested kmemleak on the x86 and x86_64 architecture again. There
> is only
> backtrace:
>
> [<ffffffffffffffff>] 0xffffffffffffffff
>
> unreferenced object 0xffffc90012d27000 (size 64):
>
> comm "insmod", pid 13092, jiffies 4298369684
>
> hex dump (first 32 bytes):
>
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>
> backtrace:
>
> [<ffffffffffffffff>] 0xffffffffffffffff
>
> But in the x86, there is full backtrace.

Can you enable CONFIG_BACKTRACE_SELF_TEST and check whether the
boot-time backtrace test goes ok?

--
Catalin


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