Bug 93927

Summary: [APL] pm_rc6_residency fails
Product: DRI Reporter: cprigent <christophe.prigent>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED WORKSFORME QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: BXT i915 features: power/runtime PM
Attachments:
Description Flags
dmesg none

Description cprigent 2016-01-29 14:04:22 UTC
Created attachment 121392 [details]
dmesg

Setup:
======
Platform: Broxton P A0 Platform
CPU Name : Intel(R) @ 1.2 GHz (family: 6, model: 92, stepping: 8) – 4 cores
SoC : BROXTON-P A0
CRB :  Apollo Lake RVPC1 Fab1 
Reworks : R14, R06C and R16

Software:
=========
BIOS (IFWI Version): APLK_IFWI_X64_R_2015_41_5_02 
KSC : 1.02
Linux distribution: Ubuntu 15.10 64 bits
Kernel: drm-intel-nightly 4.4.0 8114b00 from http://cgit.freedesktop.org/drm-intel/
drm: tag libdrm-2.4.66 e342c0f from http://cgit.freedesktop.org/mesa/drm/
mesa: tag mesa-11.0.8 261daab from http://cgit.freedesktop.org/mesa/mesa/
cairo: tag 1.15.2 db8a7f1 from http://cgit.freedesktop.org/cairo
waffle: master bb29b2a from https://github.com/waffle-gl/waffle
xorg-server-macros: master d7acec2 from git://git.freedesktop.org/git/xorg/util/macros
libva: tag libva-1.6.1 cb418f6 from http://cgit.freedesktop.org/libva/
vaapi-intel-driver: tag 1.6.1 2110b3a from http://cgit.freedesktop.org/vaapi/intel-driver

Tool:
======
intel-gpu-tool: tag intel-gpu-tools-1.13 51e965f from http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/

Connect one monitor to HDMI port (Asus PB287Q)

Steps:
------
1. Execute command:
sudo -s
cd <…>/intel-gpu-tools/tests
./pm_rc6_residency

Actual result:
--------------
1. Subtests are fail or skip

IGT-Version: 1.13-NOT-GIT (x86_64) (Linux: 4.4.0-nightly+ x86_64)
Residency in rc6 or deeper state: 0 ms (sleep duration 3454 ms) (ratio to expected duration: 0.00)
(pm_rc6_residency:1198) CRITICAL: Test assertion failure function residency_accuracy, file pm_rc6_residency.c:110:
(pm_rc6_residency:1198) CRITICAL: Failed assertion: ratio > 0.9 && ratio <= 1
(pm_rc6_residency:1198) CRITICAL: Sysfs RC6 residency counter is inaccurate.
Stack trace:
  #0 [__igt_fail_assert+0xf1]
  #1 [residency_accuracy+0x86]
  #2 [__real_main192+0x136]
  #3 [main+0x29]
  #4 [__libc_start_main+0xf0]
  #5 [_start+0x29]
  #6 [<unknown>+0x29]
Subtest rc6-accuracy failed.
**** DEBUG ****
(pm_rc6_residency:1198) DEBUG: Test requirement passed: !(!(rc6_mask & RC6_ENABLED))
(pm_rc6_residency:1198) INFO: Residency in rc6 or deeper state: 0 ms (sleep duration 3454 ms) (ratio to expected duration: 0.00)
(pm_rc6_residency:1198) CRITICAL: Test assertion failure function residency_accuracy, file pm_rc6_residency.c:110:
(pm_rc6_residency:1198) CRITICAL: Failed assertion: ratio > 0.9 && ratio <= 1
(pm_rc6_residency:1198) CRITICAL: Sysfs RC6 residency counter is inaccurate.
****  END  ****
Subtest rc6-accuracy: FAIL (0.179s)
Test requirement not met in function __real_main192, file pm_rc6_residency.c:218:
Test requirement: !(!((rc6_mask & RC6_ENABLED) && (IS_VALLEYVIEW(devid) || IS_CHERRYVIEW(devid))))
Subtest media-rc6-accuracy: SKIP (0.000s)
Test requirement not met in function __real_main192, file pm_rc6_residency.c:223:
Test requirement: !(!(rc6_mask & RC6P_ENABLED))
Subtest rc6p-accuracy: SKIP (0.000s)
Test requirement not met in function __real_main192, file pm_rc6_residency.c:228:
Test requirement: !(!(rc6_mask & RC6PP_ENABLED))
Subtest rc6pp-accuracy: SKIP (0.000s)

Expected result:
----------------
At least subtest rc6-accuracy is Pass
Comment 1 Imre Deak 2016-01-29 14:10:48 UTC
Do you have RC6 enabled in BIOS? Please see the following for which options are needed:
https://bugs.freedesktop.org/show_bug.cgi?id=93872
Comment 2 cprigent 2016-01-29 16:01:17 UTC
Sorry, I confirm it works with options activated from Bios.
Comment 3 cprigent 2016-01-29 16:01:29 UTC
So closed

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.