mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stephen Oberholtzer" <oliverklozoff@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: oliverklozoff@gmail.com
Subject: How to diagnose a process stuck in D state?
Date: Fri, 22 Feb 2008 18:08:34 -0500	[thread overview]
Message-ID: <8abd1bfd0802221508i373d37e7hd6ad7702bde25330@mail.gmail.com> (raw)

First off: I'm not subscribed to the list (I don't think I could
handle the volume), so please make sure you CC me if you reply.

I run an application on one of my machines; it often hangs, with the
process stuck D state.  When this happens, the process sticks around
until I reboot the machine.

I have tried the following to start diagnosing the problem:

* Running 'ps -axl' shows "-" in the wchan column.
* The contents of /proc/pid/wchan say "_stext".
* 'strace -p pid' says "Process pid attached - interrupt to quit" and
stops responding.  Sending SIGINT and SIGTERM have no effect on the
strace process, although kill -11 (SIGSEGV, my personal favorite) does
work.

This is very confusing.  I would greatly appreciate it if someone
could tell me how a process can enter D state without being in a
syscall, and what I can do to start tracking down the cause.

(By the way: This is on amd64, 2.6.23. I'm updating to 2.6.24.2 right
now, on the off chance that whatever was causing the problem has been
fixed.)

-- 
-- Stevie-O
Real programmers use COPY CON PROGRAM.EXE

             reply	other threads:[~2008-02-22 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 23:08 Stephen Oberholtzer [this message]
2008-02-23  0:31 ` Lee Revell
2008-02-23 13:37 Daniel J Blueman

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=8abd1bfd0802221508i373d37e7hd6ad7702bde25330@mail.gmail.com \
    --to=oliverklozoff@gmail.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

all inboxes | Powered by JetHome®