Re: Unkillable processes stuck in "D" state running forever
Denis Vlasenko (email@example.com)
Mon, 29 Jul 2002 11:17:24 -0200
On 29 July 2002 05:22, Federico Sevilla III wrote:
> 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?
It is logged by syslog. /var/log/messages if your conf is standard.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/