[Bug 68150] New: DebugFS reporting wrong RC-state on ilk

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Aug 15 07:43:20 PDT 2013


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

          Priority: medium
            Bug ID: 68150
                CC: ben at bwidawsk.net
          Assignee: jbarnes at sgi.com
           Summary: DebugFS reporting wrong RC-state on ilk
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: joecool1029 at gmail.com
          Hardware: x86-64 (AMD64)
            Status: ASSIGNED
           Version: XOrg CVS
         Component: DRM/Intel
           Product: DRI

Patched in this series of patches from bwidawsk to test RC6 state on ILK.
http://lists.freedesktop.org/archives/intel-gfx/2013-July/030263.html

Issue was seeing if it ever reached RC6 state, sysfs has no interface for this
anymore.  I poked around in debugFS and found i915_drpc_info.

cat /sys/kernel/debug/dri/64/i915_drpc_info
HD boost: yes
Boost freq: 9
HW control enabled: no
SW control enabled: yes
Gated voltage change: no
Starting frequency: P8
Max P-state: P0
Min P-state: P10
RS1 VID: 0
RS2 VID: 8
Render standby enabled: yes
Current RS state: RC1


It also shows RS state: on if performing activity on the GPU.  Tried polling
repeatedly using:

while [ 1 ] ; do grep "Current" /sys/kernel/debug/dri/0/i915_drpc_info >>
out.txt ; sleep .01; done

Still bounced between RC1 and on, never hitting RC6


However, if I use intel-gpu-tools and run:

intel_reg_read 0x111b8
I see:

0x111B8 : 0x474C3000 (RS2/RC6)
or
0x111B8 : 0x471C3000 (RS1)
or 
0x111B8 : 0x470C3000 (on)

Though today I'm seeing just:

0x111B8 : 0x0
0x111B8 : 0x100000

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


More information about the intel-gfx-bugs mailing list