Re: Can't debug ACPI

A followup regarding ACPI debugging. It turns out that, to use any 
of the debugging features of the ACPI driver, one has to add

options DDB

and

options KDB

in the kernel configuration as well as

options ACPI_DEBUG

I've now enabled the debugging features, but have made no headway 
in solving the problems with the MeLE single board Celeron N4000 
computer by using them. Disabling the "ec" and "cmbat" portions of 
ACPI does not help.

However, from the error messages I see on the console during and 
after boot, it appears that the ACPI driver is searching for data 
and code in an area very high in the address space - far outside 
the range where all of the other blocks of ACPI code and data are 
located. This leads me to believe that the driver has walked past 
the edge of an array and is interpreting random junk as ACPI information.

Windows works on the computer without error, so whatever is going 
wrong seems to be specific to the FreeBSD implementation of ACPI. 
Alas, I don't know enough about the code, or the implementation of 
ACPI, to debug on my own. Can someone help?

--Brett Glass