From owner-freebsd-stable@FreeBSD.ORG Tue Oct 2 21:23:03 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60E821065673 for ; Tue, 2 Oct 2012 21:23:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 367CD8FC17 for ; Tue, 2 Oct 2012 21:23:03 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 95A71B94B; Tue, 2 Oct 2012 17:23:02 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Tue, 2 Oct 2012 17:15:19 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p20; KDE/4.5.5; amd64; ; ) References: <1990296074.1528480.1349129938870.JavaMail.root@erie.cs.uoguelph.ca> <506B3037.60201@yahoo.de> In-Reply-To: <506B3037.60201@yahoo.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201210021715.19310.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 02 Oct 2012 17:23:02 -0400 (EDT) Cc: Norbert Aschendorff Subject: Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2012 21:23:03 -0000 On Tuesday, October 02, 2012 2:19:35 pm Norbert Aschendorff wrote: > Well... > > Here the results for a kernel without WITNESS_SKIPSPIN (I'll compile one > including that tomorrow, but until then...) > > Good news is: The kernel crashed with activated WITNESS. > Bad news is: I have to turn power off after the crash with WITNESS. The > crash dump is _not_ written to disk :( > > Good news II is: It wrote something to the syslog. Actually, it wrote > very much to the syslog, some megabytes in total. Most of it is the > same, here the latest messages logfile: > http://lbo.spheniscida.de/Files/nfs-crash.log (94K) > > It specifies the file, line and zone. Maybe it's useful... That does help. It tells us that the lock being held is a vnode interlock that was last acquired in vinactive(). I don't see how though, unless the lock was recursively acquired elsewhere. You could try adding a different WITNESS check (using WITNESS_WARN) to see which NFS proc returns with a lock held so you can catch this when it first occurs rather than much later after the fact. Do you have the start of the log messages? -- John Baldwin