From: Peter Zijlstra <peterz@infradead.org>
To: Mark Hills <mark@pogo.org.uk>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: cgroup: rmdir() does not complete
Date: Thu, 09 Sep 2010 13:50:17 +0200 [thread overview]
Message-ID: <1284033017.402.8.camel@laptop> (raw)
In-Reply-To: <alpine.NEB.2.01.1009091234230.26366@jrf.vwaro.pbz>
On Thu, 2010-09-09 at 12:36 +0100, Mark Hills wrote:
> I am still finding the problem incredibly hard to reproduce, so I'd like
> to observe as much data as possible from the current case before
> rebooting. If I could capture some kind of stack trace in the kernel for
> the running process that would be great, any suggestions appreciated.
echo l > /proc/sysrq-trigger
another thing you can do is run something like: perf record -gp $pid
which will give you a profile of that task.
next prev parent reply other threads:[~2010-09-09 11:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 15:51 cgroup: rmdir() does not complete Mark Hills
2010-08-27 0:56 ` Daisuke Nishimura
2010-08-27 1:20 ` Balbir Singh
2010-08-27 2:35 ` KAMEZAWA Hiroyuki
2010-08-27 3:39 ` Daisuke Nishimura
2010-08-27 5:42 ` KAMEZAWA Hiroyuki
2010-08-27 6:29 ` KAMEZAWA Hiroyuki
2010-08-30 7:32 ` Balbir Singh
2010-08-30 9:13 ` Mark Hills
2010-09-01 11:10 ` Mark Hills
2010-09-01 23:42 ` KAMEZAWA Hiroyuki
2010-09-02 9:45 ` Mark Hills
2010-09-09 10:01 ` Mark Hills
2010-09-09 10:09 ` Balbir Singh
2010-09-09 11:36 ` Mark Hills
2010-09-09 11:50 ` Peter Zijlstra [this message]
2010-09-09 23:04 ` Mark Hills
2010-09-09 23:43 ` KAMEZAWA Hiroyuki
2010-09-10 2:16 ` KAMEZAWA Hiroyuki
2010-09-10 4:05 ` Daisuke Nishimura
2010-09-10 4:11 ` KAMEZAWA Hiroyuki
2010-09-10 7:28 ` Mark Hills
2010-09-10 7:33 ` KAMEZAWA Hiroyuki
2010-09-10 7:51 ` Mark Hills
2010-08-27 1:25 ` KAMEZAWA Hiroyuki
2010-08-30 9:25 ` 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=1284033017.402.8.camel@laptop \
--to=peterz@infradead.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@pogo.org.uk \
--cc=nishimura@mxp.nes.nec.co.jp \
/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