Date: Wed, 26 Apr 2017 14:15:21 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Johannes Lundberg <johalun0@gmail.com> Cc: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: increased power consumption lately? Message-ID: <CAJ-Vmon7nLOdcgbdAFAB1hOoF6hv5HQELWXp%2BFdWeALuDsCriA@mail.gmail.com> In-Reply-To: <CAECmPwsJWFxwHzTNxWrE9uGXxArsCocCquf-b=hVvki5X4LzMw@mail.gmail.com> References: <CAJ-VmomW0=8Zj=o7NRadefYyrWepTG=r4xh80fQKUT3JiUd8Vg@mail.gmail.com> <CAECmPwuRQQZkZ1qJBAkaGTH8erX8b=evpTFiA7qCQR4DOfhQzw@mail.gmail.com> <CAJ-Vmo=PqTEBLKgCh%2BuH1UHzt5YWdD11f46j4vuZ6cLZbaVjAQ@mail.gmail.com> <CAECmPwtrS5h1AhW1uLgW=sFam8wwo0hb3RFNBYOepFRoON8Dbw@mail.gmail.com> <CAJ-Vmo=O9Lviq2%2BC0Z%2BWCTAE=dHG01N7p8a%2BJicw8vhChjV2Ag@mail.gmail.com> <CAECmPwsFt2aOprnLptYe_L%2BD0xFRONP1kAg2%2BmHvb0cLK7vz3Q@mail.gmail.com> <CAJ-Vmo=g5jye9b5KGeOdVY7gcryxu07OVE3AXOK2LMg5_BsnWQ@mail.gmail.com> <DA046A06-D7F8-486D-BB4D-7ADA4EF5418F@gmail.com> <CAECmPwspOvNsKrTgG3wXrmN%2BRqLa_e6RYo-SY6k6cS2K4hHBFw@mail.gmail.com> <CAECmPwvCxDqeUiWoqthOm_qVEh8q=ob0uN5sjBS7Z%2BzjYNC0ig@mail.gmail.com> <CAECmPwsJWFxwHzTNxWrE9uGXxArsCocCquf-b=hVvki5X4LzMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
can you file a bugzilla bug with this information in it? What's
triggering the interrupt?
-a
On 20 April 2017 at 02:05, Johannes Lundberg <johalun0@gmail.com> wrote:
> I found another solution. Modifying the DSDT file by removing
>
> Method (_L06, 0, NotSerialized) // _Lxx: Level-Triggered GPE
> {
> If (LAnd (\_SB.PCI0.IGPU.GSSE, LNot (GSMI)))
> {
> \_SB.PCI0.IGPU.GSCI ()
> }
> Else
> {
> Store (0x00, \_SB.PCI0.IGPU.GEFC)
> Store (0x01, SCIS) /* \SCIS */
> Store (0x00, \_SB.PCI0.IGPU.GSSE)
> Store (0x00, \_SB.PCI0.IGPU.SCIE)
> }
> }
>
> seem to solve the problem, as discussed here
> https://bugs.freedesktop.org/show_bug.cgi?id=3D98501
>
> I will keep an eye on that bug report and see what happens.
> I should also mention that I am running the Linux i915kms driver
> https://github.com/FreeBSDDesktop/freebsd-base-graphics
>
> Since we're constantly merging updates from Linux maybe there will be a f=
ix
> for this soon.
>
>
>
> On Thu, Apr 20, 2017 at 10:35 AM, Johannes Lundberg <johalun0@gmail.com>
> wrote:
>>
>> 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@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=EF=BF=BDGSMI\/
>>> _SB_PCI0IGPUGSCI=EF=BF=BDK p
>>>
>>> Might be related to:
>>> https://bugs.freedesktop.org/show_bug.cgi?id=3D98501
>>>
>>>
>>>
>>> On Wed, Apr 5, 2017 at 8:15 PM, Ngie Cooper (yaneurabeya)
>>> <yaneurabeya@gmail.com> wrote:
>>>>
>>>>
>>>> > On Apr 5, 2017, at 10:39, Adrian Chadd <adrian@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=E2=80=99s not p=
rinting
>>>> out arg0 =E2=80=94 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
>>>
>>>
>>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmon7nLOdcgbdAFAB1hOoF6hv5HQELWXp%2BFdWeALuDsCriA>