Tue Mar 23 16:33:18 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 16:32:43 -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: 1269387246 crater_reader.dragonflybsd.org 55376 188.8.131.52
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:11573
: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've pushed more fixes to head, please try it.
It's STILL the rebalancing code. This time it deadlocked waiting for
the VM system to free up memory while holding shared locks on a
We will keep going until these deadlocks go away, but I'm going to
have to rethink portions of the kernel memory allocator w/ regards
to HAMMER for sure after we roll the release.
<dillon at backplane.com>
More information about the Bugs