From: Gilles Hamel <hamelg@laposte.net>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Ulrich Keller <uhkeller@googlemail.com>,
linux-kernel@vger.kernel.org, Thomas Sattler <tsattler@gmx.de>,
Gilles Hamel <hamelg@laposte.net>
Subject: Re: iotop: khugepaged at 99.99% (2.6.38.3)
Date: Wed, 01 Jun 2011 21:37:48 +0200 [thread overview]
Message-ID: <4DE6950C.3030500@laposte.net> (raw)
In-Reply-To: <20110512140352.GG11579@random.random>
On 12/05/2011 16:03, Andrea Arcangeli wrote:
> On Wed, May 11, 2011 at 10:53:18AM +0000, Ulrich Keller wrote:
>> I am seeing exactly the same symptoms on my Lenovo T60 Core2 duo, 3GB RAM,
>> running Arch Linux i686 with Kernel 2.6.38.6. When I've heavily used Firefox for
>> a while, or used R with high memory usage (>1 GB), individual applications
>> become unresponsive, new processes fail to start and after a while the whole
>> system freezes. When it happens, iotop shows khugepaged and sometimes firefox at
>> 99.99%.
> SYSRQ+T run multiple times during the hang and /proc/zoneinfo as well
> run multiple times during the hang is the best info we can have for
> now, /proc/zoneinfo is the most interesting as it will show us the
> values that the too_many_isolated loop is checking to decide if to
> continue looping.
Me too :(
Since running 2.6.38, it was happening only 3 times on the same process
(convert from the ImageMagick toolkit). The last time I'm running 2.6.38.7.
This process is launched every 15 minutes by crond, like this :
*/15 * * * * convert -delay 50
http://www.meteo60.org/radars/radar-nord-picardie-idf{-90,-90,-90,-75,-60,-45,-30,-15,,,}.png
-loop 0 $HOME/temp/radar-pluie.gif >/dev/null 2>&1
*/15 * * * * convert -delay 50
http://www.sat24.com/image.ashx\?ok=1\&country=fr\&type=slide\&time=\&index={9,9,9,8,7,6,5,4,3,2,1,1,1}\&sat=vis
-loop 0 $HOME/temp/radar-nuage.gif >/dev/null 2>&1
When it's happen, I'm using firefox. Here, the whole system continues
functioning normally a moment, then the X server hangs. Only these 3
tasks was stuck at 99% io busy in iotop :
$ iotop -ob
Total DISK READ: 0.00 B/s | Total DISK WRITE: 0.00 B/s
TID PRIO USER DISK READ DISK WRITE SWAPIN IO COMMAND
Total DISK READ: 0.00 B/s | Total DISK WRITE: 0.00 B/s
TID PRIO USER DISK READ DISK WRITE SWAPIN IO COMMAND
26 be/7 root 0.00 B/s 0.00 B/s 0.00 % 96.84 % [khugepaged]
22839 be/4 hamelg 0.00 B/s 0.00 B/s 0.00 % 96.84 % convert
-delay 50 http://www.meteo60....
22841 be/4 hamelg 0.00 B/s 0.00 B/s 0.00 % 96.84 % convert
-delay 50 http://www.sat24....
Total DISK READ: 0.00 B/s | Total DISK WRITE: 0.00 B/s
TID PRIO USER DISK READ DISK WRITE SWAPIN IO COMMAND
22839 be/4 hamelg 0.00 B/s 0.00 B/s 0.00 % 99.99 % convert
-delay 50 http://www.meteo60...
26 be/7 root 0.00 B/s 0.00 B/s 0.00 % 99.99 % [khugepaged]
22841 be/4 hamelg 0.00 B/s 0.00 B/s 0.00 % 99.99 % convert
-delay 50 http://www.sat24...
...
Before rebooting, I followed your hints. You'll find the output of
multiple SYSRQ+T, /proc/zoneinfo and ps axu and my config.gz :
http://gilles.hamel.free.fr/config.gz
http://gilles.hamel.free.fr/typescript
http://gilles.hamel.free.fr/sysrq+t.txt
I hope these additional clues will help you to hunt this bug.
Regards
next prev parent reply other threads:[~2011-06-01 19:45 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
2011-05-25 20:44 ` Thomas Sattler
2011-06-01 19:37 ` Gilles Hamel [this message]
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=4DE6950C.3030500@laposte.net \
--to=hamelg@laposte.net \
--cc=aarcange@redhat.com \
--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