From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to dump stack for kernel threads
Date: Thu, 26 Jan 2006 21:00:50 -0600 [thread overview]
Message-ID: <43D98CE2.9020700@lwfinger.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0601262214430.27891@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>>In a driver that I am debugging, there is a periodic task that runs every
>>minute. Intermittently, it destructively interrupts some other activity in the
>>driver, but I have not been able to find the section that is not thread-safe. I
>>have included a dump_stack call at the point where the problem is evident, but
>>the current thread is OK. How would I generate a stack dump of the rest of this
>>driver's kernel threads? Dumping all kernel threads would also be OK.
>
>
> Sysrq+T. Behind the jungle, there's a function doing what you want.
>
>
> Jan Engelhardt
Thanks for the tip. It won't work for me from the keyboard but your suggestion got me into a call to
handle_sysrq.
Larry
prev parent reply other threads:[~2006-01-27 3:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 17:45 How to dump stack for kernel threads Larry Finger
2006-01-26 21:15 ` Jan Engelhardt
2006-01-27 3:00 ` Larry Finger [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=43D98CE2.9020700@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=jengelh@linux01.gwdg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).