ACPI problems with this morning's -CURRENT

[Nate Lawson]

> (To recap: I'm having ACPI problems on a DFI CD70-SC, with both 5.1-R and
> 5-CURRENT.  Booting GENERIC doesn't show any problems, however, so there's
> a good chance it's a misconfiguration issue.)
>
> Thus spake Damian Gerow (damian at sentex.net) [15/09/03 17:34]:
> > It's attached.  There's no APM in there.  I did some more testing --
> GENERIC works for the -CURRENT date I stated before, and 5.1-R.  As soon
> as I compile my own kernel, it breaks.
>
>Okay, here's a backtrace with debugging.  Unfortunately, when dropped to the
>debugging prompt, I don't know what to do.  Attached is the kernel config I
>used to generate this on 5.1-R, I can re-do this on -CURRENT if need be.
>
>Here's a snippet of boot, and the stack backtrace:
>
>    ...
>    Preloaded elf kernel "/boot/kernel/kernel" at 0xc04b8000
>    Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04b81f4
>    ...
>    real memory  = 536870912 (512 MB)
>    avail memory = 516313088 (492 MB)
>    panic: pmap_mapdev: Couldn't allocate kernel virtual memory
>    Stack backtrace:
>    backtrace(c035b0cc,c03baea0,c0372994,c04dabbc,100) at backtrace+0x17
>    panic(c0372994,c036f000,0,0,0) at panic+0x93
>    pmap_mapdev(1fff3000,c036ec14,c04dac48,c04dabcc,c048e880) at pmap_mapdev+0x4b
>    AcpiOsMapMemory(1fff3000,0,c036ec14,c04dabbc,c04dabc4) atAcpiOsMapMemory+0x1e

I'm almost certain your problem is defining MAXMEM to 512 MB.  Remove that
from your kernel config and try again.  MAXMEM causes all kinds of
problems.  If this doesn't solve it, start with the stock GENERIC and add
back in your custom kernel options until it fails.  The last option you
add is the faulty one.

-Nate