Tue Mar 23 09:12:02 PDT 2010
apollo.backplane.com> <20100323090705.GA1138 at sekishi.zefyris.com>
From: Matthew Dillon <dillon at apollo.backplane.com>
Subject: Re: Machine unresponsive with cache_lock: blocked on... message
Date: Tue, 23 Mar 2010 09:11:40 -0700 (PDT)
List-Post: <mailto:bugs at crater.dragonflybsd.org>
List-Subscribe: <mailto:bugs-request at crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:bugs-request at crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:bugs-request at crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-bugs at crater.dragonflybsd.org>
Sender: bugs-errors at crater.dragonflybsd.org
Errors-To: bugs-errors at crater.dragonflybsd.org
X-Trace: 1269360809 crater_reader.dragonflybsd.org 55375 18.104.22.168
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:11565
:I'm not completely happy either: even with 40 some applications get paged out,
:which didn't occur with 2.4.
There's nothing wrong with an application getting paged out if it
is idle. It really isn't a bad thing. It frees up memory for the
apps which ARE running.
What people don't seem to like is when a lot of apps get paged out
overnight in order to satisfy certain overnight operations which
operate on a very large data set (the entire filesystem) and
can't be cached anyway.
:I also had a new deadlock this night (possibly during the daily periodic run).
:Symptoms were the same as usual: no keyboard input, no network activity, many
:pmap_interlock messages on the console...
:The new crash dump is there: http://www.wolfpond.org/crash.dfly/
:I have now set vfs.vm_cycle_point to 64 just in case. I may still be
Ok, I'll look at it.
<dillon at backplane.com>
More information about the Bugs