From: Bernd Schubert <bs@q-leap.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysrq+t doesn't work for some threads
Date: Mon, 4 Aug 2008 21:51:24 +0200 [thread overview]
Message-ID: <200808042151.25342.bs@q-leap.de> (raw)
In-Reply-To: <48975C96.9090401@shaw.ca>
On Monday 04 August 2008 21:46:30 Robert Hancock wrote:
> Bernd Schubert wrote:
> > Hello,
> >
> > I need to debug a lustre problem, where lustre threads take 100% cpu time
> > and also have a memory leak. The problem is, that sysrq+t doesn't work
> > for these threads. It nicely shows all stack traces, just the trouble
> > some threads won't show their traces:
> >
> > [69338.858825] ll_mdt_36 R running task 0 21679 2 (L-TLB)
>
> This means this task is running, you won't get a stack trace for such a
> thread. You'd likely have to stop it somehow. Is this a kernel thread?
Yes, it is a kernel thread. How can I stop it? Is there a way to stop kernel
threads at all? kill -STOP doesn't work.
Thanks,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
next prev parent reply other threads:[~2008-08-04 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.sh1LseUiXeu++640VETUX2tdFMs@ifi.uio.no>
2008-08-04 19:46 ` sysrq+t doesn't work for some threads Robert Hancock
2008-08-04 19:51 ` Bernd Schubert [this message]
2008-08-04 12:47 Bernd Schubert
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=200808042151.25342.bs@q-leap.de \
--to=bs@q-leap.de \
--cc=hancockr@shaw.ca \
--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