Re: Debugging process hanging in D status and not responding to SIGKILL

["Ray Lee" <ray-lk@madrabbit.org>]

On Dec 21, 2007 7:38 AM, Christian Hammers <ch@lathspell.de> wrote:
> Hello
>
> Occasionally all my apache2 processes hang in "D" process status where they are
> no longer responsible to SIGKILL which makes the server almost un-rebootable.
> The processes usually vanish after about 15-30min.
>
> I know that this usually means "I/O wait" somewhere deep inside a kernel
> function where signals are not handled.
>
> But using "strace -p <pid>" I can only see that the last called function is
> flock() (according to /proc/<pid>/fd somebody produced a deadlock when using
> PHP sessions). But flock() normally terminates on SIGTERM and SIGKILL.
>
> Could it be a problem with my SCSI driver who's involed in the flock process?
> The problem usually occurs on two other webserver at the same time, one using
> the same hardware and one being a Dell 6850 with Dell PERC RAID, though.
>
> How can I get further debugging information that could give me a hint?

Do an

   echo t >/proc/sysrq-trigger

and see what it shows.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/