Date: Wed, 8 Feb 2006 20:33:32 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Nate Lawson <nate@root.org> Cc: freebsd-acpi@freebsd.org Subject: Re: Kernel panic with ACPI enabled Message-ID: <20060208093332.GA702@turion.vk2pj.dyndns.org> In-Reply-To: <43E9A4CA.9090701@root.org> References: <43E7D1A2.1030008@o2.pl> <200602071404.44314.jhb@freebsd.org> <200602071413.07109.duncan.fbsd@gmail.com> <200602071552.33235.jhb@freebsd.org> <43E9A4CA.9090701@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2006-Feb-07 23:59:06 -0800, Nate Lawson wrote: >John Baldwin wrote: >>Actually, in his case I'm fairly sure MAXMEM is the problem. Several >>people have had problems trying to use the tunable equivalent >>(hw.physmem=3g and the like) because if the new maxmem value is greater > >Can we at least put a printf() in the boot sequence that says "warning: >maxmem set and acpi enabled, this may cause problems"? This keeps >coming up. Presumably this isn't a problem where hw.physmem is used to artifically reduce the system for testing. -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060208093332.GA702>