All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Rob Mueller <robm@fastmail.fm>
Cc: Chris Mason <mason@suse.com>, linux-kernel@vger.kernel.org
Subject: Re: Processes stuck in unkillable D state (now seen in 2.6.7-mm6)
Date: Mon, 12 Jul 2004 13:25:25 -0700	[thread overview]
Message-ID: <20040712202525.GJ21066@holomorphy.com> (raw)
In-Reply-To: <00b001c4684c$d060bb20$9aafc742@ROBMHP>

At some point in the past, my attribution was shamelessly removed from:
>> Nice, deep stack there; however, this appears to only be one process. It
>> may be helpful to see the others.

On Mon, Jul 12, 2004 at 01:14:12PM -0700, Rob Mueller wrote:
> I've put the dumps here. I did sysreq-t twice, thus the 2 dumps. If you 
> diff them, you'll see they're very very similar.
> http://robm.fastmail.fm/kernel/t2/

Hmm, I wonder which of the two lock_page()'s in filemap_nopage() this is.


-- wli

  reply	other threads:[~2004-07-12 20:27 UTC|newest]

Thread overview: 10+ 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 [this message]
2004-07-20 19:51     ` Chris Mason
2004-07-20 21:19       ` Rob Mueller
2004-07-15 16:12   ` Processes stuck in unkillable D state (now seen in 2.6.8-rc1) Rob Mueller
  -- strict thread matches above, loose matches on Subject: below --
2004-07-09  9:52 Processes stuck in unkillable D state (now seen in 2.6.7-mm6) Rob Mueller

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=20040712202525.GJ21066@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --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.