From: Damien Wyart <damien.wyart@free.fr>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Zeno Davatz <zdavatz@gmail.com>,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kmemleak, cpu usage jump out of nowhere
Date: Wed, 14 Jul 2010 10:31:12 +0200 [thread overview]
Message-ID: <20100714083112.GA4627@brouette> (raw)
In-Reply-To: <AANLkTinGoUml9PQ8w7flukqwF9V1ae-YafiDVQy6Q8gC@mail.gmail.com>
Hi,
> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@gmail.com> wrote:
> > I got a new Intel core-8 i7 processor.
> > I am on kernel uname -a
> > Linux zenogentoo 2.6.35-rc5 #97 SMP Tue Jul 13 16:13:25 CEST 2010 i686
> > Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux
> > Sometimes in the middle of nowhere all of a sudden all of my 8-cores
> > are at 100% CPU usage and my machine really lags and hangs and is not
> > useable anymore. Some random process just grabs a bunch CPUs according
> > to htop.
* Pekka Enberg <penberg@cs.helsinki.fi> [2010-07-14 11:05]:
> Why did you enable CONFIG_DEBUG_KMEMLEAK? Memory leak scanning is
> likely the source of these pauses.
I am seeing the same problem with a Core i7 920 and 2.6.35-rc5, and I do
not have CONFIG_DEBUG_KMEMLEAK enabled, so I think this is not related.
I do not see anything special in the logs, just the load becoming mad
and almost preventing ssh access. I've been seeing that since the first
2.6.35 rc I tested (-rc2 or -rc3, I don't remember) and I did not have
time to report it before but I was surprised nobody else did. No problem
with 2.6.34 and 2.6.34.1.
--
Damien
next prev parent reply other threads:[~2010-07-14 8: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
2010-08-20 9:40 ` Peter Zijlstra
2010-07-14 8:31 ` Damien Wyart [this message]
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=20100714083112.GA4627@brouette \
--to=damien.wyart@free.fr \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--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