Date: Sun, 26 Jan 2003 15:32:23 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Eric Jones <fpicard@bellsouth.net> 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> In-Reply-To: <1043618525.630.4.camel@griffin.webcoven.org> References: <20030123173821.F3206-100000@oahu.WURLDLINK.NET> <20030124045626.GA8647@troutmask.apl.washington.edu> <1043618525.630.4.camel@griffin.webcoven.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030126233223.GB24897>