From owner-freebsd-current@FreeBSD.ORG Thu Mar 1 09:33:34 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CED5316A400; Thu, 1 Mar 2007 09:33:34 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id A415C13C4A8; Thu, 1 Mar 2007 09:33:34 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 01784470C6; Thu, 1 Mar 2007 04:33:34 -0500 (EST) Date: Thu, 1 Mar 2007 09:33:33 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Scott Robbins In-Reply-To: <20070301092759.GB6385@mail.scottro.net> Message-ID: <20070301093205.M13593@fledge.watson.org> References: <20070226204916.C56223@fledge.watson.org> <45E5D589.3080202@FreeBSD.org> <20070228234754.Q13593@fledge.watson.org> <45E6178F.8040302@cisco.com> <20070301031907.GD94643@mail.scottro.net> <45E67908.9090707@cisco.com> <20070301092759.GB6385@mail.scottro.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Randall Stewart , brooks@freebsd.org, "Stephane E. Potvin" , current@freebsd.org Subject: Re: HEADS UP: UNIX domain socket locking changes merged to CVS HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 09:33:34 -0000 On Thu, 1 Mar 2007, Scott Robbins wrote: >> So the good news is once you can build .. it seems to be the problem is >> solved.. of course I still could lock up.. but only using X will tell :-0 > > Yes, I'm almost afraid to startx. I won't really get a chance till tonight, > but Robert, thank you. (Also, I've lost track of who was the one who was > able to get the trace, but thanks are also due there.) No problem, and sorry about the deadlocks. I'm was a bit surprised they didn't turn up in the rather heavy UNIX domain socket testing with MySQL, but it occurs to me that traffic with MySQL is largely synchronous due to it being a query transmitted completely, processing, and then a reply transmitted completely. As a result, there was likely very little simulteneous transmitting and receiving on the same socket at the same time. It sounds like a new regression test is called for... Robert N M Watson Computer Laboratory University of Cambridge