From: David Miller <davem@davemloft.net>
To: cebbert@redhat.com
Cc: jeff@garzik.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.23] tasks stuck in running state?
Date: Fri, 19 Oct 2007 17:01:40 -0700 (PDT) [thread overview]
Message-ID: <20071019.170140.45897518.davem@davemloft.net> (raw)
In-Reply-To: <47192D20.8090608@redhat.com>
From: Chuck Ebbert <cebbert@redhat.com>
Date: Fri, 19 Oct 2007 18:18:08 -0400
> On 10/19/2007 06:03 PM, Jeff Garzik wrote:
> >> [jgarzik@pretzel misc-2.6]$ strace -p8484
> >> Process 8484 attached - interrupt to quit
> > [sits there, chewing up CPU grepping a 47-line header file]
> >
>
> And sysrq-p is pretty useless unless you can force the keyboard
> interrupt and the spinning process onto the same CPU.
Yes, I find this a painful limitation too.
Sparc64 used to dump the registers on all active cpus for show_regs()
via a cross-call, and this was incredibly useful. But I disabled that
as soon as I started playing with Niagara because at 32 cpus and
larger the output is just too voluminous to be useful.
What might be appropriate is just to get a one-line program counter
dump on every cpu via some new sysrq keystroke.
next prev parent reply other threads:[~2007-10-20 0:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 21:39 Jeff Garzik
2007-10-19 21:53 ` Chuck Ebbert
2007-10-19 22:03 ` Jeff Garzik
2007-10-19 22:18 ` Chuck Ebbert
2007-10-20 0:01 ` David Miller [this message]
2007-10-21 15:59 ` Chuck Ebbert
2007-10-21 19:52 ` David Miller
2007-10-21 17:25 ` Dmitry Adamushko
2007-10-21 17:34 ` Dmitry Adamushko
2007-10-20 1:08 ` Ray Lee
2007-10-21 20:11 ` ext3 deadlock or " Guennadi Liakhovetski
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=20071019.170140.45897518.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cebbert@redhat.com \
--cc=jeff@garzik.org \
--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
all inboxes | Powered by JetHome®