From owner-freebsd-current Sun Jan 26 15:32:26 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 9835837B401 for ; Sun, 26 Jan 2003 15:32:25 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22E5943F18 for ; Sun, 26 Jan 2003 15:32:25 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.6/8.12.6) with ESMTP id h0QNWNXv024989; Sun, 26 Jan 2003 15:32:23 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.6/8.12.6/Submit) id h0QNWNUH024988; Sun, 26 Jan 2003 15:32:23 -0800 (PST) Date: Sun, 26 Jan 2003 15:32:23 -0800 From: Steve Kargl To: Eric Jones Cc: freebsd-current@FreeBSD.ORG Subject: Re: Options MAXMEM added to GENERIC kernel config causes kernel panic in -current Message-ID: <20030126233223.GB24897@troutmask.apl.washington.edu> References: <20030123173821.F3206-100000@oahu.WURLDLINK.NET> <20030124045626.GA8647@troutmask.apl.washington.edu> <1043618525.630.4.camel@griffin.webcoven.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1043618525.630.4.camel@griffin.webcoven.org> User-Agent: Mutt/1.4i 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 On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote: > On Thu, 2003-01-23 at 23:56, Steve Kargl wrote: > > > > > > > Disable acpi. acpi is broken. > > I had the same problem until today. If ACPI was enabled, I would get a > panic on boot. I removed MAXMEM from my kernel conf, recompiled, and > voila, no panic. ACPI looks like its working, according to the dmesg, > where any attempt to load it before panicked with pmap_mapdev: Couldn't > alloc kernel virtual memory. > > 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. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message