From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Brad Fitzpatrick <brad@danga.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9: unkillable processes during heavy IO
Date: Sun, 14 Nov 2004 21:41:05 +0000 [thread overview]
Message-ID: <1100468463.25613.0.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0411141403040.22805@danga.com>
On Sul, 2004-11-14 at 22:15, Brad Fitzpatrick wrote:
> Next time it hangs like this, how can I get a kernel backtrace or other useful information
> for a certain process?
See what is in dmesg and /var/log/messages. Use ps to get the waitqueue
of the
stuck processes (see man ps)
next prev parent reply other threads:[~2004-11-14 22:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 22:15 2.6.9: unkillable processes during heavy IO Brad Fitzpatrick
2004-11-14 21:41 ` Alan Cox [this message]
2004-11-14 22:30 ` Andrew Morton
2004-11-14 22:45 ` Andries Brouwer
2004-11-15 7:39 ` Lenar Lõhmus
2004-11-16 13:56 ` Brad Fitzpatrick
2004-11-17 4:01 ` Andrew Morton
2004-11-17 4:55 ` Nathan Scott
2004-11-17 7:00 ` Brad Fitzpatrick
2004-11-18 5:05 ` Nathan Scott
2004-11-19 4:59 ` Nathan Scott
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=1100468463.25613.0.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=brad@danga.com \
--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).