Re: lock error panic: rw_vector_enter: locking against myself

[haad <haaaad%gmail.com@localhost>]

Hi,

Do you use any sort of layered filesystem in your setup?

On Sun, Jul 3, 2011 at 1:59 AM, NONAKA Kimihiro <nonakap%gmail.com@localhost> 
wrote:
> Hi,
>
> NetBSD/i386-current(20110702) panic when build.sh*3 and daily script is 
> running.
>
> -----
> Reader / writer lock error: rw_vector_enter: locking against myself
>
> lock address : 0x00000000cead7418
> current cpu  :                  0
> current lwp  : 0x00000000cc124800
> owner/count  : 0x00000000cc124800 flags    : 0x0000000000000004
>
> panic: lock error
> fatal breakpoint trap in supervisor mode
> trap type 1 code 0 eip c0202324 cs 8 eflags 246 cr2 bb53a000 ilevel 0
> Stopped in pid 9491.1 (find) at netbsd:breakpoint+0x4:  popl    %ebp
> db{0}> bt
> breakpoint()
> panic()
> lockdebug_abort()
> rw_abort()
> rw_vector_enter() at netbsd:rw_vector_enter+0x315
> genfs_lock() at netbsd:genfs_lock+0xa8
> layer_bypass() at netbsd:layer_bypass+0xc3
> VOP_LOCK() at netbsd:VOP_LOCK+0x62
> vclean() at netbsd:vclean+0x97
> getcleanvnode() at netbsd:getcleanvnode+0xd4
> getnewvnode() at netbsd:getnewvnode+0x70
> ffs_vget() at netbsd:ffs_vget+0x57
> ufs_lookup() at netbsd:ufs_lookup+0x74a
> VOP_LOOKUP() at netbsd:VOP_LOOKUP+0x8b
> lookup_once() at netbsd:lookup_once+0x18e
> namei_tryemulroot() at netbsd:namei_tryemulroot+0x17c
> namei() at netbsd:namei+0x2a
> do_sys_stat(): netbsd:do_sys_stat+0x52
> sys___lstat50() at netbsd:sys___lstat50+0x2a
> syscall() at netbsd:syscall+0xc4
> db{0}>
>
> --
> NONAKA Kimihiro
>



-- 


Regards.

Adam