From owner-freebsd-hackers Wed Feb 17 12:12:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id DB5E71128A for ; Wed, 17 Feb 1999 12:12:38 -0800 (PST) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.1/8.9.1) with ESMTP id VAA22106; Wed, 17 Feb 1999 21:12:34 +0100 (CET) Message-Id: <199902172012.VAA22106@midten.fast.no> To: dillon@apollo.backplane.com Cc: hackers@FreeBSD.ORG Subject: Re: Problems in VM structure ? From: Tor.Egge@fast.no In-Reply-To: Your message of "Wed, 17 Feb 1999 11:31:12 -0800 (PST)" References: <199902171931.LAA10322@apollo.backplane.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 17 Feb 1999 21:12:34 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ach. > > So why isn't it panicing on boot? Why does the machine > destabilize and die later on with all sorts of problems? > Is it trying to use more page table entries then were allocated > for the kernel_map? Is the submap allocator broken? The numbers I gave for kva consumptions by zones etc. might not be completely accurate. Thus kernel_map might be sufficient large for boot. But kernel_map is used directly later (pipes, imgact_gzip, link_elf, resource lists, pmap_new_proc, ...), and one of those KVM consumers might have insufficient error handling when kernel_map no longer has sufficient contiguous free space. > Is there some test we can add to panic the machine at boot > time if KVM is over-reserved? You might give a warning (or panic) if kernel_map has less free space than some predefined limits (using kernel configuration parameters when calculating the limits). - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message