From owner-freebsd-bugs Fri Oct 31 23:27:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA05331 for bugs-outgoing; Fri, 31 Oct 1997 23:27:20 -0800 (PST) (envelope-from owner-freebsd-bugs) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA05227; Fri, 31 Oct 1997 23:24:31 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id XAA28863; Fri, 31 Oct 1997 23:24:48 -0800 (PST) Message-Id: <199711010724.XAA28863@implode.root.com> To: Tony Overfield cc: bugs@FreeBSD.ORG, hackers@FreeBSD.ORG, elh@svic.com Subject: Re: 2.2.5 installation bug on 1gig machines In-reply-to: Your message of "Fri, 31 Oct 1997 22:54:37 CST." <3.0.3.32.19971031225437.006d6490@bugs.us.dell.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 31 Oct 1997 23:24:48 -0800 Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >At 04:40 PM 10/31/97 -0800, David Greenman wrote: >>You'll >>have to physically pull out some of the memory and/or replace it with >>lower density SIMMs until you've finished the installation and built a >>customized kernel. > >Can the kernel know (or calculate) the maximum amount of memory it can >use without crashing? If so, it could refuse to register memory greater >than that amount. Uh, well, the answer to this is that there is a bug in the kernel that is causing the problem. We didn't test kernel's with the BOUNCE_BUFFERS option on any large memory systems. Otherwise, how much memory a system has is not an issue with regard to the system crashing (resources allocated out of that memory can be a problem if tuned wrong, but that is a different issue). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project