From: Damien Wyart <damien.wyart@free.fr>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Zeno Davatz <zdavatz@gmail.com>,
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: Thu, 15 Jul 2010 21:16:38 +0200 [thread overview]
Message-ID: <20100715191638.GA3694@brouette> (raw)
In-Reply-To: <20100715162805.GA10240@brouette>
> > > I also did not have anymore hangs and random bad moods of my CPUs
> > > that all of a sudden grab 100% of all 8 cores of my CPU power across
> > > my machine since I disabled
> > > CONFIG_NO_BOOTMEM:
> * Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-15 18:54]:
> > Interesting. Damien, does disabling CONFIG_NO_BOOTMEM fix you problem too?
> I will test in the coming hours, and report back tomorrow... Just
> recompiled 2.6.35-rc5-git1 with this option disabled.
For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
with the option and rc5 the problem was happening quite quickly after
boot and normal use of the machine. So it seems I can confirme what Zeno
has seen and I hope this will give a hint to debug the problem. I guess
this has not been reported that much because many testers might not have
enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
benchmark with a kernel having this option enabled?
--
Damien
next prev parent reply other threads:[~2010-07-15 19:17 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 [this message]
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
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=20100715191638.GA3694@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=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