From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Mike Galbraith <bitbucket@online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.13.5 : rm -rf running forever, one cpu at approx 100%
Date: Thu, 27 Feb 2014 03:45:35 +0000 [thread overview]
Message-ID: <20140227034535.GC14346@milliways> (raw)
In-Reply-To: <1393471595.5519.22.camel@marge.simpson.net>
On Thu, Feb 27, 2014 at 04:26:35AM +0100, Mike Galbraith wrote:
>
> I would start with strace to see if a task is looping in userspace, then
> move on to perf top -g -p <pid> (or perf record/report) to peek at what
> it's up to in the kernel. Once you have the where, trace_printk() is
> the best thing since sliced bread (which ranks just below printk()).
>
> -Mike
Thanks. I'll need to build perf.
ĸen
--
das eine Mal als Tragödie, dieses Mal als Farce
next prev parent reply other threads:[~2014-02-27 3:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 0:52 3.13.5 : rm -rf running forever, one cpu at approx 100% Ken Moffat
2014-02-27 1:28 ` Gene Heskett
2014-02-27 1:47 ` Ken Moffat
2014-02-27 1:57 ` Gene Heskett
2014-02-27 3:26 ` Mike Galbraith
2014-02-27 3:45 ` Ken Moffat [this message]
2014-02-27 4:19 ` Gene Heskett
2014-02-27 4:52 ` Mike Galbraith
2014-02-27 11:30 ` Gene Heskett
2014-03-03 21:16 ` Ken Moffat
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=20140227034535.GC14346@milliways \
--to=zarniwhoop@ntlworld.com \
--cc=bitbucket@online.de \
--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 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.