[Bug 97049] New: [BXT] kms_pipe_color legacy-gamma-reset-pipe subtests are failing

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 97049
           Summary: [BXT] kms_pipe_color legacy-gamma-reset-pipe subtests
                    are failing
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: jairo.daniel.miramontes.caton at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 125262
  --> https://bugs.freedesktop.org/attachment.cgi?id=125262&action=edit
logs for kms_pipe_color legacy-gamma-reset for pipe 0 ,1 and 2

Unfortunately I was not able to find much valuable information on the logs when
this tests are executed, please let me know if more logs with different drm
flags are needed and I'll gather and upload them ASAP, the log I attached has
drm.debug=0xe flag on.

=== Software information ==
Kernel version: 4.7.0-rc7 with patch-revert-guc-loading-submission+
Linux distribution: Ubuntu 16.04 LTS
Architecture: 64-bit
xf86-video-intel version,2.99.917,
Xorg-Xserver version: 1.18.99.1,
DRM version: 2.4.68
Cairo version: 1.15.2
Kernel driver in use: i915
Bios revision: 144.10
KSC revision: 1.15

 === Hardware information ===
Platform: BXT-P
Motherboard model:Broxton P
Motherboard type: NOTEBOOK Hand Held
Motherboard manufacturer: Intel Corp.
CPU family:Other,
CPU information: 06/5c
GPU Card: Intel Corporation Device 5a84 (rev 0a) (prog-if 00 [VGA controller]),
Memory ram: 16 GB
Maximum memory ram allowed: 16 GB
Hard drive capacity:80.0 GB

Steps:
------
Execute commands:
cd <...>/intel-gpu-tools/tests
# ./kms_pipe_color --run-subtest legacy-gamma-reset-pipe0
# ./kms_pipe_color --run-subtest legacy-gamma-reset-pipe1
# ./kms_pipe_color --run-subtest legacy-gamma-reset-pipe2


Actual results:
-------------
Tests Fails with the following ouput: 
(kms_pipe_color:1407) CRITICAL: Test assertion failure function
test_pipe_legacy_gamma_reset, file kms_pipe_color.c:634:
(kms_pipe_color:1407) CRITICAL: Failed assertion: get_blob(data, primary->pipe,
"DEGAMMA_LUT") == NULL
Stack trace:
  #0 [__igt_fail_assert+0x101]
  #1 [run_tests_for_pipe+0x1d76]
  #2 [__real_main1158+0x59]
  #3 [main+0x23]
  #4 [__libc_start_main+0xf0]
  #5 [_start+0x29]
  #6 [<unknown>+0x29]
Subtest legacy-gamma-reset-pipe0 failed.
**** DEBUG ****
(kms_pipe_color:1407) igt-kms-DEBUG: display: eDP-1: set_pipe(A)
(kms_pipe_color:1407) igt-kms-DEBUG: display: commit {
(kms_pipe_color:1407) igt-kms-DEBUG: display:     eDP-1: Selecting pipe A
(kms_pipe_color:1407) igt-kms-DEBUG: display:     DP-2: Selecting pipe B
(kms_pipe_color:1407) igt-kms-DEBUG: display: }
(kms_pipe_color:1407) igt-kms-DEBUG: display: commit {
(kms_pipe_color:1407) igt-kms-DEBUG: display:     eDP-1: Selecting pipe A
(kms_pipe_color:1407) igt-kms-DEBUG: display:     DP-2: Selecting pipe B
(kms_pipe_color:1407) igt-kms-DEBUG: display: }
(kms_pipe_color:1407) igt-kms-DEBUG: display: commit {
(kms_pipe_color:1407) igt-kms-DEBUG: display:     eDP-1: Selecting pipe A
(kms_pipe_color:1407) igt-kms-DEBUG: display:     DP-2: Selecting pipe B
(kms_pipe_color:1407) igt-kms-DEBUG: display: }
(kms_pipe_color:1407) CRITICAL: Test assertion failure function
test_pipe_legacy_gamma_reset, file kms_pipe_color.c:634:
(kms_pipe_color:1407) CRITICAL: Failed assertion: get_blob(data, primary->pipe,
"DEGAMMA_LUT") == NULL
****  END  ****
Subtest legacy-gamma-reset-pipe0: FAIL

Expected results:
-----------------
Tests are marked as PASS

Kernel flags:
-----------------
drm.debug=0xe

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