From owner-freebsd-threads@FreeBSD.ORG  Fri Jan  2 00:47:25 2009
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: threads@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 78573106564A;
	Fri,  2 Jan 2009 00:47:25 +0000 (UTC)
	(envelope-from bright@elvis.mu.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id 67FBA8FC18;
	Fri,  2 Jan 2009 00:47:25 +0000 (UTC)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 5CE901A3C39; Thu,  1 Jan 2009 16:32:15 -0800 (PST)
Date: Thu, 1 Jan 2009 16:32:15 -0800
From: Alfred Perlstein <alfred@freebsd.org>
To: David Xu <davidxu@freebsd.org>, Julian Elischer <julian@elischer.org>,
	threads@freebsd.org
Message-ID: <20090102003215.GB60686@elvis.mu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Cc: 
Subject: (forw) Re: (forw) Re: Process stuck in STOP state
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2009 00:47:25 -0000

David, Julian, there's a pretty good synopsys by Tor attached
here for a deadlock in 7.x.

Can anyone comment if it's fixed or if there's a way to fix it?

thanks,
-Alfred

----- Forwarded message from Tor Egge <Tor.Egge@cvsup.no.freebsd.org> -----

From: Tor Egge <Tor.Egge@cvsup.no.freebsd.org>
To: alfred@freebsd.org
Cc: smp@freebsd.org
Subject: Re: (forw) Re: Process stuck in STOP state
Date: Thu, 01 Jan 2009 22:15:14 +0000 (UTC)
Message-Id: <20090101.221514.41667097.Tor.Egge@cvsup.no.freebsd.org>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Sender: owner-freebsd-smp@freebsd.org

> 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 <URL:http://aqua.pixnet.tw/~jnlin/textdump/event3/1230/>

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
_______________________________________________
freebsd-smp@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-smp
To unsubscribe, send any mail to "freebsd-smp-unsubscribe@freebsd.org"

----- End forwarded message -----

-- 
- Alfred Perlstein