Re: [issue557] 1.9.0-DEVELOPMENT hangs with ACPI enabled

["Mariano Aliaga" <marianoaliaga@xxxxxxxxx>]

On 2/20/07, YONETANI Tomokazu <bugs@lists.dragonflybsd.org> wrote:
> YONETANI Tomokazu <qhwt+dfly@les.ath.cx> added the comment:
>
>   HERE: acpi_cpu_attach:206
> In this case, it means that the driver locked up following the line 206 of
> acpi_cpu.c(the name before the number is the function name, and it resides
> in acpi_cpu.c).

OK, the last line was 219.

> And the next thing I'm going to tell you is to add two lines in the
> acpi_cpu.c like this:
>
>   kprintf("HERE: %s:%d\n", __func__, __LINE__); /* <== line 206 */
>       AcpiDbgLayer = ACPI_ALL_COMPONENTS;
>       AcpiDbgLevel = ACPI_LV_ALL;
>       status = AcpiEvaluateObject(handle, NULL, NULL, &buf);    /* <== possibly offending statement */
>       if (ACPI_FAILURE(status)) {

I added those two lines below 219, but after that the screen was
flooded with messages for more than 10 minutes, and I can't see/take a
picture of the last lines. So I tried with AcpiDbgLayer =
ACPI_PROCESSOR, and took a picture of the last messages of acpi driver
before . You can find it here
http://www.e-nix.com.ar/~maliaga/ACPI_PROCESSOR.jpg
I also tried with AcpiDbgLayer = ACPI_NAMESPACE, but the screen was
flooded again.

HTH

Regards.-

--
"El incremento de la satisfacción profesional y de la unidad familiar
son fatales para un proveedor de sustancias entumecedoras del cerebro."
Moe, 1991.