Re: increased power consumption lately?

There's a rather lengthy theory about it here
https://bugs.freedesktop.org/show_bug.cgi?id=98501


On Wed, Apr 26, 2017 at 11:15 PM, Adrian Chadd <adrian_at_freebsd.org> wrote:

> 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_at_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=98501
> >
> > 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
> fix
> > for this soon.
> >
> >
> >
> > On Thu, Apr 20, 2017 at 10:35 AM, Johannes Lundberg <johalun0_at_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_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
> >>>
> >>>
> >>
> >
>