From owner-freebsd-current Sun Jan 26 16: 7: 6 2003 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 0B9F137B401 for ; Sun, 26 Jan 2003 16:07:05 -0800 (PST) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99D6643F18 for ; Sun, 26 Jan 2003 16:07:04 -0800 (PST) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com wa1ter@smtp-send.myrealbox.com [66.126.109.206] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.23 $ on Novell NetWare via secured & encrypted transport (TLS); Sun, 26 Jan 2003 17:07:08 -0700 Message-ID: <3E34787F.7020201@hotmail.com> Date: Sun, 26 Jan 2003 16:08:31 -0800 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3a) Gecko/20030125 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Options MAXMEM added to GENERIC kernel config causes kernel panic in -current References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed 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 Steve Kargl wrote: > On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote: >>Is there any reason, on newer motherboards, to need the MAXMEM option? > I don't know. I've always used MAXMEM. Guess it's > time to remove it from my kernel config file. FWIW, I've been using FBSD -stable and -current for about 3 years on five different machines and I've never used MAXMEM. Never had any problems recognizing memory, either -- guess I've been luckier than some. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message