From owner-freebsd-acpi@FreeBSD.ORG Sun Oct 12 11:15:00 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 56984277 for ; Sun, 12 Oct 2014 11:15:00 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 20A3C911 for ; Sun, 12 Oct 2014 11:14:57 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id s9CBEsDq093002; Sun, 12 Oct 2014 22:14:54 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 12 Oct 2014 22:14:53 +1100 (EST) From: Ian Smith To: Eric McCorkle Subject: Re: ACPI debug messages In-Reply-To: <5439727F.4070602@metricspace.net> Message-ID: <20141012220103.X56328@sola.nimnet.asn.au> References: <5439727F.4070602@metricspace.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org 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: Sun, 12 Oct 2014 11:15:00 -0000 On Sat, 11 Oct 2014 14:10:07 -0400, Eric McCorkle wrote: > 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? It's all in acpi(4), and in the Handbook in the nowadays rather poorly-named "Power and Resource Management" at section 12.13.4: http://www.freebsd.org/doc/handbook/acpi-overview.html You can add it to your kernel, but I think acpi is now always loaded as a module, therefore you just need to rebuild the module, as described. cheers, Ian