[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimM_jTTRVsJdht9gyBiiBw758nP4_pw-dx5OtZn@mail.gmail.com>
Date: Tue, 3 Aug 2010 11:18:12 +0200
From: Zeno Davatz <zdavatz@...il.com>
To: damien.wyart@...e.fr
Cc: Peter Zijlstra <peterz@...radead.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Catalin Marinas <catalin.marinas@....com>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>, x86@...nel.org,
mingo@...e.hu, yinghai@...nel.org
Subject: Re: kmemleak, cpu usage jump out of nowhere
On Tue, Aug 3, 2010 at 11:15 AM, <damien.wyart@...e.fr> wrote:
>> > Vacation.. but now I'm back ;-)
>> >
>> > Even something simple as: perf top -r 1 (make sure you're root in order
>> > to run with real-time prios) could give a clue as to what is consuming
>> > all your cpu-time.
>> >
>> > Or did the issue get sorted already?
>>
>> Thank you for the hint.
>>
>> I am on 2.6.35 now and all seems to be fine again.
>
> Are you 100% sure you compiled it with CONFIG_NO_BOOTMEM enabled?
>
> I did not test 2.6.35 yet but I did not see anything related to this bug
> commited since the discussion so I am very surprised the problem disappeared by
> itself...
>
> Will be on vacation very soon, so not sure I will have time to test 2.6.35
> before leaving.
Yes: I got:
# CONFIG_PARAVIRT_SPINLOCKS is not set
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set
CONFIG_NO_BOOTMEM=y
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
in my .config.
Linux zenogentoo 2.6.35 #122 SMP Mon Aug 2 10:26:05 CEST 2010 i686
Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
Best
Zeno
--
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