mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Mueller" <robm@fastmail.fm>
To: "Chris Mason" <mason@suse.com>,
	"William Lee Irwin III" <wli@holomorphy.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Processes stuck in unkillable D state (now seen in 2.6.8-rc1)
Date: Thu, 15 Jul 2004 09:12:13 -0700	[thread overview]
Message-ID: <006801c46a86$81234230$9aafc742@ROBMHP> (raw)
In-Reply-To: <1089377936.3956.148.camel@watt.suse.com>

I upgraded the kernel on a couple of the machines to 2.6.8-rc1 (compiled 
with debug symbols), but now we've seen two completely different types of 
failures

1. The same as the old one, where a couple of processes (half dozen in this 
case) would get stuck in D state, but the machine was otherwise pretty much 
fine
2. A new one where over 1000 processes get stuck within a short period of 
time and leave the machine is a very fragile state (even attempts to run 
'ps -auxw' freeze up)

I've placed all the results here:

http://robm.fastmail.fm/kernel/t3/

sysreqdmesg1-s1.txt - output of sysreq-t for system with a few procs in D 
state
sysreqdmesg2-s1.txt - same again, just done a second time
sysreqdmesg1-s2.txt - output of sysreq-t for system with 1000 procs in D 
state
vmlinux.gz - kernel image, built with debug symbols
config - config used to compile the kernel

Is there anything else I can provide? This problem is driving us crazy and 
I'd like to help in any way possible to try and get it investigated and 
resolved.

Rob


      parent reply	other threads:[~2004-07-15 16:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08 22:15 Processes stuck in unkillable D state (now seen in 2.6.7-mm6) Rob Mueller
2004-07-09 12:58 ` Chris Mason
2004-07-12 19:53   ` Rob Mueller
2004-07-12 20:11     ` William Lee Irwin III
2004-07-12 20:14       ` Rob Mueller
2004-07-12 20:25         ` William Lee Irwin III
2004-07-20 19:51     ` Chris Mason
2004-07-20 21:19       ` Rob Mueller
2004-07-15 16:12   ` Rob Mueller [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='006801c46a86$81234230$9aafc742@ROBMHP' \
    --to=robm@fastmail.fm \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=wli@holomorphy.com \
    /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

Powered by JetHome