Discussion:
How to kill process in state "D" uninterruptible sleep
(too old to reply)
Sally Shears
2003-10-02 00:43:21 UTC
Permalink
I have a process that shows in ps aux as state "D". I cannot kill it.

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 29755 0.0 1.7 8168 4484 ? D Sep29 0:00 tethereal

man ps tells me that "D" is "uninterruptible sleep."

How can I kill this process?

kill -9 29755

..doesn't kill it.

-- Sally
--
Sally Shears (a.k.a. "Molly")
***@theWorld.com -or- ***@Shears.org
http://theWorld.com/~sshears
o***@yqxcte.com
2003-10-02 01:21:06 UTC
Permalink
|I have a process that shows in ps aux as state "D". I cannot kill it.
|
|USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
|root 29755 0.0 1.7 8168 4484 ? D Sep29 0:00 tethereal
|
|man ps tells me that "D" is "uninterruptible sleep."
|
|How can I kill this process?

Generally you can't, it's waiting for some I/O event, like a disk
operation completion. It's sometimes a symptom of bad hardware.
Sometimes you can provoke the hardware to abort, e.g. if writing to a
floppy, eject the floppy.
--
Sally Shears
2003-10-02 01:51:26 UTC
Permalink
Post by o***@yqxcte.com
|I have a process that shows in ps aux as state "D". I cannot kill it.
|
|USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
|root 29755 0.0 1.7 8168 4484 ? D Sep29 0:00 tethereal
|
|man ps tells me that "D" is "uninterruptible sleep."
|
|How can I kill this process?
Generally you can't, it's waiting for some I/O event, like a disk
operation completion. It's sometimes a symptom of bad hardware.
Sometimes you can provoke the hardware to abort, e.g. if writing to a
floppy, eject the floppy.
I created this when I launched tethereal with no arguements...

What am I left to do? Reboot? Or is there any downside if I just leave
the process sleeping permanently?

-- Sally
--
Sally Shears (a.k.a. "Molly")
***@theWorld.com -or- ***@Shears.org
http://theWorld.com/~sshears
e***@htdfty.com
2003-10-02 01:59:52 UTC
Permalink
|> |man ps tells me that "D" is "uninterruptible sleep."
|> |
|> |How can I kill this process?
|>
|> Generally you can't, it's waiting for some I/O event, like a disk
|> operation completion. It's sometimes a symptom of bad hardware.
|> Sometimes you can provoke the hardware to abort, e.g. if writing to a
|> floppy, eject the floppy.
|
|I created this when I launched tethereal with no arguements...
|
|What am I left to do? Reboot? Or is there any downside if I just leave
|the process sleeping permanently?

I don't know why it's like that, I don't see anything special about
tethereal that would cause this. If you start another tethereal what
happens? Another process in D state? Are there any messages in the log
about disk errors?
--
Roland Schulte-Osthoff
2003-10-02 07:28:27 UTC
Permalink
Post by Sally Shears
What am I left to do? Reboot? Or is there any downside if I just
leave the process sleeping permanently?
These processes are also called zombies.

Look at this short explanation:
<http://www.linuxsa.org.au/tips/zombies.html>

For more Information try to google with "kill zombies"

HTH
Roland
o***@ojpqkl.com
2003-10-02 07:56:26 UTC
Permalink
|> What am I left to do? Reboot? Or is there any downside if I just
|> leave the process sleeping permanently?
|
|These processes are also called zombies.

Ahh...no. Zombies are denoted by Z in the ps output, not D as the OP
posted. Zombies are already dead, only not collected yet. Different
situation.
--
Kevin & Theresa Miller
2003-10-02 04:04:30 UTC
Permalink
Post by Sally Shears
I have a process that shows in ps aux as state "D". I cannot kill it.
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 29755 0.0 1.7 8168 4484 ? D Sep29 0:00 tethereal
man ps tells me that "D" is "uninterruptible sleep."
How can I kill this process?
kill -9 29755
..doesn't kill it.
-- Sally
reboot?
--
Kevin & Theresa Miller
Juneau, Alaska
http://www.alaska.net/~atftb
mjt
2003-10-02 17:24:20 UTC
Permalink
Post by Sally Shears
man ps tells me that "D" is "uninterruptible sleep."
How can I kill this process?
... as a rule, you cant (even root). this process is waiting
for some i/o operation to complete. if there is faulty h/w
it is waiting on, then this process may never return

drop to runlevel 1 and see if it's still there; if not,
then return to your 'default' runlevel, which i suspect
is either 3 or 5
.
--
/// Michael J. Tobler: motorcyclist, surfer, skydiver, \\\
\\\ and author: "Inside Linux", "C++ HowTo", "C++ Unleashed" ///
\\\ http://pages.sbcglobal.net/mtobler/mjt_linux_page.html ///
A jury consists of 12 persons chosen to decide who has the
better lawyer. - Robert Frost
Loading...