From owner-freebsd-smp@FreeBSD.ORG Thu Jan 1 22:44:32 2009 Return-Path: Delivered-To: smp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E46E9106564A for ; Thu, 1 Jan 2009 22:44:32 +0000 (UTC) (envelope-from Tor.Egge@cvsup.no.freebsd.org) Received: from pil.idi.ntnu.no (pil.idi.ntnu.no [129.241.107.93]) by mx1.freebsd.org (Postfix) with ESMTP id 67D168FC08 for ; Thu, 1 Jan 2009 22:44:32 +0000 (UTC) (envelope-from Tor.Egge@cvsup.no.freebsd.org) Received: from cvsup.no.freebsd.org (c2h5oh.idi.ntnu.no [129.241.103.69]) by pil.idi.ntnu.no (8.14.1/8.13.1) with ESMTP id n01MFQqA004853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Jan 2009 23:15:27 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by cvsup.no.freebsd.org (8.14.2/8.14.2) with ESMTP id n01MFQhV042846; Thu, 1 Jan 2009 22:15:26 GMT (envelope-from Tor.Egge@cvsup.no.freebsd.org) Date: Thu, 01 Jan 2009 22:15:14 +0000 (UTC) Message-Id: <20090101.221514.41667097.Tor.Egge@cvsup.no.freebsd.org> To: alfred@freebsd.org From: Tor Egge In-Reply-To: <20081227223820.GE18389@elvis.mu.org> References: <20081227223820.GE18389@elvis.mu.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned-By: mimedefang.idi.ntnu.no, using CLAMD X-SMTP-From: Sender=, Relay/Client=c2h5oh.idi.ntnu.no [129.241.103.69], EHLO=cvsup.no.freebsd.org X-Scanned-By: MIMEDefang 2.48 on 129.241.107.38 X-Scanned-By: mimedefang.idi.ntnu.no, using MIMEDefang 2.48 with local filter 16.42-idi X-Filter-Time: 0 seconds Cc: smp@freebsd.org Subject: Re: (forw) Re: Process stuck in STOP state X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jan 2009 22:44:33 -0000 > Can someone look at this? This is pretty weird, it seems > that somehow there's some deadlock with vnode locks, but it > doesn't appear to be due a leaked vnode lock as "show lockednods" > doesn't show any vnodes locks. > > The trace should be somewhat easy to figure out but I'm kinda > of stuck.. > > Any ideas how this could happen? I had a brief look at msgbuf.txt contained info about some nfs vnodes locked by pid 27645. It looks like thread suspension is broken for the SINGLE_NO_EXIT case. Threads performing an interruptable sleep are suspended, even while holding other resources (e.g. vnode locks). Threads performing a non-interruptable sleep, waiting for resources held by the suspended threads are not suspended. The thread that started the suspension is not woken up since some of the other threads are not yet suspended. - Tor Egge