All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Rob Mueller <robm@fastmail.fm>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Processes stuck in unkillable D state (2.4 and 2.6)
Date: Wed, 30 Jun 2004 10:12:03 -0400	[thread overview]
Message-ID: <1088604723.1589.1387.camel@watt.suse.com> (raw)
In-Reply-To: <006a01c45de6$e4442930$62afc742@ROBMHP>

On Tue, 2004-06-29 at 10:39, Rob Mueller wrote:
> Over the past several years, we've observed a problem on our email servers 
> (cyrus, postfix, mod_perl) where processes get stuck in an unkillable D 
> state. This has happened to more or less a degree in every kernel we've 
> tried from 2.4.18 up and all the 2.6 series.
> 
Hi, could you please post the full sysrq-t output?

thanks,
Chris



  reply	other threads:[~2004-06-30 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 14:39 Processes stuck in unkillable D state (2.4 and 2.6) Rob Mueller
2004-06-30 14:12 ` Chris Mason [this message]
2004-06-30 14:58   ` Rob Mueller
2004-06-30 16:51     ` Chris Mason
2004-06-30 17:07       ` Rob Mueller
2004-07-04 17:39       ` Marcelo Tosatti
2004-07-05  0:34         ` Processes stuck in unkillable D state (2.4 and 2.6)\ Marcelo Tosatti

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=1088604723.1589.1387.camel@watt.suse.com \
    --to=mason@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robm@fastmail.fm \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.