From owner-freebsd-current@FreeBSD.ORG Tue Dec 16 13:23:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D19BF16A4CE; Tue, 16 Dec 2003 13:23:57 -0800 (PST) Received: from hudson.icann.org (hudson.icann.org [192.0.35.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98B5D43D1D; Tue, 16 Dec 2003 13:23:56 -0800 (PST) (envelope-from DougB@dougbarton.net) Received: from dougbarton.net (g35-097.icann.org [192.0.35.97] (may be forged)) by hudson.icann.org (8.11.6/8.11.6) with ESMTP id hBGLNep04241; Tue, 16 Dec 2003 13:23:41 -0800 Message-ID: <3FDF77DC.7060600@dougbarton.net> Date: Tue, 16 Dec 2003 13:23:40 -0800 From: Doug Barton User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <3FDBDA30.6010101@freebsd.org> In-Reply-To: <3FDBDA30.6010101@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ICANN-MailScanner-Information: Please contact support@icann.org for more information X-ICANN-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: HEADS UP: Status of the 5.2 release X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 16 Dec 2003 21:23:57 -0000 Do we have an updated status on this? I just got my new laptop, so I was going to burn an ISO of the latest RC and give it a try, but if it's going to blow up on install I don't want to waste time... Doug Scott Long wrote: > All, > > As I mentioned yesterday, we have a serious show-stopper for the 5.2 > release. Jeff Roberson and Doug White did some good diagnosis work a > few nights ago, but we are still without a fix. We cannot cut 5.2 until > this gets resolved. I know that this is the end of the year and > everyone has deadlines, family, travel, etc, but we really need some > more eyes on this. To recap, a panic happens from sysinstall while > unpacking the bin distribution. It is most readily created by enabling > SoftUpdates on the root partition, but there are reports that SU is not > a required factor. The panic originates in the fsync codepath and > ends with a corrupt mutex. This is discussed on the freebsd-current@ > mailing under the subject of "HAVE TRACE & DDB Re: FreeBSD 5.2-RC1 > released". Any help is appreciated. > > Thanks, > > The Release Engineering Team >