Current-Users archive

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

Re: mount_lofs panic



On Sun, May 04, 2008 at 03:51:54PM +0200, Juan RP wrote:
> On Sat, 3 May 2008 20:40:20 +0100
> "Chavdar Ivanov" <ci4ic4%gmail.com@localhost> wrote:
> 
> >  Reader / writer lock error: rw_vector_enter: locking against myself
> > 
> > lock address :  0x00000000dd7f04fc
> > current cpu  :                   1
> > current lwp  :  0x00000000cd781c60
> > owner / count:  0x00000000cd781c60
> >         flags:  0x00...04
> > panic: lock error
> > stopped in pid 526.1 (mount_null) at netbsd:breakpoint+0x4: popl %ebp
> > 
> > The trace points taken from screen:
> > 
> > db> bt
> > 
> > 
> > breakpoint
> > panic
> > lockdebug_abort
> > rw_abort
> > rw_vector_enter
> > vfs_busy
> > getnewvnode
> > layer_node_alloc
> > layer_node_create
> > nullfs_mount
> > VFS_MOUNT
> > do_sys_mount
> > sys___mount
> > syscall
> 
> I'm also seeing this panic with null mounts.

Again this is PR kern/38141... I'm looking into it.

Andrew


Home | Main Index | Thread Index | Old Index