Bug 98259 - [KBL] [IGT] kms_rotation_crc / bad-pixel-format fails
Summary: [KBL] [IGT] kms_rotation_crc / bad-pixel-format fails
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-14 15:12 UTC by Luis Botello
Modified: 2017-03-17 21:55 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features: display/Other

Attachments
dmesg (44.51 KB, text/plain)
2016-10-14 15:12 UTC, Luis Botello 		no flags Details
IGToutput (9.58 KB, text/plain)
2016-10-14 15:12 UTC, Luis Botello 		no flags Details
View All

Description Luis Botello 2016-10-14 15:12:22 UTC 
Created attachment 127301 [details]
dmesg

Description:
=====================================================
kms_rotation_crc / bad-pixel-format fails produces a Test assertion failure.

Steps to reproduce:
========================================================
#./kms_rotation_crc --run-subtest bad-pixel-format fails

Software Config:
=====================================================
Kernel:
commit f35ed31aea66b3230c366fcba5f3456ae2cb956e
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Mon Oct 10 14:29:09 2016 +0300
    drm-intel-nightly: 2016y-10m-10d-11h-28m-51s UTC integration manifest

drm:
  tag: libdrm-2.4.71
  commit: a44c9c31b7b38b3eedf3d26648f9e68dcc377c4c
mesa:
  tag: mesa-12.0.0
  commit: 8b06176f310f65628ce136b90a99005278ba5e0d
cairo:
  tag: 1.15.2
  commit: db8a7f1697c49ae4942d2aa49eed52dd73dd9c7a
xorg-server-macros:
  tag: util-macros-1.19.0-2-gd7acec2
  commit: d7acec2d3a3abe79814ceb72e2c0d4d95ed31d37
xserver:
  tag: xorg-server-1.18.99.901-76-g97a8353
  commit: 97a8353ec1192d8d3bd2ebb99e5687cb91427e09
xf86-video-intel:
  tag: 2.99.917-712-g696f58f
  commit: 696f58f69f2bac5717d19f7a1a2278fee50a083e
libva:
  tag: libva-1.7.2-38-g3b7e499
  commit: 3b7e4999950a04fabd42edbead8c2f24c6cdf3cf
vaapi-intel-driver:
  tag: 1.7.2-133-gdd73514
  commit: dd73514209d7942f2d8c8b0bbb541fe6884ea1bc

Hardware Config:
========================================================
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])

Attachments:
=====================================================
dmesg
IGToutput
Comment 1 Luis Botello 2016-10-14 15:12:48 UTC 
Created attachment 127302 [details]
IGToutput
Comment 2 Luis Botello 2016-10-20 22:28:37 UTC 
Issue is still present over KBL with the following configuration

Software Configuration:
========================================================
Kernel:
Branch           : drm-intel-nightly WW42 
commit 15dfed2b90e84e7c277f81842fc3f19355293061
Author: Lyude <thatslyude@gmail.com>
Date:   Sun Oct 16 19:16:08 2016 -0400
    drm-intel-nightly: 2016y-10m-16d-23h-15m-00s UTC integration manifest

Component         : drm
        tag       : libdrm-2.4.71
        commit    : a44c9c31b7b38b3eedf3d26648f9e68dcc377c4c 
Component         : cairo
        tag       : 1.15.2
        commit    : db8a7f1697c49ae4942d2aa49eed52dd73dd9c7a 
Component         : intel-gpu-tools
        tag       : intel-gpu-tools-1.16-83-g54f8a3f
        commit    : 54f8a3f7cf12eea484a0b0641718ced559959f53
Comment 3 Jari Tahvanainen 2017-03-16 14:28:19 UTC 
Removing BXT since on 4.10.0-rc8-drm-tip-qa-ww7-commit-e80b772+ (BXT-1-NOTEBOOK) one has
igt@kms_ccs@bad-pixel-format		Pass
Comment 4 Jari Tahvanainen 2017-03-16 14:47:07 UTC 
Marking resolved+fixed since on 4.10.0-drm-tip-qa-ww9-commit-7f38bb9+ (KBL-1-MS-B1421)
igt@kms_ccs@bad-pixel-format		Pass
Unfortunately I do not have the commit that fixed this.

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.