Date: Tue, 16 Dec 2003 13:23:40 -0800 From: Doug Barton <DougB@dougbarton.net> To: Scott Long <scottl@freebsd.org> Cc: current@freebsd.org Subject: Re: HEADS UP: Status of the 5.2 release Message-ID: <3FDF77DC.7060600@dougbarton.net> In-Reply-To: <3FDBDA30.6010101@freebsd.org> References: <3FDBDA30.6010101@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FDF77DC.7060600>