Date: Fri, 06 Feb 2004 22:03:06 -0700 From: Scott Long <scottl@freebsd.org> To: "Robin P. Blanchard" <robin.blanchard@gactr.uga.edu> Cc: current@FreeBSD.org Subject: Re: Odd quirks after updating to 5.2... Message-ID: <4024718A.3010108@freebsd.org> In-Reply-To: <EE3D3FBAFFCAED448C21C398FDAD91AC013BDEA1@EBE1.gc.nat> References: <EE3D3FBAFFCAED448C21C398FDAD91AC013BDEA1@EBE1.gc.nat>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4024718A.3010108>