From owner-freebsd-acpi@FreeBSD.ORG Sat Oct 11 18:10:15 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C4BBD8C for ; Sat, 11 Oct 2014 18:10:15 +0000 (UTC) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::103]) by mx1.freebsd.org (Postfix) with ESMTP id CC64564A for ; Sat, 11 Oct 2014 18:10:14 +0000 (UTC) Received: from [192.168.42.24] (unknown [172.16.0.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id E916E2F1D1 for ; Sat, 11 Oct 2014 18:10:07 +0000 (UTC) Message-ID: <5439727F.4070602@metricspace.net> Date: Sat, 11 Oct 2014 14:10:07 -0400 From: Eric McCorkle User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Subject: ACPI debug messages Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Oct 2014 18:10:15 -0000 Hello, I decided to try tracing through the evaluation of the DSM method in order to track down where the graphics driver failure I mentioned earlier is coming from. However, it looks like there's already an extensive debug logging system in place in the acpica system. Can this be controlled from user space (presumably through sysctls), or does it need to be compiled in?