From owner-freebsd-hackers Thu Aug 12 22: 7:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1087F1564A for ; Thu, 12 Aug 1999 22:07:26 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA87573; Thu, 12 Aug 1999 22:05:36 -0700 (PDT) (envelope-from dillon) Date: Thu, 12 Aug 1999 22:05:36 -0700 (PDT) From: Matthew Dillon Message-Id: <199908130505.WAA87573@apollo.backplane.com> To: David Scheidt Cc: "Addr.com Web Hosting" , freebsd-hackers@FreeBSD.ORG Subject: Re: Q: panic: pipeinit: cannot allocate pipe -- out of kvm -- code = 3 References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Thu, 12 Aug 1999, Addr.com Web Hosting wrote: : :> It happened more often then I am comfortable with (twice per day on one :> occasion). This is a machine running FreeBSD 3.0-STABLE on dual PII 400 :> with 1GB of ram and a DPT raid card. The machine is running semi-heavy load :> (http/mail/telnet/ftp), as well as nfs server and client. What could I do :> to avoid this sort of panic in the future? : :The first thing I would do is upgrade to a more recent -STABLE. Lots :of things have changed since 3.0-STABLE. Even if this particular thing :hasn't, there have been a number of nfs improvements, as well as assorted :other changes. : : :David Scheidt The latest versions of both STABLE and CURRENT do a better job scaling KVM to main memory. Upgrading should fix this problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message