No subject

Unknown Unknown
Tue Mar 23 16:33:18 PDT 2010> <20100323090705.GA1138 at>
From: Matthew Dillon <dillon at>
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>
List-Subscribe: <mailto:bugs-request at>
List-Unsubscribe: <mailto:bugs-request at>
List-Help: <mailto:bugs-request at>
List-Owner: <mailto:owner-bugs at>
Sender: bugs-errors at
Errors-To: bugs-errors at
Lines: 26
X-Trace: 1269387246 55376
Xref: 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:
:I have now set vfs.vm_cycle_point to 64 just in case. I may still be
:positively surprised...
:Francois Tigeot

    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
    HAMMER cursor.

    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.

					Matthew Dillon 
					<dillon at>

More information about the Bugs mailing list