From owner-freebsd-current Wed Jul 17 12:58:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C52137B400 for ; Wed, 17 Jul 2002 12:58:42 -0700 (PDT) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id F364B43E42 for ; Wed, 17 Jul 2002 12:58:41 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0460.cvx22-bradley.dialup.earthlink.net ([209.179.199.205] helo=mindspring.com) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17UuwK-0005G1-00; Wed, 17 Jul 2002 12:58:24 -0700 Message-ID: <3D35CC2B.F34C72BD@mindspring.com> Date: Wed, 17 Jul 2002 12:57:31 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Szilveszter Adam Cc: freebsd-current@FreeBSD.ORG Subject: Re: Interesting panic very early in the boot References: <3D3508A0.B7D12818@mindspring.com> <200207171657.MAA28965@glatton.cnchost.com> <20020717173822.GB1068@fonix.adamsfamily.xx> <3D35B8F7.9915A14D@mindspring.com> <20020717194940.GC650@fonix.adamsfamily.xx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Szilveszter Adam wrote: > On Wed, Jul 17, 2002 at 11:35:35AM -0700, Terry Lambert wrote: > > My bet on the root cause, if I am correct, means that if you change > > the amount of physical RAM installed in the machine, the problem will > > go away, and that the problem is probably rare because it depends on > > certain things that are more complicated, after Matt's changes after > > my complaints about machdep.c reservations on large memory machines, > > as the amount of physical RAM approaches the size of the address > > space. > > 'Key, I can try that too. However, this machine is anything but "large > memory" these days: it has 128 Megs of (non-DDR) SDRAM. (2x64) It used to be that you would see the problem on large memory machines. Matt's changes have likely converted this into a discontinuous function. Another way of checking this without cracking the hood on the machine is to crank up the value of "maxfiles". For complicated reasons, it's best to put this number at 50,000 or higher, if you can still boot your machine with the prereservation of that much KVA space; the result should be an alternative mask for the problem. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message