From: Dave Jones <davej@codemonkey.org.uk>
To: Andrew Morton <akpm@digeo.com>
Cc: Patrick Mau <mau@oscar.ping.de>, linux-kernel@vger.kernel.org
Subject: Re: pdflush in D state
Date: Thu, 6 Feb 2003 12:37:51 +0000 [thread overview]
Message-ID: <20030206123751.GB3305@codemonkey.org.uk> (raw)
In-Reply-To: <20030205234139.237887a7.akpm@digeo.com>
On Wed, Feb 05, 2003 at 11:41:39PM -0800, Andrew Morton wrote:
> At a guess, I'd say that a disk device driver has dropped an interrupt and
> I/O completion has not happened.
>
> Check your kernel log and dmesg output for anything untoward, and then try
> invoking sysrq-P and sysrq-T to find out where everythihg is stuck.
Unrelated to this problem, but it reminded me...
I've not heard any compelling arguments saying that these[1] patches
are wrong.
Dave
[1] http://www.uwsg.iu.edu/hypermail/linux/kernel/0301.1/2217.html
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2003-02-06 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 23:12 pdflush in D state Patrick Mau
2003-02-06 7:41 ` Andrew Morton
2003-02-06 12:37 ` Dave Jones [this message]
2003-02-06 18:07 ` Robert Love
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=20030206123751.GB3305@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mau@oscar.ping.de \
/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