Date: Sun, 12 Oct 2014 10:19:59 -0400 From: Eric McCorkle <eric@metricspace.net> To: Ian Smith <smithi@nimnet.asn.au> Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI debug messages Message-ID: <543A8E0F.9000000@metricspace.net> In-Reply-To: <20141012220103.X56328@sola.nimnet.asn.au> References: <5439727F.4070602@metricspace.net> <20141012220103.X56328@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks. I turned on maximum logging, tried starting X, and walked through the traces. I think I can definitely rule out the ACPI error messages as being relevant at this point. The argument type check fails, but the methods all execute normally. The actual issue seems to be optimus-related instead. Thanks for all the help, though. On 10/12/2014 07:14, Ian Smith wrote: > 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?543A8E0F.9000000>