[Bug 88563] New: [HSW][i915][HD 4600] GPU preventing package state from fully reaching PC6

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Jan 18 12:50:54 PST 2015


https://bugs.freedesktop.org/show_bug.cgi?id=88563

            Bug ID: 88563
           Summary: [HSW][i915][HD 4600] GPU preventing package state from
                    fully reaching PC6
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: shawn.starr at rogers.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

I am unable to get processor package c-state to PC6 fully, upon testing various
things.

I have narrowed this down to the i915.

Here is my current cmdline for booting up laptop:

rhgb slub_debug=- cgroup_disable=memory console=tty0 console=ttyS0,115200n8
radeon.audio=0 snd_hda_intel.power_save=1 nmi_watchdog=0 i915.powersave=1
intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 zswap.zpool=zsmalloc
zswap.enabled=1 radeon.backlight=0 video=eDP-1:d video=VGA-2:e video=VGA-1:d
video=VGA-1-0:d pcie_aspm=off i915.enable_rc6=1 i915.i915_enable_rc6=1

Kernels: 3.19-rc4 (stock), 3.19-rc4 (intel-drm-nightly) both show same result.

I can get the package state to PC7 by setting dpms force on VGA-2 output, then
we reach PC7 95%+ of time, upon wakeup it returns to PC2 state for majority of
sleep.

The GPU is reaching its own RC6 state 99% of time in my testing so that is
working fine.

Any tools I can use to see why it is preventing deeper PC sleep states?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150118/f7885f27/attachment.html>


More information about the intel-gfx-bugs mailing list