From owner-freebsd-fs@FreeBSD.ORG Mon May 20 20:42:20 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E51CD2EB; Mon, 20 May 2013 20:42:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id B7E741877; Mon, 20 May 2013 20:42:20 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 005DBB965; Mon, 20 May 2013 16:42:19 -0400 (EDT) From: John Baldwin To: freebsd-fs@freebsd.org, Rick Macklem Subject: Re: kern/177335: [nfs] [panic] Sleeping on "vmopar" with the following non-sleepable locks held: exclusive sleep mutex NFSnode lock (NFSnode lock) Date: Mon, 20 May 2013 15:31:45 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <201305200332.r4K3WsBS083290@freefall.freebsd.org> In-Reply-To: <201305200332.r4K3WsBS083290@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201305201531.45263.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 20 May 2013 16:42:20 -0400 (EDT) Cc: kib@freebsd.org, linimon@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2013 20:42:21 -0000 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. -- John Baldwin