[Bug 89123] New: [SKL]igt/pm_rps/blocking fail

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Feb 12 21:21:40 PST 2015


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

            Bug ID: 89123
           Summary: [SKL]igt/pm_rps/blocking fail
           Product: DRI
           Version: unspecified
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: huax.lu at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 113442
  --> https://bugs.freedesktop.org/attachment.cgi?id=113442&action=edit
dmesg

==System Environment==
--------------------------
Regression: not sure

no-working platforms: SKL

==kernel==
--------------------------
drm-intel-nightly/b4442ee4e150506cebeee72249efc566c5f14bbe
commit b4442ee4e150506cebeee72249efc566c5f14bbe
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date:   Fri Feb 6 10:25:31 2015 +0100

    drm-intel-nightly: 2015y-02m-06d-09h-25m-00s UTC integration manifest

==Bug detailed description==
-----------------------------
It fails on SKL with -nightly kernel.

output:
IGT-Version: 1.9-g9846e7f (x86_64) (Linux:
3.19.0-rc7_drm-intel-nightly_b4442e_20150208+ x86_64)
(pm_rps:5289) CRITICAL: Test assertion failure function matchit, file
pm_rps.c:165:
(pm_rps:5289) CRITICAL: Failed assertion: freqs1[CUR] == freqs2[CUR]
(pm_rps:5289) CRITICAL: error: 350 != 600
Subtest blocking: FAIL (35.257s)

==Reproduce steps==
---------------------------- 
1. ./pm_rps --run-subtest blocking

-- 
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/20150213/5df29fa8/attachment-0001.html>


More information about the intel-gfx-bugs mailing list