From owner-freebsd-hackers Tue Apr 6 16:36:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 5D9A6154B2 for ; Tue, 6 Apr 1999 16:36:48 -0700 (PDT) (envelope-from fanf@demon.net) Received: by noc.demon.net; id AAA03096; Wed, 7 Apr 1999 00:34:49 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma003078; Wed, 7 Apr 99 00:34:48 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10UfMl-0004wW-00; Wed, 7 Apr 1999 00:34:47 +0100 To: hackers@freebsd.org From: Tony Finch Subject: Re: Increasing both NBUF and NMBCLUSTERS leads to panics In-Reply-To: References: <199904061651.SAA11984@adv.iae.nl> <199904061806.LAA09677@apollo.backplane.com> Message-Id: Date: Wed, 7 Apr 1999 00:34:47 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: >Matthew Dillon writes: >> >> The problem is that insufficient KVM is being reserved. You need >> to upgrade to the latest -CURRENT ( i.e. 4.x ). The fixes will probably >> go into -STABLE before the next release, but they are not in yet. > >Nah, just read section 13.15 in the FreeBSD FAQ. I don't think that covers all the bases: after patching the kernel for a larger address space we couldn't boot it until we also patched /boot/loader. I can't log into the machine with the patches right now to get the details, but looking for recent threads on freebsd-current about large memory machines will get you what you need. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message