Machine unresponsive with cache_lock: blocked on... message

[Francois Tigeot]

On Thu, Mar 04, 2010 at 04:09:27PM -0800, Matthew Dillon wrote:
> :I just got a new crash.
> :
> :The system was running DragonFly v2.5.1.902.g333f4-DEVELOPMENT from the 25th.
> :
> :There were these messages on the console:
> :
> :Warning: pmap_interlock 00010003
> :Warning: pmap_interlock 00010003
> :
> :No cache_lock stuff this time.
> 
>     It looks like a deadlock between the VM system and HAMMER due to
>     kmalloc() blocking during a low memory situation.  Your system
>     was paging heavily at the time and was low on free memory.
> 
>     I have committed a change to master which should fix this particular
>     issue.

I got a new one.
Same symptoms, many pmap_interlock messages on the console.

System has been updated to
DragonFly v2.5.1.960.g7a6ce-DEVELOPMENT #9: Thu Mar 11 10:22:12 CET 2010

Kernel and crash dump are at the usual place:

http://www.wolfpond.org/crash.dfly/

-- 
Francois Tigeot