From: David Miller <davem@davemloft.net>
To: cebbert@redhat.com
Cc: jeff@garzik.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [2.6.23] tasks stuck in running state?
Date: Sun, 21 Oct 2007 12:52:40 -0700 (PDT) [thread overview]
Message-ID: <20071021.125240.23398793.davem@davemloft.net> (raw)
In-Reply-To: <471B7752.7050306@redhat.com>
From: Chuck Ebbert <cebbert@redhat.com>
Date: Sun, 21 Oct 2007 11:59:14 -0400
> IIRC -mm had something like this but it was buggy because we were
> sending IPIs to each processor asking them to print their state.
What's buggy about this? :-) That's exactly how it work(ed)
on sparc64.
next prev parent reply other threads:[~2007-10-21 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 21:39 [2.6.23] tasks stuck in running state? 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
2007-10-21 15:59 ` Chuck Ebbert
2007-10-21 19:52 ` David Miller [this message]
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=20071021.125240.23398793.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--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