From owner-freebsd-current@FreeBSD.ORG Sat Oct 2 20:08:20 2004 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 9854A16A4CE for ; Sat, 2 Oct 2004 20:08:20 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id D43BE43D1F for ; Sat, 2 Oct 2004 20:08:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 02D2C53A87; Sat, 2 Oct 2004 13:09:01 -0700 (PDT) Date: Sat, 2 Oct 2004 13:09:01 -0700 From: Kris Kennaway To: Sascha Schumann Message-ID: <20041002200901.GA53162@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: Conclusion of thread "Deadlocks with recent SMP current"? 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: Sat, 02 Oct 2004 20:08:20 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 02, 2004 at 09:55:48PM +0200, Sascha Schumann wrote: > [same message is in moderation queue] >=20 > Hi, >=20 > was there any conclusion to that thread? I have got two > systems which are showing the exact same symptoms running > RELENG_5_2. The busier one deadlocks regularly once a day. Yes, this is believed to have been resolved in 5.3. > What is the recommended way to procede? I don't want to > upgrade to RELENG_5 due to the experimental nature of the > network stack, gcc 3.4 integration and general dislike of > bleeding edge software for production systems. (and yes, the > freebsd 5 systems are inherited.) So, you're running 5.2 on those systems, which was documented as a development release and not recommended for use on production systems (and indeed contained numerous rough edges and bugs), and you're scared to update to 5.3 which is going to be designated as the beginning of the 5.3-STABLE branch (and has had a couple of months of extensive bugfixing and QA)? You might want to consider re-evaluating your position. Kris --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBXwrdWry0BWjoQKURAgBhAKC12F02NL7hxDKRkfxqF7y6lmO07wCg6iLa ymR0OXWOMtkTEakKLOG1XbE= =04z1 -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--