From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 16:27:31 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9499A16A41F for ; Mon, 8 Aug 2005 16:27:31 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4330243D46 for ; Mon, 8 Aug 2005 16:27:31 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 7ACBC46B46; Mon, 8 Aug 2005 12:27:30 -0400 (EDT) Date: Mon, 8 Aug 2005 17:30:36 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Rong-En Fan In-Reply-To: <6eb82e050808085132807d80@mail.gmail.com> Message-ID: <20050808171707.E34546@fledge.watson.org> References: <6eb82e0507241001615f7490@mail.gmail.com> <20050729001511.O60522@fledge.watson.org> <6eb82e050808085132807d80@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org, A.S.Usov@kvi.nl Subject: Re: panic: sbflush_locked on 5.4-p5/i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 16:27:31 -0000 On Mon, 8 Aug 2005, Rong-En Fan wrote: > After upgrading to 5-STABLE (about Aug 6), it works very good. With > mpsafenet=1, it can work more than one day without panic. For 5.4-p5, it > will panic at most half day or so. This bug seems fixed after 5.4 is > released. I'll keep watching this machine. Will let you know if it still > have similar panics ;-) If you can confirm that the problem really is fixed in -STABLE, there are two sets of changes that may be relevant: - There are a number of SACK-related bug fixes in RELENG_5 that are not in the RELENG_5_4 branch. - There are a number of TCP/inpcb-related locking fixes (one in particular for IPv6) that are in RELENG_5 but not RELENG_5_4. We can then try and figure out which change it is that's helping, and get that merged to RELENG_5_4 as an errata item. If you have IPv6 traffic, there are some fixes I made a month or two ago that might be particularly relevant during connection tear-down. Robert N M Watson