[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0902211335g354b6860ic7244fb699d7d01b@mail.gmail.com>
Date: Sat, 21 Feb 2009 22:35:19 +0100
From: Vegard Nossum <vegard.nossum@...il.com>
To: Sitsofe Wheeler <sitsofe@...oo.com>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: Is kmemcheck currently broken on tip?
> 2009/2/21 Sitsofe Wheeler <sitsofe@...oo.com>:
>> Hi,
>>
>> I've been trying to test kmemcheck in linux-tip on my EeePC and things
>> have been going suspiciously not so slow with little extra memory used
>> (at least compared to the last time I used kmemcheck). While I see
>> [ 0.063412] kmemcheck: "Bugs, beware!"
>> in dmesg, I'm not sure kmemcheck is working especially since nothing is
>> flagged when I trigger the issue described in
>> http://marc.info/?l=linux-kernel&m=123472656015761&w=1 ...
Ah, sorry, you'll probably have to disable SLUB debugging on the
command line if it was enabled by default in the config. Boot with
slub_debug=- parameter. Maybe we should print a warning for this...
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists