From: Andrea Arcangeli <aarcange@redhat.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: Ulrich Keller <uhkeller@googlemail.com>,
linux-kernel@vger.kernel.org, Thomas Sattler <tsattler@gmx.de>
Subject: Re: iotop: khugepaged at 99.99% (2.6.38.3)
Date: Wed, 25 May 2011 18:06:59 +0200 [thread overview]
Message-ID: <20110525160659.GE19505@random.random> (raw)
In-Reply-To: <201105232005.56840.johannes.hirte@fem.tu-ilmenau.de>
On Mon, May 23, 2011 at 08:05:55PM +0200, Johannes Hirte wrote:
> Is there any progress on this? I've observed this behavior different times too,
> with kernel 2.6.39-rc7. After a while working some processes (kmail,
> akregator, konqueror) got stuck in D state together with the khugepaged task.
> I could kill the hanging process (kill -n 9) but the khugepaged task stayed in
> D state.
> The system is a Pentium M (Banias) with 1.3GHz and 1.5G RAM. Attached is the
> output from multiple SYSRQ+T, content from /proc/zoneinfo and the config.
great progress thanks to your info.
nr_isolated_file 4294967295
0xffffffff
I didn't check all data you provided yet but the critical bit is we're
off by one in nr_isolated_file and that's the bug, looks unrelated to
anon memory and THP. I'm reviewing more but I recommend everyone to
check this nr_isolated_file code, hoping it's not random memory
corruption. Why it only happened on 32bit so far is unclear though,
you're 32bit too. I doubt it's an overflow, the value is unsigned too,
so it has to be an underflow and that should have happened on 64bit
too in theory.
You and Ulrich both have PREEMPT=y so it may be a preempt bug. What
about you Thomas, do you have PREEMPT=y too?
next prev parent reply other threads:[~2011-05-25 16:07 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
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 [this message]
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=20110525160659.GE19505@random.random \
--to=aarcange@redhat.com \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tsattler@gmx.de \
--cc=uhkeller@googlemail.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