mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Christian Hammers" <ch@lathspell.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Debugging process hanging in D status and not responding to SIGKILL
Date: Fri, 21 Dec 2007 08:18:50 -0800	[thread overview]
Message-ID: <2c0942db0712210818q1a16291au3b3ddf395867542a@mail.gmail.com> (raw)
In-Reply-To: <20071221163845.6fa3f2a9@sys-251.netcologne.de>

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.

      reply	other threads:[~2007-12-21 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 15:38 Christian Hammers
2007-12-21 16:18 ` Ray Lee [this message]

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=2c0942db0712210818q1a16291au3b3ddf395867542a@mail.gmail.com \
    --to=ray-lk@madrabbit.org \
    --cc=ch@lathspell.de \
    --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®