DragonFly BSD
DragonFly bugs List (threaded) for 2010-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[no subject]


apollo.backplane.com> <20100323090705.GA1138@sekishi.zefyris.com>
From: Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: Machine unresponsive with cache_lock: blocked on... message
Date: Tue, 23 Mar 2010 16:32:43 -0700 (PDT)
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:bugs@crater.dragonflybsd.org>
List-Subscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:bugs-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-bugs@crater.dragonflybsd.org>
Sender: bugs-errors@crater.dragonflybsd.org
Errors-To: bugs-errors@crater.dragonflybsd.org
Lines: 26
X-Trace: 1269387246 crater_reader.dragonflybsd.org 55376
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
: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 

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]