increased power consumption lately?

[Johannes Lundberg]

Seem like a temporary solution on Linux is to disable the interrupt. Can
this be done on FreeBSD somehow?

On Thu, Apr 20, 2017 at 10:09 AM, Johannes Lundberg <johalun0 at gmail.com>
wrote:

> Thanks Ngie, that was a good one!  (I really need to learn dtrace...)
>
> Got this among other:
>
> AcpiNsLookup:entry PathInfo: \/ _SB_PCI0IGPUGSSE�GSMI\/ _SB_PCI0IGPUGSCI�K
> p
>
> Might be related to:
> https://bugs.freedesktop.org/show_bug.cgi?id=98501
>
>
>
> On Wed, Apr 5, 2017 at 8:15 PM, Ngie Cooper (yaneurabeya) <
> yaneurabeya at gmail.com> wrote:
>
>>
>> > On Apr 5, 2017, at 10:39, Adrian Chadd <adrian at freebsd.org> wrote:
>> >
>> > hm, you could use dtrace to find what's calling that function and
>> > print out the call stack?
>>
>>         *does shrug* something like this (I realize it’s not printing out
>> arg0 — arg0 is a union that would need decoding)?
>> Thanks,
>> -Ngie
>>
>> $ cat AcpiNsLookup.d
>> fbt:kernel:AcpiNsLookup:entry
>> {
>>         printf("PathInfo: %s\nType: %d\nFlags: %u",
>>             stringof(arg1), arg2, arg3);
>> }
>> $ sudo dtrace -s AcpiNsLookup.d
>>
>
>