From: Thomas Sattler <tsattler@gmx.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Kelly Anderson <kelly@silka.with-linux.com>
Subject: Re: 2.6.38.x: system hangs, iowait ~75, no resource-hogs, no logs
Date: Wed, 13 Apr 2011 00:37:51 +0200 [thread overview]
Message-ID: <4DA4D43F.1080205@gmx.de> (raw)
In-Reply-To: <4D9E4546.3090407@silka.with-linux.com>
On 04/08/11 01:14, Kelly Anderson wrote:
> Try the patch found in "Linux 2.6.38 freeze because of
> sound/core/pcm_lib.c commit"
I applied https://lkml.org/lkml/diff/2011/4/1/69/1 but that
did not (completely?) solve my problem:
While running firefox (>50 open Tabs), khugepaged suddenly
run at 99.99% IO (according to 'iotop'). X became unusable
within seconds, but the system itself was still running.
I was able to switch to tty1 where everything was quite
normal, except khugepaged beeing constantly above 90%.
Switching back to X showed a frozen windowmanager with
empty windows. Back to tty1 I was able to kill X and
start a new X session, which behaved as usual.
khugepaged kept the system busy for another 10min so I
rebooted the machine. (This time there was no problem
running 'pkill' and 'iotop' several times.)
My current kernel is configured like this:
$ zgrep HUGE /proc/config.gz
CONFIG_TRANSPARENT_HUGEPAGE=y
CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
** Please CC: me, as I'm not on the list. **
Thomas
prev parent reply other threads:[~2011-04-12 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 22:21 2.6.38.x: system hangs, iowait ~75, no resource-hogs, no logs Thomas Sattler
2011-04-07 23:14 ` Kelly Anderson
2011-04-12 22:37 ` Thomas Sattler [this message]
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=4DA4D43F.1080205@gmx.de \
--to=tsattler@gmx.de \
--cc=kelly@silka.with-linux.com \
--cc=linux-kernel@vger.kernel.org \
/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