mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Hammers <ch@lathspell.de>
To: <linux-kernel@vger.kernel.org>
Subject: Debugging process hanging in D status and not responding to SIGKILL
Date: Fri, 21 Dec 2007 16:38:45 +0100	[thread overview]
Message-ID: <20071221163845.6fa3f2a9@sys-251.netcologne.de> (raw)

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?

The system:
	Kernel: 2.6.22-3-amd64 (modified by Debian distribution)
	CPU: Quad Dualcore Intel(R) Xeon(R) E5310  @ 1.60GHz, 8GB RAM
	M/B: Transtec Server with Intel 5000 Series Chipset
	SCSI: 3ware Inc 9550SX SATA-RAID with firmware FE9X 3.08.00.016

bye,

-christian-

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

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

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=20071221163845.6fa3f2a9@sys-251.netcologne.de \
    --to=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®