[issue557] 1.9.0-DEVELOPMENT hangs with ACPI enabled

[Mariano Aliaga]

On 2/28/07, YONETANI Tomokazu <bugs at lists.dragonflybsd.org> wrote:
Does this reliably reproduce?  I mean it always yields the same result,
across reboot or after power-cycle?  I see 6 ProcId lines in dmesg output,
not 4, and none of them failed, unlike it did in the last picture.
Yes, it's always the same result: 6 ProcId lines. BUT, I wasn't sure
about how many times "acpi_pcpu_get_id() failed" appeared on previous
test. So I reverted changes on acpi_cpu.c and modified these lines as
before:
%%%%
      acpi_id = obj->Processor.ProcId;
kprintf("Before calling AcpiOsFree()\n");
      AcpiOsFree(obj);
kprintf("After calling AcpiOsFree()\n");
      if (acpi_pcpu_get_id(device_get_unit(dev), &acpi_id, &cpu_id) != 0) {
kprintf("acpi_pcpu_get_id() failed\n");
          return (ENXIO);
      }
kprintf("acpi_id: %d, cpu_id: %d\n", acpi_id, cpu_id);
%%%%

and started taking pictures to get a better shot. After watching them,
I saw that "acpi_pcpu_get_id() failed" appears only 3 times
(http://www.e-nix.com.ar/~maliaga/00003.jpg and
(http://www.e-nix.com.ar/~maliaga/00004.jpg). So sorry, I thought they
were 4 :-(
If it does, please try yet another patch attached to this message(after
reverting the last patches).  Also please make sure that the files in
/sys/dev/acpica5 or /sys/platform/pc32/acpica5 are up to date before
rebuilding the acpi driver.  This time you are going to try 6 to 11 for
debug.acpi.cpu.knob and see when it locks up.  If I'm not mistaken,
it should lock up before reaching to 11.
For this I cvsupped last changes, applied your patch, and tried from
knob 6 to 11. Unfortunately, it didn't lock on any of the tests, and
the messages where the same than previous tests with knob 0 to 5.
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.