From: Edward Shishkin <edward.shishkin@gmail.com>
To: Andrej Podzimek <andrej@podzimek.org>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Problems with the 'flush-8:0' process in 2.6.35.3
Date: Sat, 28 Aug 2010 12:15:49 +0200 [thread overview]
Message-ID: <4C78E1D5.80101@gmail.com> (raw)
In-Reply-To: <4C789044.3020403@podzimek.org>
Andrej Podzimek wrote:
> Hello,
Hello.
>
> I use a 2.6.35.3 kernel and Reiser4 as the root file system. In a
> couple of minutes after boot, a kernel process called 'flush-8:0'
> takes up all the available CPU time. From that moment on, it is
> impossible to sync filesystems (and suspend, hibernate or reboot).
> (The 'sync' command halts indefinitely.) In some cases it is even
> impossible to log in. Existing sessions seem to work fine, to an extent.
>
> I first thought this was related to the GTT chipset coherency patch.
> (This patch fixes a one-year-old bug that caused all the Intel 855
> class GPUs to be totally unusable.) However, removing the patch and
> testing with only a vanilla kernel (and Reiser4, of course) showed
> that 'flush-8:0' will eventually go mad, no matter if the GPU-related
> patch is present or not.
>
> The machine is an Asus M2400N laptop with a 100GB Seagate Momentus.
>
> Is this a known issue?
Um, nop..
> How could I track this down?
Could you try to catch sysrq-t output to take a look what the flush-8:0
doing?
> In fact I don't even know whether this is related to Reiser4 or not.
Which kernel version did you have before upgrade?
Thanks,
Edward.
> It may be a bug in VFS. I don't use 'noflushd' or anything of that
> kind. (Some people reported similar problems related to noflushd. So
> this is not the case.) If this is unrelated to Reiser4, where should I
> report it?
>
> Andrej
>
next prev parent reply other threads:[~2010-08-28 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 4:27 Problems with the 'flush-8:0' process in 2.6.35.3 Andrej Podzimek
2010-08-28 10:15 ` Edward Shishkin [this message]
2010-08-31 0:21 ` Edward Shishkin
2010-09-15 11:41 ` Andrej Podzimek
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=4C78E1D5.80101@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=andrej@podzimek.org \
--cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).