Re: Unkillable processes stuck in "D" state running forever

[Federico Sevilla III <jijo@free.net.ph>]

On Sun, Jul 28, 2002 at 04:09:33PM -0200, Denis Vlasenko wrote:
> D state processes are sitting in kernel code waiting for something to
> happen. It is ok to sit in D state for milliseconds, it is acceptable
> to sit for seconds. If those processes are stuck forever, it's a bug.

The processes I refer to get stuck in D state forever. I have other
processes that are in D state legitimately, and for reasonable amounts
of time depending on the task, but it is only these random processes
that occur once in awhile that stay there forever and drive the load
levels way beyond their normal levels.

> Capture Alt-SysRq-T output and ksymoops relevant part Yes it means you
> should have ksymoops installed and tested, which is easy to get wrong.
> I've done that too often.

It also requires access the console, right? Or is it possible to get a
similar task information dump when logged on remotely via SSH? I have
ksymoops working and tested on both of these systems, and console access
to one of them. It would be great to know what to do to help the kernel
hackers figure out what's going on as soon as the next stuck process
shows up.

 --> Jijo

-- 
Federico Sevilla III   :  <http://jijo.free.net.ph/>
Network Administrator  :  The Leather Collection, Inc.
GnuPG Key ID           :  0x93B746BE