From owner-freebsd-alpha Sun Oct 8 3: 7:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id 1B04C37B502 for ; Sun, 8 Oct 2000 03:07:56 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 13iDN4-0009U5-0C; Sun, 8 Oct 2000 10:07:54 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA31732; Sun, 8 Oct 2000 11:14:36 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 8 Oct 2000 11:07:14 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: size problems with INVARIANTS/DIAGNOSTIC -current kernels In-Reply-To: <14815.26475.95721.701188@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 7 Oct 2000, Andrew Gallatin wrote: > > Doug Rabson writes: > > On Fri, 6 Oct 2000, Andrew Gallatin wrote: > > > > > /ithreads data=0x3e6a78+0x32678 syms=[0x8+0x4ea98+0x8+0x39115] > > > Entering ithreads at 0xfffffc0000330320... > > > XentMM = 0xfffffc00005e1f2c > > > Memory cluster count: 3 > > > MEMC 0: pfn 0x0 cnt 0xa5 usage 0x1 > > > MEMC 1: pfn 0xa5 cnt 0x3ee6 usage 0x0 > > > Cluster 1 contains kernel > > > Loading chunk after kernel: 0x3d3 / 0x3f8b > > > MEMC 2: pfn 0x3f8b cnt 0x75 usage 0x1 > > > Unrecognized boot flag '"'. > > > Unrecognized boot flag '"'. > > > Copyright (c) 1992-2000 The FreeBSD Project. > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > > The Regents of the University of California. All rights reserved. > > > kmem_init: kmemusage = 0xfffffe0000296000 > > > > > > halted CPU 0 > > > > Hmm. I wonder if the kernel is running out of its bootstrap address space > > limits before it manages to finish initialising the vm system. Try > > increasing the value of NKPT in pmap.h to see if it helps. > > I doubled it from 9 to 18 & still see the same behaviour.. Hmm. I think I need to see a disassembly of the region which contains the fault pc. I can't quite see what is happening yet. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message