From: Andrea Arcangeli <aarcange@redhat.com>
To: Thomas Sattler <tsattler@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: iotop: khugepaged at 99.99% (2.6.38.3)
Date: Wed, 4 May 2011 16:38:42 +0200 [thread overview]
Message-ID: <20110504143842.GK7838@random.random> (raw)
In-Reply-To: <4DC14474.9040001@gmx.de>
Hello Thomas,
On Wed, May 04, 2011 at 02:20:04PM +0200, Thomas Sattler wrote:
> Different machine (kernel 2.6.38.2) 4x SYSRQ+l
>
> http://pastebin.com/raw.php?i=B2XeVyz6
> (URL should be valid for one month)
>
> Since this is a DualCore machine, it is still
> quite usable. I'll try to keep it running, in
> case you need more details.
>
> BTW: I haven't seen the problem with 2.6.38.4
> so far. May have been fixed in the meantime?
There's no sign of khugepaged in the traces :( and one of the two cpu
is always idle (the other is often idle too). Maybe khugepaged was
stuck in D state and that is shown as 100% load for iotop? Please next
time can you run SYSRQ+t too in addition of SYSRQ+l? (I should have
suggested it right away but I thought khugepaged was running at 100%
cpu load and sysrq+t wouldn't have been as interesting in that
case). You can run also a "ps xal" to see the actual scheduler task
state. I suggest to stay at .2 if it reproduces it more easily.
If we understand what it is, it'll be easy to tell if it was already
fixed in 2.6.38.4 but I doubt unless it's not related to MM.
Thanks a lot for the help,
Andrea
next prev parent reply other threads:[~2011-05-04 14:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 23:28 iotop: khugepaged at 99.99% (2.6.38.3) Thomas Sattler
2011-04-27 13:46 ` Andrea Arcangeli
2011-05-04 12:20 ` Thomas Sattler
2011-05-04 12:37 ` Thomas Sattler
2011-05-04 14:38 ` Andrea Arcangeli [this message]
2011-05-05 13:08 ` Thomas Sattler
2011-05-05 22:04 ` iotop: khugepaged at 99.99% (2.6.38.X) Thomas Sattler
2011-05-06 1:13 ` Andrea Arcangeli
2011-05-06 6:35 ` Andrea Arcangeli
2011-05-06 8:49 ` Thomas Sattler
2011-05-06 8:54 ` Thomas Sattler
2011-05-06 14:24 ` Thomas Sattler
2011-05-06 17:20 ` Andrea Arcangeli
2011-05-06 17:55 ` Andrea Arcangeli
2011-05-11 10:53 ` iotop: khugepaged at 99.99% (2.6.38.3) Ulrich Keller
2011-05-12 14:03 ` Andrea Arcangeli
2011-05-16 9:27 ` Ulrich Keller
2011-05-16 12:29 ` Ulrich Keller
2011-05-23 18:05 ` Johannes Hirte
2011-05-25 16:06 ` Andrea Arcangeli
2011-05-25 20:44 ` Thomas Sattler
2011-06-01 19:37 ` Gilles Hamel
2011-06-13 10:28 ` Antonio Messina
[not found] <fa.FZDTDqnxL4JfQvyaCQTn405rzwM@ifi.uio.no>
2011-09-14 12:57 ` Slawomir Czarko-Wasiutycz
2011-09-14 13:32 ` Slawomir Czarko-Wasiutycz
2011-09-15 6:43 ` Lin Ming
2011-09-15 6:48 ` Lin Ming
2011-09-15 7:24 ` Thomas Sattler
2011-09-15 7:50 ` Lin Ming
2011-09-19 17:51 ` Andrea Arcangeli
2011-09-20 13:19 ` Slawomir Czarko-Wasiutycz
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=20110504143842.GK7838@random.random \
--to=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tsattler@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.