Hello,
I get this while working on my port of NetBSD to Milkymist (lm32) SoC:
panic: kernel diagnostic assertion ci-ci_mtx_count == -1 failed: file
/home/ysionneau/perso/NetBSD/sys/kern/kern_synch.c, line 676
mi_switch: cpu0: ci_mtx_count (0) != -1 (block with spin-mutex held)
I put a
Yann Sionneau yann.sionn...@gmail.com wrote:
I've tried to understand how ci_mtx_count is supposed to be managed my
MD code, so far I failed to understand.
It seems some arch use spin_mutex and inc/dec ci_mtx_count upon
spin_mutex_enter/exit.
Some other archs do it in softint handling.
On 02/24/2014 06:38 PM, Mindaugas Rasiukevicius wrote:
Yann Sionneau yann.sionn...@gmail.com wrote:
I've tried to understand how ci_mtx_count is supposed to be managed my
MD code, so far I failed to understand.
It seems some arch use spin_mutex and inc/dec ci_mtx_count upon
Date: Fri, 21 Feb 2014 12:35:40 +0100
From: J. Hannken-Illjes hann...@eis.cs.tu-bs.de
Diff available at http://www.netbsd.org/~hannken/vnode-pass3-1.diff
Comments or objections anyone?
This seems needlessly complicated to me. Outside of the vfs lifecycle
code, why would you ever
Date: Sun, 23 Feb 2014 13:57:52 +0100
From: J. Hannken-Illjes hann...@eis.cs.tu-bs.de
Currently dead vnodes still reside on the vnodelist of the file system
they have been removed from. To me it looks much better to create
a dead mount that takes dead vnodes until they get freed.
