Bug 55871

Summary: [i915 SNB] rc6 regression
Product: DRI Reporter: philipp
Component: DRM/IntelAssignee: Daniel Vetter <daniel>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: high CC: ben, chris, daniel, jbarnes
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg|grep drm
none
Xorg.0.log
none
hold rc6 while enabling rps none

Description philipp 2012-10-11 12:15:58 UTC
Created attachment 68436 [details]
dmesg|grep drm

Since kernel v3.6, my GPU is always active. In v3.6.1 this is still the case.

The software used besides (Ubuntu Quantal):
xf86-video-intel: 2:2.20.9-0ubuntu2
libdrm: 2.4.39+git20120830.7080bfdf-0ubuntu0ricotz2~precise
libgl1-mesa-dri: 9.0-0ubuntu1
xserver: 1.13.0

Sometimes, it helps to suspend and resume the system. It never uses any rc6-state after a fresh boot.  

The boot options are: pcie_aspm=force acpi_osi=Linux acpi_backlight=vendor i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.i915_enable_rc6=7 drm.debug=0x06 vt.handoff=7

Kernel v3.5 and earlier are fine.
Comment 1 philipp 2012-10-11 12:17:08 UTC
Created attachment 68437 [details]
Xorg.0.log
Comment 2 Chris Wilson 2012-10-11 12:19:25 UTC
Can you please clarify by 'always active'? /sys/kernel/debug/dri/0/i915_cur_delayinfo and /sys/kernel/debug/dri/0/i915_drpc_info would be useful, and in the extreme case a 'trace-cmd record -e i915' report.
Comment 3 Chris Wilson 2012-10-11 12:21:05 UTC
And please don't apply random hacks ' i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.i915_enable_rc6=7' without knowing the damage they may inflict upon your system.
Comment 4 Daniel Vetter 2012-10-29 16:15:02 UTC
Created attachment 69240 [details] [review]
hold rc6 while enabling rps

Can you please try this patch?
Comment 5 Ingemar Ã…dahl 2012-11-22 16:31:31 UTC

*** This bug has been marked as a duplicate of bug 54089 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.