[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1280826924.4c57de2c3a6b0@imp.free.fr>
Date: Tue, 03 Aug 2010 11:15:24 +0200
From: damien.wyart@...e.fr
To: Zeno Davatz <zdavatz@...il.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Damien Wyart <damien.wyart@...e.fr>,
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
> > 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.
Damien
--
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