DragonFly bugs List (threaded) for 2007-02
DragonFly BSD
DragonFly bugs List (threaded) for 2007-02
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

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

From: "Mariano Aliaga" <marianoaliaga@xxxxxxxxx>
Date: Mon, 26 Feb 2007 09:55:40 -0300

On 2/24/07, YONETANI Tomokazu <bugs@lists.dragonflybsd.org> wrote:

hw.acpi.cpu sysctl knob? The picture is somewhat overwrapped, but it seems that acpi_pcpu_get_id() failed for both units. You saw 4 "acpi_pcpu_get_id() failed" message, right? I think the lock-up occurred somewhere other than acpi_cpu_probe(), after returning from it, but whether it locks up or not depends on what acpi_cpu_probe() does.

Yes, "acpi_pcpu_get_id() failed" appears 4 times.

I wrote another patch to find it.  Please apply attached patch after
reverting the previous change, and install the driver.  Boot into the
boot loader prompt, and type(without other debug.acpi variables set)
the following two lines to boot into single-user mode:
  set debug.acpi.cpu.knob=5
  boot -sv
if it locks up, write down(or take a picture of) lines containing "ProcId",
which looks like this:
  cpu0: ProcId 1: acpi_id=0, cpu_id=0
  cpu0: ProcId 1: can't find cpu_id

With debug.acpi.cpu.knob=5 I get 2 of this messages (dmesg attached), and the system doesn't lock up. I tried 4, 3, 2, 1 just in case, but Procid messages don't appear and the system also doesn't lock up.


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

Attachment: dmesg.knob5.gz
Description: GNU Zip compressed data

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]