From owner-freebsd-current@FreeBSD.ORG Sat Oct 2 19:55:52 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 2CB8B16A4CE for ; Sat, 2 Oct 2004 19:55:52 +0000 (GMT) Received: from chatserv.de (p15119030.pureserver.info [217.160.175.43]) by mx1.FreeBSD.org (Postfix) with SMTP id 5C25543D1F for ; Sat, 2 Oct 2004 19:55:51 +0000 (GMT) (envelope-from sascha@schumann.cx) Received: (qmail 29464 invoked by uid 1040); 2 Oct 2004 19:55:49 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 2 Oct 2004 19:55:49 -0000 Date: Sat, 2 Oct 2004 21:55:48 +0200 (CEST) From: Sascha Schumann X-X-Sender: sas@localhost To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: 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 19:55:52 -0000 [same message is in moderation queue] 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