Date: Mon, 17 Mar 2003 19:53:12 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: freebsd-current@freebsd.org Subject: nfs panic: lockmgr: locking against myself Message-ID: <15990.28152.594563.16107@grasshopper.cs.duke.edu>
next in thread | raw e-mail | index | archive | help
I'm seeing the following panic under heavy NFS client usage on an SMP
w/kernel sources from Weds. evening. Has this been fixed?
Thanks,
Drew
panic: lockmgr: locking against myself
cpuid = 0; lapic.id = 00000000
Debugger("panic")
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db> t
Debugger(c0355e8c,0,c0354b5c,d8e2793c,1) at Debugger+0x55
panic(c0354b5c,0,c0354b22,ef,c41d6400) at panic+0x11f
lockmgr(ce6abce4,2090022,c470136c,c41d6400,26b) at lockmgr+0x491
BUF_TIMELOCK(ce6abc18,10022,c470136c,c035d2bf,0) at BUF_TIMELOCK+0x80
nfs_flush(c470136c,c443e480,1,c41d6400,1) at nfs_flush+0x607
nfs_fsync(d8e27a9c,0,c035a68f,45a,c1df8858) at nfs_fsync+0x31
vinvalbuf(c470136c,1,c443e480,c41d6400,0) at vinvalbuf+0xe4
nfs_vinvalbuf(c470136c,1,c443e480,c41d6400,1) at nfs_vinvalbuf+0x191
nfs_setattr(d8e27b60,20002,c41d6400,0,0) at nfs_setattr+0x1f5
setutimes(c41d6400,c470136c,d8e27ca8,2,0) at setutimes+0x1c4
kern_utimes(c41d6400,bfbff8e8,0,bfbfece0,0) at kern_utimes+0x9c
utimes(c41d6400,d8e27d10,c03667a3,404,2) at utimes+0x31
syscall(2f,2f,2f,bfbff8e8,4) at syscall+0x24e
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (138, FreeBSD ELF32, utimes), eip = 0x8049e8f, esp = 0xbfbfecbc, ebp = 0xbfbfed08 ---
db>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15990.28152.594563.16107>