From owner-freebsd-threads@FreeBSD.ORG Mon Jan 12 20:49:59 2009 Return-Path: Delivered-To: freebsd-threads@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D94B1065678 for ; Mon, 12 Jan 2009 20:49:59 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from gw.sandvine.com (gw.sandvine.com [199.243.201.138]) by mx1.freebsd.org (Postfix) with ESMTP id BE9BD8FC1F for ; Mon, 12 Jan 2009 20:49:58 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 12 Jan 2009 15:37:57 -0500 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 12627) id 8F35513613; Mon, 12 Jan 2009 15:37:57 -0500 (EST) Date: Mon, 12 Jan 2009 15:37:57 -0500 From: Ed Maste To: Alfred Perlstein Message-ID: <20090112203757.GA10620@sandvine.com> References: <200811041440.mA4Ee31J084489@freefall.freebsd.org> <20081104154113.GP60438@elvis.mu.org> <20081104180349.GA9527@sandvine.com> <20081104190221.GT60438@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081104190221.GT60438@elvis.mu.org> User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 12 Jan 2009 20:37:57.0788 (UTC) FILETIME=[A7357DC0:01C974F5] Cc: freebsd-threads@FreeBSD.org Subject: Re: threads/128180: pthread_cond_broadcast(3) lost wakeup X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 20:49:59 -0000 On Tue, Nov 04, 2008 at 11:02:21AM -0800, Alfred Perlstein wrote: > * Ed Maste [081104 10:03] wrote: > > On Tue, Nov 04, 2008 at 07:41:13AM -0800, Alfred Perlstein wrote: > > > > > This bug may have been fixed in 6-stable and 6.4. > > > > > > http://svn.freebsd.org/viewvc/base?view=revision&revision=184172 > > > > > > Can you try upgrading? > > > > I tried with the changes from r184172, but I'm still able to reproduce > > the problem using the test app in the PR. With your change it does > > seem to run for on average about 10 times as long before it hangs though. > > Hmm... I'll look into it. Did you have a chance to look into it at all? I didn't really test it very thoroughly, so my my comment about running 10 times as long may not be right -- my main concern is that the test app still does demonstrate the problem with r184172 applied. -Ed