From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 23:02:40 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 3D8B116A41F for ; Mon, 21 Nov 2005 23:02:40 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from bafirst.com (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 498D043D46 for ; Mon, 21 Nov 2005 23:02:39 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by bafirst.com with local; Mon, 21 Nov 2005 17:02:38 -0600 id 00095804.4382520E.00010C04 Received: from local4.local.net (local4.local.net [192.168.1.4]) by mail.bafirst.com (Horde MIME library) with HTTP; Mon, 21 Nov 2005 17:02:38 -0600 Message-ID: <20051121170238.45y62menj4gcgkc0@mail.bafirst.com> Date: Mon, 21 Nov 2005 17:02:38 -0600 From: eculp@bafirst.com To: freebsd-current@freebsd.org References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> <20051121030915.GC41629@dan.emsphone.com> <43813BBE.2010302@freebsd.org> <20051121034025.GD41629@dan.emsphone.com> <20051121131114.p7ed53lnkk4ckk4w@mail.bafirst.com> <20051121204018.GC760@pato.euesrg02.net> In-Reply-To: <20051121204018.GC760@pato.euesrg02.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Nov 2005 23:02:40 -0000 Quoting Victor Balada Diaz : > On Mon, Nov 21, 2005 at 01:11:14PM -0600, eculp@bafirst.com wrote: >> Thanks to all who have answered and I apologize for not finding this >> when searching google. I obviously needed to filter it more. As >> always now that I know what the problem probably is it is easy. >> >> I'm currently building kernel with PAE although it does make me a bit >> nervious to remotely reboot. I think I will first reboot enabling >> verbose with the debug.bootverbose sysctl variable since I only have >> remote access to the machine and no serial console. >> >> I will report back this weekend after rebooting with the PAE kernel >> that will hopefully work as expected. > > You can use nextboot(8) to try the new kernel in a 'safe' way. I had never seen nexboot. Neat. I'm going to give it a try. Thanks for the tip, Victor. ed