From: Andrea Arcangeli <aarcange@redhat.com>
To: Thomas Sattler <tsattler@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mel Gorman <mel@csn.ul.ie>
Subject: Re: iotop: khugepaged at 99.99% (2.6.38.X)
Date: Fri, 6 May 2011 19:55:48 +0200 [thread overview]
Message-ID: <20110506175548.GE6330@random.random> (raw)
In-Reply-To: <4DC3B629.7010409@gmx.de>
On Fri, May 06, 2011 at 10:49:45AM +0200, Thomas Sattler wrote:
> > You can already run "grep threshold /proc/zoneinfo" on the system
> > where you reproduced the hang the last time (the one running 2.6.38.4)
> > the one with 1.5G of ram. They all should be well below 512 (so in
> > theory not causing troubles because of the per-cpu stats, and with so
> > few cpus it shouldn't have been such a longstanding problem anyway).
>
> 'grep threshold /proc/zoneinfo' returns nothing on this machine after
> a reboot and before a crash. Did I tell it's a single core machine?
Hmm single core machine doesn't seem to fit my theory of per-cpu stats
too well... I think it's not impossible but it should only be possible
on smp and maybe it's not reproducible and probably not what you're
dealing with.
The new make-it-worse-patch should help to reproduce though.
If you can "cat /proc/zoneinfo" _during_ the hang (and then run
sysrq+t again to see the status, no need of sysrq+l), it'll help to
try to track this down. I'll recheck your last sysrq+t once again to
see if I get other ideas.
A 'cat /proc/zoneinfo' after the hang resolves itself and the system
is mostly idle, will also be interesting to verify the nr_isolated_*
are all zero.
Thanks,
Andrea
next prev parent reply other threads:[~2011-05-06 17:56 UTC|newest]
Thread overview: 23+ 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
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 [this message]
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
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=20110506175548.GE6330@random.random \
--to=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--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.