From owner-freebsd-current@FreeBSD.ORG  Sun Oct  3 20:02:10 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 4A8E816A4D0
	for <freebsd-current@freebsd.org>;
	Sun,  3 Oct 2004 20:02:10 +0000 (GMT)
Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1662E43D2F
	for <freebsd-current@freebsd.org>;
	Sun,  3 Oct 2004 20:02:07 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from elischer.org (adsl-67-124-50-20.dsl.snfc21.pacbell.net
	[67.124.50.20])i93K1iIV009605;	Sun, 3 Oct 2004 16:01:46 -0400
Message-ID: <41605AB9.8090008@elischer.org>
Date: Sun, 03 Oct 2004 13:02:01 -0700
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Sascha Schumann <sascha@schumann.cx>
References: <Pine.LNX.4.60.0410021850180.1355@localhost>
In-Reply-To: <Pine.LNX.4.60.0410021850180.1355@localhost>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Oct 2004 20:02:10 -0000

Sascha Schumann wrote:
>     Hi,
> 
>     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.
> 
>     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.)
> 
>     Thanks for any advise.
> 
>     - Sascha
> 
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

We have two thread dealock cases hat we are tracking down
there are fixes for both in the works.