From: Chuck Ebbert <cebbert@redhat.com>
To: Brice Figureau <brice+lklm@daysofwonder.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: Strange freeze on 2.6.22 (deadlock?)
Date: Tue, 08 Jan 2008 18:16:59 -0500 [thread overview]
Message-ID: <4784046B.5000004@redhat.com> (raw)
In-Reply-To: <49447.213.41.177.193.1199732765.squirrel@corp.daysofwonder.com>
On 01/07/2008 02:06 PM, Brice Figureau wrote:
> Thanks for the answer.
> I'm using whatever is the default mount option (which I think is
> data=ordered). The only other mount option I use is nodiratime,noatime.
>
> Note that a large part of the processes in D state are "waiting" in
> __mutex_lock from generic_file_aio_write.
> Another large part is coming from balance_dirty_pages_ratelimited_nr.
>
> It seems that there was some writeback congestion to the block device.
> All the /proc/sys/vm/* files are at their defaults.
>
> This looks like if it wasn't possible to write to the block device anymore.
> Could a block device write error (ie hardware failure) be the root cause?
>
> Any other idea?
> What should I try the next time it freezes?
Same bug as http://lkml.org/lkml/2007/8/1/469 ??
next prev parent reply other threads:[~2008-01-08 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 19:06 Strange freeze on 2.6.22 (deadlock?) Brice Figureau
2008-01-08 23:16 ` Chuck Ebbert [this message]
2008-01-09 16:02 ` Brice Figureau
-- strict thread matches above, loose matches on Subject: below --
2008-01-07 21:14 Brice Figureau
2008-01-07 15:48 Brice Figureau
2008-01-07 17:20 ` Randy Dunlap
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=4784046B.5000004@redhat.com \
--to=cebbert@redhat.com \
--cc=brice+lklm@daysofwonder.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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.