From: Mark Hills <mark@xwax.org>
To: linux-mm@kvack.org
Subject: ps lockups, cgroup memory reclaim
Date: Tue, 17 Sep 2013 16:50:42 +0100 (BST) [thread overview]
Message-ID: <1309171621250.11844@wes.ijneb.com> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1497 bytes --]
I'm investigating intermitten kernel lockups in an HPC environment, with
the RedHat kernel.
The symptoms are seen as lockups of multiple ps commands, with one
consuming full CPU:
# ps aux | grep ps
root 19557 68.9 0.0 108100 908 ? D Sep16 1045:37 ps --ppid 1 -o args=
root 19871 0.0 0.0 108100 908 ? D Sep16 0:00 ps --ppid 1 -o args=
SIGKILL on the busy one causes the other ps processes to run to completion
(TERM has no effect).
In this case I was able to run my own ps to see the process list, but not
always.
perf shows the locality of the spinning, roughly:
proc_pid_cmdline
get_user_pages
handle_mm_fault
mem_cgroup_try_charge_swapin
mem_cgroup_reclaim
There are two entry points, the codepaths taken are better shown by the
attached profile of CPU time.
We've had this behaviour since switching to Scientific Linux 6 (based on
RHEL6, like CentOS) at kernel 2.6.32-279.9.1.el6.x86_64.
The example above is kernel 2.6.32-358.el6.x86_64.
I haven't been able to get a re-producable case with which to test the
mainline kernel; our large-scale automated use of ps is working as a
fuzz-test and switching kernels like that is not an option unfortunately.
Does this issue sound familiar? I'd appreciate any advice or information,
or pointers to the mainline where such cases have been investigated.
I could not find anything using Google, but this problem does not have an
key word or error message.
Many thanks
--
Mark
[-- Attachment #2: Type: APPLICATION/PDF, Size: 31913 bytes --]
next reply other threads:[~2013-09-17 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 15:50 Mark Hills [this message]
2013-09-17 16:28 ` Johannes Weiner
2013-09-18 0:50 ` Mark Hills
2013-10-24 17:39 ` Mark Hills
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=1309171621250.11844@wes.ijneb.com \
--to=mark@xwax.org \
--cc=linux-mm@kvack.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