From owner-freebsd-current@FreeBSD.ORG Mon Sep 13 15:25:21 2004 Return-Path: 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 D449516A4D0; Mon, 13 Sep 2004 15:25:21 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD78C43D54; Mon, 13 Sep 2004 15:25:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.11] (junior-wifi.samsco.home [192.168.0.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i8DFPr1L029181; Mon, 13 Sep 2004 09:25:53 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4145BB0D.20905@samsco.org> Date: Mon, 13 Sep 2004 09:21:49 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040831 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Roman Kurakin References: <414560D3.10108@cronyx.ru> <20040913105133.GA85717@hub.freebsd.org> <414581FE.6060702@cronyx.ru> In-Reply-To: <414581FE.6060702@cronyx.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org Subject: Re: Large mem disk with not very recent current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2004 15:25:22 -0000 Roman Kurakin wrote: > Kris Kennaway wrote: > >> On Mon, Sep 13, 2004 at 12:56:51PM +0400, Roman Kurakin wrote: >> >> >>> Hi, >>> >>> I have the following idea/problem. I want to build world in memory. >>> I've put in to my system 1G of memory and tried to put on it sources. >>> But all times I've tried to do that system went to panic. I've used md >>> with malloc type. >>> >>> Any ideas? >>> >> >> >> Please provide more information. It's likely you're trying to create >> a md that is too big, though. >> >> > It is about 800Mb. But system panics while I try to extract source tree. > It is not very recent > current. The intent of my question was to get some hints how to set up > such build area, I > belive it should help to make compilation much faster than using hard > drive. My home system > is not ready for panic investigation now. I'll update it to current and > set console to it and will > try again. > > > PS. Sorry to all for my last posts to current that are so weak in > "technical" details, the debug > technique I used before was without remote debugging since most of > problems were very > near my code and it was enough for me anlo three things: my mind, > printed sources, and printf. > So now I am in stage of adaptation to/setting up remote debugging. > > rik What kind of panic was it? Try using swap backing instead of malloc. Malloc will consume wired memory and will generally make life difficult for other parts of the kernel that need memory later. Swap-backed pages will stay in RAM until the VM needs to push them out due to memory pressure. Scott