Date: Thu, 6 Mar 2003 13:22:20 -0600 From: Jonathan Lemon <jlemon@flugsvamp.com> To: John Baldwin <jhb@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: witness: nfs & buf queue Message-ID: <20030306132220.T61787@flugsvamp.com> In-Reply-To: <XFMail.20030306130149.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Thu, Mar 06, 2003 at 01:01:49PM -0500 References: <20030305201016.S61787@flugsvamp.com> <XFMail.20030306130149.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 06, 2003 at 01:01:49PM -0500, John Baldwin wrote: > > On 06-Mar-2003 Jonathan Lemon wrote: > > Doing a kernel build over NFS on today's -current gives a pile of > > following error messages during the final link phase: > > > > Acquiring lockmgr lock "nfs" with the following non-sleepablelocks held: > > exclusive sleep mutex buf queue lock r = 0 (0xc0427b60) locked @ ../../../kern/vfs_bio.c:2107 > > Acquiring lockmgr lock "nfs" with the following non-sleepablelocks held: > > exclusive sleep mutex buf queue lock r = 0 (0xc0427b60) locked @ ../../../kern/vfs_bio.c:2107 > > Acquiring lockmgr lock "nfs" with the following non-sleepablelocks held: > > exclusive sleep mutex buf queue lock r = 0 (0xc0427b60) locked @ ../../../kern/vfs_bio.c:2107 > > ... > > Witness didn't used to complain about these until my recent commits, > so these could be old bugs that we are just now seeing. It does look > like all the lock functions in inmem() use LK_NOWAIT which is exempted > from the witness check: > > if ((flags & (LK_NOWAIT|LK_RELEASE)) == 0) > WITNESS_WARN(WARN_GIANTOK | WARN_SLEEPOK, > &lkp->lk_interlock->mtx_object, > "Acquiring lockmgr lock \"%s\"", lkp->lk_wmesg); > > A stack trace from one of these would be helpful. Here you go. This is from -current as of roughly an hour ago, I managed to break into ddb in the middle of witness_warn: kvprintf(c03918eb,c0210c20,e4050bfc,a,e4050c48) at kvprintf+0x8d vprintf(c03918eb,e4050c48,0,c0428620,10001) at vprintf+0x57 witness_warn(5,c0400da8,c03918eb,c039fff9,c6a752d0) at witness_warn+0xbe lockmgr(ca438304,10001,ca438248,c6a752d0,12) at lockmgr+0xc8 vop_sharedlock(e4050c98,0,c039a8b0,35c,c01eb1f2) at vop_sharedlock+0x7d vn_lock(ca438248,12,c6a752d0,83b,c04285e0) at vn_lock+0xeb flushbufqueues(c04285e0,0,c0398a32,104,64) at flushbufqueues+0x100 buf_daemon(0,e4050d48,c0390fdb,35f,0) at buf_daemon+0xd5 fork_exit(c0239920,0,e4050d48) at fork_exit+0xc4 fork_trampoline() at fork_trampoline+0x1a --- trap 0x1, eip = 0, esp = 0xe4050d7c, ebp = 0 --- No gdb stack trace, my dump device is too small. :-( -- Jonathan 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?20030306132220.T61787>