LKML Archive on
help / color / mirror / Atom feed
From: Brice Figureau <>
To: Chuck Ebbert <>
Cc: Randy Dunlap <>,
Subject: Re: Strange freeze on 2.6.22 (deadlock?)
Date: Wed, 09 Jan 2008 17:02:14 +0100	[thread overview]
Message-ID: <1199894534.7626.75.camel@localhost.localdomain> (raw)
In-Reply-To: <>


On Tue, 2008-01-08 at 18:16 -0500, Chuck Ebbert wrote: 
> 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 ??

Some of the stacktrace of the OP looks like the ones I posted.
The timeframe also matches since I noticed the first problems in 2.6.19
like the OP.

I remounted the fs without noatime and we'll see if it still freezes
next week.

Unfortunately, there doesn't seem to be any bug fix for this problem yet
(except the upcoming per device write throttling patch).

Thanks for pointing me in this direction,
Brice Figureau <>

  reply	other threads:[~2008-01-09 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 19:06 Brice Figureau
2008-01-08 23:16 ` Chuck Ebbert
2008-01-09 16:02   ` Brice Figureau [this message]
  -- 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1199894534.7626.75.camel@localhost.localdomain \ \ \ \ \
    --subject='Re: Strange freeze on 2.6.22 (deadlock?)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).