From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 21:05:36 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 258E716A4CE for ; Fri, 6 Feb 2004 21:05:36 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 0103643D39 for ; Fri, 6 Feb 2004 21:05:35 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 64835 invoked by uid 1002); 7 Feb 2004 05:05:32 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 7 Feb 2004 05:05:32 -0000 Message-ID: <4024718A.3010108@freebsd.org> Date: Fri, 06 Feb 2004 22:03:06 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Robin P. Blanchard" References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Peter Losher cc: current@FreeBSD.org Subject: Re: Odd quirks after updating to 5.2... 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, 07 Feb 2004 05:05:36 -0000 Robin P. Blanchard wrote: >>-----Original Message----- >>From: owner-freebsd-current@freebsd.org >>[mailto:owner-freebsd-current@freebsd.org] On Behalf Of Doug White >>Sent: Wednesday, February 04, 2004 7:50 PM >>To: Peter Losher >>Cc: current@freebsd.org >>Subject: Re: Odd quirks after updating to 5.2... >> >> >>On Wed, 4 Feb 2004, Peter Losher wrote: >> >> >>>-----BEGIN PGP SIGNED MESSAGE----- >>>Hash: SHA1 >>> >>>Ever since I updated one of our other boxes from 5.1 to 5.2, I have >>>been having issues with the periodic processes not finishing up >>>properly, which after a week or so fills up all the >> >>permitted forked >> >>>processes, and then causes FreeBSD to deprive itself of resources. >> >>They weren't getting blocked in getblk or inode, were they? >>Thats one thing that we're still chasing. >> > > > I'd be glad to offer ssh access to a 2650 that consistently exhibits this > behaviour in hopes to get -CURRENT primed for the masses. Any takers ? > I just committed several fixes to the aac driver that might help your problem here. Without a posted dmesg, it's hard to say, though, so please let me know if it does. Scott