From owner-freebsd-current@FreeBSD.ORG Sat Jun 12 22:11:09 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 5A2EF16A4CE; Sat, 12 Jun 2004 22:11:09 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1BC43D45; Sat, 12 Jun 2004 22:11:03 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id BBF9A6AA57; Sun, 13 Jun 2004 08:09:50 +1000 (EST) Date: Sun, 13 Jun 2004 08:09:50 +1000 From: John Birrell To: Robert Watson Message-ID: <20040612220950.GF15577@freebsd3.cimlogic.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: current@FreeBSD.org Subject: Re: HEADS UP: Starting socket locking merge 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, 12 Jun 2004 22:11:09 -0000 On Sat, Jun 12, 2004 at 05:09:32PM -0400, Robert Watson wrote: > As we've had mbuma merged recently, altq, and several other networking > changes in addition to this, I'd ask people be particularly diligent in > reporting new poor behavior in the network stack. Because we've also seen > several fixes along the way, I'd also ask you make sure you're up-to-date. That's difficult for those of us who are affected by the ACPI interrupt allocation problems. If ACPI isn't going to be fixed soon (it's been 2 weeks already), then the last commits should be backed. -- John Birrell