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