From: Damien Wyart <damien.wyart@free.fr>
To: Zeno Davatz <zdavatz@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
x86@kernel.org, mingo@elte.hu, yinghai@kernel.org
Subject: Re: kmemleak, cpu usage jump out of nowhere
Date: Fri, 20 Aug 2010 11:32:26 +0200 [thread overview]
Message-ID: <20100820093226.GA7371@brouette> (raw)
In-Reply-To: <1280826924.4c57de2c3a6b0@imp.free.fr>
Hi,
> > > 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.
After a few days of running 2.6.35.2 without problem, I got the same
huge slowness for a few tens of seconds yesterday. Did not have time to
run perf (and the system was almost unresponsive), but I will try to do
so if the problem occurs again. Anyway, even if less frequent than
during the -rcs, and as nothing had been commited to fix it before
final, the problem is still there...
It seems that the problem occurs after some CPU intensive tasks have
been run for some time (ie compiling a kernel) and only on Core i7
machines with NO_BOOTMEM. I am surprised so few people reported it and
that it has not been seen on test machines running CPU/scheduler
benchmark tools.
--
Damien Wyart
next prev parent reply other threads:[~2010-08-20 9:40 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 6:12 kmemleak, cpu usage jump out of nowhere Zeno Davatz
2010-07-14 8:05 ` Pekka Enberg
2010-07-14 8:27 ` Zeno Davatz
2010-07-14 9:47 ` Catalin Marinas
2010-07-14 9:55 ` Pekka Enberg
2010-07-14 10:00 ` Zeno Davatz
2010-07-15 14:58 ` Catalin Marinas
2010-07-15 15:15 ` Zeno Davatz
2010-07-15 15:54 ` Pekka Enberg
2010-07-15 16:28 ` Damien Wyart
2010-07-15 19:16 ` Damien Wyart
2010-07-15 19:50 ` Pekka Enberg
2010-07-15 20:00 ` Damien Wyart
2010-07-15 20:38 ` Zeno Davatz
2010-07-15 20:50 ` Pekka Enberg
2010-07-15 20:57 ` Zeno Davatz
2010-07-16 7:12 ` Zeno Davatz
2010-07-16 7:29 ` Zeno Davatz
2010-07-16 7:37 ` Zeno Davatz
2010-07-16 7:50 ` Pekka Enberg
2010-07-16 9:17 ` Zeno Davatz
2010-07-16 9:32 ` Pekka Enberg
2010-07-16 9:42 ` Zeno Davatz
2010-07-16 9:47 ` Zeno Davatz
2010-07-16 18:27 ` Yinghai Lu
2010-07-16 20:29 ` Zeno Davatz
2010-07-16 20:59 ` Yinghai Lu
2010-07-17 8:46 ` Zeno Davatz
2010-07-15 20:52 ` Pekka Enberg
2010-08-03 9:05 ` Peter Zijlstra
2010-08-03 9:11 ` Zeno Davatz
2010-08-03 9:15 ` damien.wyart
2010-08-03 9:18 ` Zeno Davatz
2010-08-20 9:32 ` Damien Wyart [this message]
2010-08-20 9:40 ` Peter Zijlstra
2010-07-14 8:31 ` Damien Wyart
2010-07-14 8:34 ` Zeno Davatz
2010-07-14 8:38 ` Pekka Enberg
2010-07-14 8:54 ` Zeno Davatz
2010-07-14 8:57 ` Pekka Enberg
2010-07-14 9:57 ` Catalin Marinas
2010-07-14 10:04 ` Zeno Davatz
2010-07-14 11:54 ` Catalin Marinas
2010-07-14 11:59 ` Zeno Davatz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100820093226.GA7371@brouette \
--to=damien.wyart@free.fr \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
--cc=zdavatz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox