From: Andrew Morton <akpm@digeo.com>
To: Jeff Dike <jdike@karaya.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-rc1 - hang with processes stuck in D
Date: Tue, 05 Nov 2002 16:37:47 -0800 [thread overview]
Message-ID: <3DC8645B.A0E99A99@digeo.com> (raw)
In-Reply-To: 200211060025.gA60P6V01413@karaya.com
Jeff Dike wrote:
>
> 2.4.20-rc1 reliably gets processes stuck in D, eventually wedging the whole
> system. This is by diffing two kernel pools, one of which has 9 138764288
> byte core files.
>
> The diff itself is stuck in __wait_on_buffer:
>
> Trace; c0131608 <__wait_on_buffer+68/90>
Kernel is waiting for IO completion on a read. I would be
suspecting your IO system, or interrupt system.
Reverting your ide/scsi/whatever drivers to the last-known-to-work
version would be interesting.
next prev parent reply other threads:[~2002-11-06 0:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 0:25 2.4.20-rc1 - hang with processes stuck in D Jeff Dike
2002-11-06 0:37 ` Andrew Morton [this message]
2002-11-06 3:08 ` Jeff Dike
2002-11-08 4:17 ` Jakob Oestergaard
2002-11-08 18:43 ` Trond Myklebust
2002-11-09 22:39 ` Jakob Oestergaard
2002-11-08 9:01 ` Marcelo Tosatti
2002-11-10 21:22 ` Jeff Dike
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=3DC8645B.A0E99A99@digeo.com \
--to=akpm@digeo.com \
--cc=jdike@karaya.com \
--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