Date: Mon, 20 May 2013 16:58:45 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-fs@freebsd.org, Rick Macklem <rmacklem@freebsd.org>, kib@freebsd.org, linimon@freebsd.org Subject: Re: kern/177335: [nfs] [panic] Sleeping on "vmopar" with the following non-sleepable locks held: exclusive sleep mutex NFSnode lock (NFSnode lock) Message-ID: <45797708.465808.1369083525132.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <201305201531.45263.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Sunday, May 19, 2013 11:32:54 pm linimon@freebsd.org wrote: > > Old Synopsis: Sleeping on "vmopar" with the following non-sleepable > > locks > held: exclusive sleep mutex NFSnode lock (NFSnode lock) > > New Synopsis: [nfs] [panic] Sleeping on "vmopar" with the following > > non- > sleepable locks held: exclusive sleep mutex NFSnode lock (NFSnode > lock) > > > > Responsible-Changed-From-To: freebsd-bugs->freebsd-fs > > Responsible-Changed-By: linimon > > Responsible-Changed-When: Mon May 20 03:32:02 UTC 2013 > > Responsible-Changed-Why: > > Over to maintainer(s). > > I think this issue might have been recently fixed in HEAD, > specifically in > r248567 and r248581. > I just emailed the reporter with a variant of these patches for 8.3/old NFS client. I suppose I should change the PR status to feedback. And, yes, the panic appears to be the same as what the above commits fix, except in 8.3/old NFS client. rick > -- > John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45797708.465808.1369083525132.JavaMail.root>