DragonFly BSD
DragonFly kernel List (threaded) for 2004-06
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: acpica5 issues

From: Rahul Siddharthan <rsidd@xxxxxxxxx>
Date: Tue, 1 Jun 2004 00:23:40 -0400

YONETANI Tomokazu said on May 30, 2004 at 13:51:16:
> As I thought I can't help you just by looking at the dmesg :(
> Ok, there is a variable called debug.acpi.disabled (in non-patched
> version it's debug.acpi.disable) to disable individual acpi subsystems.
> When you have time, can you try to find out what subsystem triggers
> the hang? The variable is a space-separated list and to be set at the
> boot loader; for instance, if you want disable "cpu" and "lid",
> type as follows from the boot loader:
> OK set debug.acpi.disabled="cpu lid"
> If you include "acpi", acpi itself is disabled. The valid subsystem
> names are(you can find out by grep'ing acpi_disabled in /sys/dev/acpica5):
> "acad" "acpi" "bus" "button" "children" "cmbat" "cpu" "ec"
> "isa" "lid" "pci" "pci_link" "sysresource" "thermal" "timer"

OK, the culprit seems to be "thermal".  If I disable that, the machine
boots and stays up (so far).

Disabling "bus" and "children" also works but most acpi stuff is then

I'm using your recent May 30 patches.

In case it's useful, the dmesg from boot -v is at

Even now, embedded controller related things (battery status,
brightness hotkeys) don't work.  As I reported earlier, they didn't on
FreeBSD either, but do on linux, Nate Lawson said it's something to do
with needing to program the ELCR registers.



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