From: Fengguang Wu <wfg@mail.ustc.edu.cn>
To: Florin Iucha <florin@iucha.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
Date: Tue, 30 Oct 2007 19:49:41 +0800 [thread overview]
Message-ID: <393744987.14537@ustc.edu.cn> (raw)
Message-ID: <E1ImpbK-0000l3-1u@localhost> (raw)
In-Reply-To: <20071030114250.GL25561@iucha.net>
On Tue, Oct 30, 2007 at 06:42:50AM -0500, Florin Iucha wrote:
> On Tue, Oct 30, 2007 at 03:54:03PM +0800, Fengguang Wu wrote:
> > It could be triggered by the more aggressive writeback behavior - the
> > new code will keep on retrying as long as there are dirty inodes pending.
> >
> > Florin, would you try the attached patches against 2.6.24-git?
> > They may generate big traffic of printk messages, but will help
> > debug the problem.
>
> I have updated to v2.6.24-rc1-334-g82798a1. After using my computer
> for two hours, I left the computer idle overnight. This morning,
> pdflushd is again consuming 25% of a CPU. I will try Fengguang's
> patches today.
Thank you.
Be sure to stop klogd ;-)
A `dmesg` will be sufficient for debugging.
btw, I cannot reproduce it with simple NFSv3 tests.
Fengguang
next prev parent reply other threads:[~2007-10-30 11:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 15:24 pdflush stuck in D state with v2.6.24-rc1-192-gef49c32 Florin Iucha
2007-10-29 13:46 ` Trond Myklebust
2007-10-29 15:01 ` Florin Iucha
2007-10-29 18:43 ` Trond Myklebust
2007-10-29 18:48 ` Florin Iucha
[not found] ` <E1ImlvH-0003YH-Qf@localhost>
2007-10-30 7:54 ` Fengguang Wu
2007-10-30 11:42 ` Florin Iucha
[not found] ` <E1ImpbK-0000l3-1u@localhost>
2007-10-30 11:49 ` Fengguang Wu [this message]
2007-10-30 11:55 ` Florin Iucha
2007-10-31 0:02 ` Florin Iucha
2007-10-31 3:52 ` Florin Iucha
[not found] ` <E1In7S9-0001rv-NO@localhost>
2007-10-31 6:53 ` Fengguang Wu
2007-10-31 12:16 ` Florin Iucha
2007-10-31 17:53 ` Florin Iucha
[not found] ` <E1InUH6-0001vE-1Y@localhost>
2007-11-01 7:15 ` Fengguang Wu
2007-11-01 12:25 ` Florin Iucha
[not found] ` <E1InZht-0004lr-NN@localhost>
2007-11-01 13:03 ` Fengguang Wu
2007-11-01 14:14 ` Florin Iucha
[not found] ` <E1InlPV-0001f1-SL@localhost>
2007-11-02 1:33 ` Fengguang Wu
2007-11-02 2:10 ` Florin Iucha
[not found] ` <E1Inw51-0001e8-PS@localhost>
2007-11-02 12:56 ` Fengguang Wu
2007-11-02 13:32 ` Florin Iucha
2007-11-11 13:43 ` Thomas
2007-12-04 10:28 ` [Bug 9291] " Ingo Molnar
2007-12-04 17:45 ` Thomas Kuther
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=393744987.14537@ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=florin@iucha.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=trond.myklebust@fys.uio.no \
/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