Kernel panic with ACPI enabled

Przemysław Celej p-celej at o2.pl
Tue Feb 7 15:09:08 PST 2006


John Baldwin wrote:
> On Tuesday 07 February 2006 15:13, Donald J. O'Neill 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 than the highest memory 
> address we found, we just extend the last segment of physical memory.  
> However, in the case of modern machines with SMAPs, this extension can result 
> in including memory that was specifically marked as unavailable (because it 
> was in use by the BIOS to store the ACPI tables) suddenly being used by the 
> kernel.  As part of this process, the kernel does test writes to each page, 
> so it would corrupt the ACPI tables and eventually lead to issues such as 
> this.
>
>   
Exactly !
I removed MAXMEM option, and: NO_MEMORY_HOLE , CPU_UPGRADE_HW_CACHE,
CPU_FASTER_5X86_FPU, CPU_SUSP_HLT, CPU_ATHLON_SSE_HACK.
And ACPI now works perfectly.

Huge thanks.

-- 
Pozdrawiam
Przemysław Celej




More information about the freebsd-acpi mailing list