DragonFlyBSD

I assume this happened with a kernel config that does not have ACPI_DEBUG specified?

Regards,
Sascha

I am using GENERIC with this machine so ACPI_DEBUG should not be specified.

Thanks for reverting, now using master through

commit b9a827c2b9a282d39b2a3d81e9d1a2dcb54ab162
Date: Mon May 12 07:01:42 2014 +0200

Revert "kernel/acpi: Improve the disabling of Debug object dumping."

I no longer have the [ACPI Debug] messages flooding the console on this machine.

Here is a new version of the commit with an additional debug printf. Can you try it out and tell me what it prints before the "[ACPI Debug]" lines? It should be something like "AcpiGbl_EnableAmlDebugObject:... AcpiDbgLevel:...".

Sorry, the patch is here: http://leaf.dragonflybsd.org/~swildner/acpi_enable_debug_objects.diff

I've mailed devel@acpica.org for clarification about this issue, since it looks like a flaw in their code.

Output from debug objects should be disabled by default (via the AcpiGbl_EnableAmlDebugObject global which defaults to FALSE and which the commit made tweakable (without messing with the default)), but due to some issues in the way they check this global and how it interacts with the AcpiDbgLevel global, they get printed anyway.

I'll see what they have to say about it.