drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
Subsystems (3)
PATCH 1/1 drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
From: Sean Paul <[email protected]>
The HDCP 1.4 spec does not require the QUERY_STREAM_ENCRYPTION_STATUS check, it was always a nice-to-have. After deploying this across various devices, we've determined that some MST bridge chips do not properly support this call for HDCP 1.4 (namely Synaptics and Realtek).
I had considered creating a quirk for this, but I think it's more prudent to just disable the check entirely since I don't have an idea how widespread support is.
--- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 26 +------------------- 1 file changed, 1 insertion(+), 25 deletions(-)
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +1 -25
@@ -640,30 +640,6 @@ intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,return ret; } -static -bool intel_dp_mst_hdcp_check_link (struct intel_digital_port *dig_port, -struct intel_connector *connector) -{ -struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); -struct intel_dp *intel_dp = &dig_port->dp; -struct drm_dp_query_stream_enc_status_ack_reply reply; -int ret; - -if (!intel_dp_hdcp_check_link (dig_port, connector)) -return false; - - ret =drm_dp_send_query_stream_enc_status (&intel_dp->mst_mgr, - connector->port, &reply); -if (ret) { -drm_dbg_kms (&i915->drm, -"[CONNECTOR:%d:%s] failed QSES ret=%d\n" , - connector->base.base.id, connector->base.name, ret); -return false; - } - -return reply.auth_completed && reply.encryption_enabled; -} -static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .write_an_aksv = intel_dp_hdcp_write_an_aksv, .read_bksv = intel_dp_hdcp_read_bksv,
@@ -674,7 +650,7 @@ static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .read_ksv_fifo = intel_dp_hdcp_read_ksv_fifo, .read_v_prime_part = intel_dp_hdcp_read_v_prime_part, .toggle_signalling = intel_dp_mst_hdcp_toggle_signalling, - .check_link = intel_dp_mst_hdcp_check_link, + .check_link = intel_dp_hdcp_check_link, .hdcp_capable = intel_dp_hdcp_capable, .protocol = HDCP_PROTOCOL_DP,
Signature · 6 lines
Sean Paul, Software Engineer, Google / Chromium OS _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
== Series Details ==
== Series Details ==
Series: drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
URL : https://patchwork.freedesktop.org/series/85555/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9554 -> Patchwork_19275
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/index.html
Known issues
------------
Here are the changes found in Patchwork_19275 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@fbdev@read:
- fi-tgl-y: [PASS][1] -> [DMESG-WARN][2] ([i915#402]) +2 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/fi-tgl-y/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/fi-tgl-y/igt@[email protected]
#### Possible fixes ####
* igt@i915_pm_rpm@module-reload:
- fi-kbl-guc: [FAIL][3] ([i915#579]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/fi-kbl-guc/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/fi-kbl-guc/igt@[email protected]
* igt@vgem_basic@dmabuf-fence:
- fi-tgl-y: [DMESG-WARN][5] ([i915#402]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/fi-tgl-y/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/fi-tgl-y/igt@[email protected]
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#579]: https://gitlab.freedesktop.org/drm/intel/issues/579
Participating hosts (42 -> 37)
------------------------------
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_9554 -> Patchwork_19275
CI-20190529: 20190529
CI_DRM_9554: 4786f2a4c7e280974d0b46ca9e30a156eb528d59 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5945: f0ad1a564956d6796d9ff09182c48d78fb00eefe @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19275: bd6eed3a74e7aef1dde724eacb490413d8b3ee79 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
bd6eed3a74e7 drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
In reply to Sean Paul== Series Details ==
== Series Details ==
Series: drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
URL : https://patchwork.freedesktop.org/series/85555/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9554_full -> Patchwork_19275_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_19275_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_19275_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_19275_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_flip_tiling@flip-to-y-tiled@edp-1-pipe-c:
- shard-skl: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl6/igt@kms_flip_tiling@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl10/igt@kms_flip_tiling@[email protected]
Known issues
------------
Here are the changes found in Patchwork_19275_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@cursor-dpms:
- shard-iclb: [PASS][3] -> [DMESG-WARN][4] ([i915#1226])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-iclb6/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-iclb5/igt@[email protected]
* igt@i915_pm_rpm@system-suspend-execbuf:
- shard-skl: [PASS][5] -> [INCOMPLETE][6] ([i915#146] / [i915#151])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl7/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl3/igt@[email protected]
* igt@kms_async_flips@test-time-stamp:
- shard-skl: [PASS][7] -> [DMESG-FAIL][8] ([i915#142])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl8/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl1/igt@[email protected]
* igt@kms_chamelium@dp-frame-dump:
- shard-skl: NOTRUN -> [SKIP][9] ([fdo#109271] / [fdo#111827]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl8/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-256x85-offscreen:
- shard-skl: [PASS][10] -> [FAIL][11] ([i915#54]) +5 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl5/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl1/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-128x42-offscreen:
- shard-skl: NOTRUN -> [FAIL][12] ([i915#54])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl8/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-skl: NOTRUN -> [FAIL][13] ([i915#2346])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl5/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@c-edp1:
- shard-skl: [PASS][14] -> [FAIL][15] ([i915#79])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl5/igt@kms_flip@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl1/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@c-hdmi-a2:
- shard-glk: [PASS][16] -> [FAIL][17] ([i915#79])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-glk9/igt@kms_flip@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-glk9/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@c-edp1:
- shard-skl: [PASS][18] -> [INCOMPLETE][19] ([i915#2295])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl6/igt@kms_flip@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-ts-check-interruptible@b-edp1:
- shard-skl: [PASS][20] -> [FAIL][21] ([i915#2122])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl9/igt@kms_flip@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl9/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-blt:
- shard-skl: NOTRUN -> [SKIP][22] ([fdo#109271]) +31 similar issues
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl8/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-render:
- shard-kbl: NOTRUN -> [SKIP][23] ([fdo#109271]) +12 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-kbl1/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-render.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-skl: NOTRUN -> [FAIL][24] ([i915#265])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [PASS][25] -> [FAIL][26] ([fdo#108145] / [i915#265])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl6/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl10/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [PASS][27] -> [SKIP][28] ([fdo#109642] / [fdo#111068])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-iclb2/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-iclb8/igt@[email protected]
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [PASS][29] -> [SKIP][30] ([fdo#109441]) +2 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-iclb1/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_vblank@pipe-d-query-idle:
- shard-iclb: NOTRUN -> [SKIP][31] ([fdo#109278])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-iclb8/igt@[email protected]
#### Possible fixes ####
* {igt@gem_exec_fair@basic-none@rcs0}:
- shard-kbl: [SKIP][32] ([fdo#109271]) -> [PASS][33]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-kbl6/igt@gem_exec_fair@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-kbl7/igt@gem_exec_fair@[email protected]
* {igt@gem_exec_fair@basic-throttle@rcs0}:
- shard-glk: [FAIL][34] ([i915#2842]) -> [PASS][35]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-glk5/igt@gem_exec_fair@[email protected]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-glk5/igt@gem_exec_fair@[email protected]
* {igt@gem_exec_schedule@u-fairslice@rcs0}:
- shard-skl: [DMESG-WARN][36] ([i915#1610] / [i915#2803]) -> [PASS][37]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl10/igt@gem_exec_schedule@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl8/igt@gem_exec_schedule@[email protected]
* igt@i915_pm_rpm@cursor-dpms:
- shard-glk: [DMESG-WARN][38] ([i915#118] / [i915#95]) -> [PASS][39] +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-glk2/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-glk3/igt@[email protected]
* igt@kms_async_flips@test-time-stamp:
- shard-tglb: [FAIL][40] ([i915#2574]) -> [PASS][41]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-tglb5/igt@[email protected]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-tglb8/igt@[email protected]
* igt@kms_color@pipe-b-ctm-0-5:
- shard-skl: [DMESG-WARN][42] ([i915#1982]) -> [PASS][43]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl7/igt@[email protected]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl3/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-128x128-offscreen:
- shard-skl: [FAIL][44] ([i915#54]) -> [PASS][45] +8 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl2/igt@[email protected]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl3/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: [FAIL][46] ([i915#2346] / [i915#533]) -> [PASS][47]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl5/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl5/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-legacy:
- shard-skl: [FAIL][48] ([i915#2346]) -> [PASS][49]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl8/igt@[email protected]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl4/igt@[email protected]
* igt@kms_cursor_legacy@pipe-c-single-bo:
- shard-kbl: [INCOMPLETE][50] -> [PASS][51]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-kbl1/igt@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-kbl1/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
- shard-tglb: [FAIL][52] ([i915#2598]) -> [PASS][53]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-tglb2/igt@kms_flip@[email protected]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-tglb6/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-skl: [FAIL][54] ([i915#79]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl10/igt@kms_flip@[email protected]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl2/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1:
- shard-kbl: [DMESG-WARN][56] ([i915#180] / [i915#78]) -> [PASS][57] +4 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-kbl2/igt@kms_flip@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-kbl6/igt@kms_flip@[email protected]
* igt@kms_flip@modeset-vs-vblank-race@c-dp1:
- shard-kbl: [DMESG-WARN][58] ([i915#165]) -> [PASS][59]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-kbl2/igt@kms_flip@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-kbl3/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1:
- shard-skl: [FAIL][60] ([i915#2122]) -> [PASS][61]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl5/igt@kms_flip@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl4/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-onoff:
- shard-iclb: [FAIL][62] ([i915#49]) -> [PASS][63]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-iclb6/igt@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-iclb5/igt@[email protected]
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [FAIL][64] ([i915#1188]) -> [PASS][65] +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl7/igt@[email protected]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl8/igt@[email protected]
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [SKIP][66] ([fdo#109441]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-iclb3/igt@kms_psr@psr2_cursor_plane_onoff.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@perf@polling:
- shard-skl: [FAIL][68] ([i915#1542]) -> [PASS][69] +1 similar issue
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl8/igt@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl4/igt@[email protected]
* igt@testdisplay:
- shard-kbl: [DMESG-WARN][70] ([i915#165] / [i915#180] / [i915#78]) -> [PASS][71] +1 similar issue
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-kbl2/[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-kbl3/[email protected]
#### Warnings ####
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: [WARN][72] ([i915#2681] / [i915#2684]) -> [WARN][73] ([i915#1804] / [i915#2684])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-iclb1/igt@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-iclb3/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [WARN][74] ([i915#1804] / [i915#2684]) -> [FAIL][75] ([i915#2680])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-iclb4/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-iclb3/igt@[email protected]
* igt@runner@aborted:
- shard-kbl: [FAIL][76] ([i915#2295] / [i915#2505] / [i915#483]) -> [FAIL][77] ([i915#2295] / [i915#483])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-kbl6/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-kbl2/igt@[email protected]
- shard-iclb: [FAIL][78] ([i915#2295] / [i915#2724] / [i915#483]) -> [FAIL][79] ([i915#2295] / [i915#2724])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-iclb6/igt@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-iclb2/igt@[email protected]
- shard-glk: ([FAIL][80], [FAIL][81]) ([i915#2295] / [i915#2426] / [i915#483] / [k.org#202321]) -> ([FAIL][82], [FAIL][83]) ([i915#2295] / [i915#2426] / [k.org#202321])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-glk7/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-glk8/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-glk6/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-glk2/igt@[email protected]
- shard-skl: ([FAIL][84], [FAIL][85]) ([i915#2295] / [i915#2426]) -> ([FAIL][86], [FAIL][87]) ([i915#2295])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl2/igt@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9554/shard-skl10/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl2/igt@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/shard-skl1/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1226]: https://gitlab.freedesktop.org/drm/intel/issues/1226
[i915#142]: https://gitlab.freedesktop.org/drm/intel/issues/142
[i915#146]: https://gitlab.freedesktop.org/drm/intel/issues/146
[i915#151]: https://gitlab.freedesktop.org/drm/intel/issues/151
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1610]: https://gitlab.freedesktop.org/drm/intel/issues/1610
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2295]: https://gitlab.freedesktop.org/drm/intel/issues/2295
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426
[i915#2505]: https://gitlab.freedesktop.org/drm/intel/issues/2505
[i915#2574]: https://gitlab.freedesktop.org/drm/intel/issues/2574
[i915#2598]: https://gitlab.freedesktop.org/drm/intel/issues/2598
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2680]: https://gitlab.freedesktop.org/drm/intel/issues/2680
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#2724]: https://gitlab.freedesktop.org/drm/intel/issues/2724
[i915#2802]: https://gitlab.freedesktop.org/drm/intel/issues/2802
[i915#2803]: https://gitlab.freedesktop.org/drm/intel/issues/2803
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#483]: https://gitlab.freedesktop.org/drm/intel/issues/483
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#78]: https://gitlab.freedesktop.org/drm/intel/issues/78
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#202321]: https://bugzilla.kernel.org/show_bug.cgi?id=202321
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_9554 -> Patchwork_19275
CI-20190529: 20190529
CI_DRM_9554: 4786f2a4c7e280974d0b46ca9e30a156eb528d59 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5945: f0ad1a564956d6796d9ff09182c48d78fb00eefe @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19275: bd6eed3a74e7aef1dde724eacb490413d8b3ee79 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19275/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Jani Nikula
maintainerAnshuman, please review.
BR,
Jani.
Quoted 60 lines · Sean Paul
From: Sean Paul <[email protected]>
The HDCP 1.4 spec does not require the
QUERY_STREAM_ENCRYPTION_STATUScheck, it was always a nice-to-have. After deploying this across various devices, we've determined that some MST bridge chips do not properly support this call for HDCP 1.4 (namely Synaptics and Realtek).I had considered creating a quirk for this, but I think it's more prudent to just disable the check entirely since I don't have an idea how widespread support is.
Signed-off-by Sean Paul <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 26 +------------------- 1 file changed, 1 insertion(+), 25 deletions(-)drivers/gpu/drm/i915/display/intel_dp_hdcp.c +1
-25@@ -640,30 +640,6 @@ intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,return ret; } -static -bool intel_dp_mst_hdcp_check_link (struct intel_digital_port *dig_port, -struct intel_connector *connector) -{ -struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); -struct intel_dp *intel_dp = &dig_port->dp; -struct drm_dp_query_stream_enc_status_ack_reply reply; -int ret; - -if (!intel_dp_hdcp_check_link (dig_port, connector)) -return false; - - ret =drm_dp_send_query_stream_enc_status (&intel_dp->mst_mgr, - connector->port, &reply); -if (ret) { -drm_dbg_kms (&i915->drm, -"[CONNECTOR:%d:%s] failed QSES ret=%d\n" , - connector->base.base.id, connector->base.name, ret); -return false; - } - -return reply.auth_completed && reply.encryption_enabled; -} -static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .write_an_aksv = intel_dp_hdcp_write_an_aksv, .read_bksv = intel_dp_hdcp_read_bksv,@@ -674,7 +650,7 @@ static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .read_ksv_fifo = intel_dp_hdcp_read_ksv_fifo, .read_v_prime_part = intel_dp_hdcp_read_v_prime_part, .toggle_signalling = intel_dp_mst_hdcp_toggle_signalling, - .check_link = intel_dp_mst_hdcp_check_link, + .check_link = intel_dp_hdcp_check_link, .hdcp_capable = intel_dp_hdcp_capable, .protocol = HDCP_PROTOCOL_DP,
Signature · 5 lines
Jani Nikula, Intel Open Source Graphics Center _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 3 lines · Sean Paul
From: Sean Paul <[email protected]>
The HDCP 1.4 spec does not require the
QUERY_STREAM_ENCRYPTION_STATUS
IMHO DP 1.4 vesa specs I.3.5 mark QSES as desirale for both HDCP 1.4 and HDCP 2.2. "The MST Source device may use a QUERY_STREAM_ENCRYPTION_STATUS message transaction to query the downstream status for a particular stream."
I feel it useful for scenario in which a non hdcp supported monitor is hot plugged to MST branch. Source really doesn't know about the hdcp capable device on MST branch, it just know the capability of immediate downstream device. QSES can fetch the HDCP capability from MST topology. We don't require to enable stream encryption for such streams.
Quoted 7 lines
check, it was always a nice-to-have. After deploying this across various devices, we've determined that some MST bridge chips do not properly support this call for HDCP 1.4 (namely Synaptics and Realtek).
I had considered creating a quirk for this, but I think it's more prudent to just disable the check entirely since I don't have an idea how widespread support is.
May be we can remove it from the link check and can retain as utility ? Thanks,
Anshuman Gupta.
Quoted 57 lines
Signed-off-by Sean Paul <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 26 +------------------- 1 file changed, 1 insertion(+), 25 deletions(-)drivers/gpu/drm/i915/display/intel_dp_hdcp.c +1
-25@@ -640,30 +640,6 @@ intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,return ret; } -static -bool intel_dp_mst_hdcp_check_link (struct intel_digital_port *dig_port, -struct intel_connector *connector) -{ -struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); -struct intel_dp *intel_dp = &dig_port->dp; -struct drm_dp_query_stream_enc_status_ack_reply reply; -int ret; - -if (!intel_dp_hdcp_check_link (dig_port, connector)) -return false; - - ret =drm_dp_send_query_stream_enc_status (&intel_dp->mst_mgr, - connector->port, &reply); -if (ret) { -drm_dbg_kms (&i915->drm, -"[CONNECTOR:%d:%s] failed QSES ret=%d\n" , - connector->base.base.id, connector->base.name, ret); -return false; - } - -return reply.auth_completed && reply.encryption_enabled; -} -static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .write_an_aksv = intel_dp_hdcp_write_an_aksv, .read_bksv = intel_dp_hdcp_read_bksv,@@ -674,7 +650,7 @@ static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .read_ksv_fifo = intel_dp_hdcp_read_ksv_fifo, .read_v_prime_part = intel_dp_hdcp_read_v_prime_part, .toggle_signalling = intel_dp_mst_hdcp_toggle_signalling, - .check_link = intel_dp_mst_hdcp_check_link, + .check_link = intel_dp_hdcp_check_link, .hdcp_capable = intel_dp_hdcp_capable, .protocol = HDCP_PROTOCOL_DP,Signature · 6 lines
Sean Paul, Software Engineer, Google / Chromium OS _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 9 lines · Anshuman Gupta
Quoted 3 lines · Sean Paul
From: Sean Paul <[email protected]>
The HDCP 1.4 spec does not require the
QUERY_STREAM_ENCRYPTION_STATUSIMHO DP 1.4 vesa specs I.3.5 mark QSES as desirale for both HDCP 1.4 and HDCP 2.2. "The MST Source device may use a
QUERY_STREAM_ENCRYPTION_STATUSmessage transaction to query the downstream status for a particular stream."
Quoted 5 lines
I feel it useful for scenario in which a non hdcp supported monitor is hot plugged to MST branch. Source really doesn't know about the hdcp capable device on MST branch, it just know the capability of immediate downstream device. QSES can fetch the HDCP capability from MST topology. We don't require to enable stream encryption for such streams.
I agree it's useful when it works, but unfortunately it's broken on at least 2 MST bridge chips I've encountered :/
Until we can figure out a) how to fix them (ie: firmware updates), or
b) how to enumerate all of the broken chips to create quirks, we probably just want to disable QSES for HDCP 1.4.
Sean
Quoted 59 lines
Quoted 7 lines
check, it was always a nice-to-have. After deploying this across various devices, we've determined that some MST bridge chips do not properly support this call for HDCP 1.4 (namely Synaptics and Realtek).
I had considered creating a quirk for this, but I think it's more prudent to just disable the check entirely since I don't have an idea how widespread support is.
May be we can remove it from the link check and can retain as utility ? Thanks,
Anshuman Gupta.Quoted 49 lines
Signed-off-by Sean Paul <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 26 +------------------- 1 file changed, 1 insertion(+), 25 deletions(-)drivers/gpu/drm/i915/display/intel_dp_hdcp.c +1
-25@@ -640,30 +640,6 @@ intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,return ret; } -static -bool intel_dp_mst_hdcp_check_link (struct intel_digital_port *dig_port, -struct intel_connector *connector) -{ -struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); -struct intel_dp *intel_dp = &dig_port->dp; -struct drm_dp_query_stream_enc_status_ack_reply reply; -int ret; - -if (!intel_dp_hdcp_check_link (dig_port, connector)) -return false; - - ret =drm_dp_send_query_stream_enc_status (&intel_dp->mst_mgr, - connector->port, &reply); -if (ret) { -drm_dbg_kms (&i915->drm, -"[CONNECTOR:%d:%s] failed QSES ret=%d\n" , - connector->base.base.id, connector->base.name, ret); -return false; - } - -return reply.auth_completed && reply.encryption_enabled; -} -static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .write_an_aksv = intel_dp_hdcp_write_an_aksv, .read_bksv = intel_dp_hdcp_read_bksv,@@ -674,7 +650,7 @@ static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .read_ksv_fifo = intel_dp_hdcp_read_ksv_fifo, .read_v_prime_part = intel_dp_hdcp_read_v_prime_part, .toggle_signalling = intel_dp_mst_hdcp_toggle_signalling, - .check_link = intel_dp_mst_hdcp_check_link, + .check_link = intel_dp_hdcp_check_link, .hdcp_capable = intel_dp_hdcp_capable,
Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +0
-1.protocol = HDCP_PROTOCOL_DP, --Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 17 lines · Sean Paul
Quoted 9 lines · Anshuman Gupta
Quoted 3 lines · Sean Paul
From: Sean Paul <[email protected]>
The HDCP 1.4 spec does not require the
QUERY_STREAM_ENCRYPTION_STATUSIMHO DP 1.4 vesa specs I.3.5 mark QSES as desirale for both HDCP 1.4 and HDCP 2.2. "The MST Source device may use a
QUERY_STREAM_ENCRYPTION_STATUSmessage transaction to query the downstream status for a particular stream."Quoted 5 lines
I feel it useful for scenario in which a non hdcp supported monitor is hot plugged to MST branch. Source really doesn't know about the hdcp capable device on MST branch, it just know the capability of immediate downstream device. QSES can fetch the HDCP capability from MST topology. We don't require to enable stream encryption for such streams.
Quoted 6 lines
I agree it's useful when it works, but unfortunately it's broken on at least 2 MST bridge chips I've encountered :/
Until we can figure out a) how to fix them (ie: firmware updates), or
b) how to enumerate all of the broken chips to create quirks, we probably just want to disable QSES for HDCP 1.4.
What happens when the user plugs in a non-hdcp screen into a hub which doesn't do QSES? Just black screen?
That would suck a bit, otoh with broken hw I don't see how we could do better :-/
-Daniel
Quoted 73 lines
Sean
Quoted 59 lines
Quoted 7 lines
check, it was always a nice-to-have. After deploying this across various devices, we've determined that some MST bridge chips do not properly support this call for HDCP 1.4 (namely Synaptics and Realtek).
I had considered creating a quirk for this, but I think it's more prudent to just disable the check entirely since I don't have an idea how widespread support is.
May be we can remove it from the link check and can retain as utility ? Thanks,
Anshuman Gupta.Quoted 49 lines
Signed-off-by Sean Paul <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 26 +------------------- 1 file changed, 1 insertion(+), 25 deletions(-)drivers/gpu/drm/i915/display/intel_dp_hdcp.c +1
-25@@ -640,30 +640,6 @@ intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,return ret; } -static -bool intel_dp_mst_hdcp_check_link (struct intel_digital_port *dig_port, -struct intel_connector *connector) -{ -struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); -struct intel_dp *intel_dp = &dig_port->dp; -struct drm_dp_query_stream_enc_status_ack_reply reply; -int ret; - -if (!intel_dp_hdcp_check_link (dig_port, connector)) -return false; - - ret =drm_dp_send_query_stream_enc_status (&intel_dp->mst_mgr, - connector->port, &reply); -if (ret) { -drm_dbg_kms (&i915->drm, -"[CONNECTOR:%d:%s] failed QSES ret=%d\n" , - connector->base.base.id, connector->base.name, ret); -return false; - } - -return reply.auth_completed && reply.encryption_enabled; -} -static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .write_an_aksv = intel_dp_hdcp_write_an_aksv, .read_bksv = intel_dp_hdcp_read_bksv,@@ -674,7 +650,7 @@ static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .read_ksv_fifo = intel_dp_hdcp_read_ksv_fifo, .read_v_prime_part = intel_dp_hdcp_read_v_prime_part, .toggle_signalling = intel_dp_mst_hdcp_toggle_signalling, - .check_link = intel_dp_mst_hdcp_check_link, + .check_link = intel_dp_hdcp_check_link, .hdcp_capable = intel_dp_hdcp_capable,Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +0
-1.protocol = HDCP_PROTOCOL_DP, --Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 22 lines · Daniel Vetter
Quoted 20 lines · Sean Paul
Quoted 9 lines · Anshuman Gupta
Quoted 3 lines · Sean Paul
From: Sean Paul <[email protected]>
The HDCP 1.4 spec does not require the
QUERY_STREAM_ENCRYPTION_STATUSIMHO DP 1.4 vesa specs I.3.5 mark QSES as desirale for both HDCP 1.4 and HDCP 2.2. "The MST Source device may use a
QUERY_STREAM_ENCRYPTION_STATUSmessage transaction to query the downstream status for a particular stream."Quoted 5 lines
I feel it useful for scenario in which a non hdcp supported monitor is hot plugged to MST branch. Source really doesn't know about the hdcp capable device on MST branch, it just know the capability of immediate downstream device. QSES can fetch the HDCP capability from MST topology. We don't require to enable stream encryption for such streams.
I agree it's useful when it works, but unfortunately it's broken on at least 2 MST bridge chips I've encountered :/
Quoted 7 lines
Quoted 3 lines
Until we can figure out a) how to fix them (ie: firmware updates), or
b) how to enumerate all of the broken chips to create quirks, we probably just want to disable QSES for HDCP 1.4.What happens when the user plugs in a non-hdcp screen into a hub which doesn't do QSES? Just black screen?
Good question, thanks for forcing me to explain myself more thoroughly :)
This patch doesn't change that behavior, QSES is currently only used as a means for verifying the stream continues to be encrypted in steady-state (ie: after auth has already completed and the pixels are flowing).
If one wanted to check HDCP 1.4 capability upfront, QSES wouldn't be the way to do it. Instead you would tunnel a remote DPCD to the sink to read the BCAPS register (ie: the same way we check non-MST connectors).
So QSES is currently only around in HDCP 1.4 as an extra precaution against a bug in the code preventing the MST stream from being encrypted. IMO broken HW overrules suspenders when we already have a belt :)
Sean
Quoted 80 lines
That would suck a bit, otoh with broken hw I don't see how we could do better :-/
-DanielQuoted 65 lines
Sean
Quoted 63 lines
Quoted 7 lines
check, it was always a nice-to-have. After deploying this across various devices, we've determined that some MST bridge chips do not properly support this call for HDCP 1.4 (namely Synaptics and Realtek).
I had considered creating a quirk for this, but I think it's more prudent to just disable the check entirely since I don't have an idea how widespread support is.
May be we can remove it from the link check and can retain as utility ? Thanks,
Anshuman Gupta.Quoted 53 lines
Signed-off-by Sean Paul <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 26 +------------------- 1 file changed, 1 insertion(+), 25 deletions(-)drivers/gpu/drm/i915/display/intel_dp_hdcp.c +1
-26@@ -640,30 +640,6 @@ intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,return ret; } -static -bool intel_dp_mst_hdcp_check_link (struct intel_digital_port *dig_port, -struct intel_connector *connector) -{ -struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); -struct intel_dp *intel_dp = &dig_port->dp; -struct drm_dp_query_stream_enc_status_ack_reply reply; -int ret; - -if (!intel_dp_hdcp_check_link (dig_port, connector)) -return false; - - ret =drm_dp_send_query_stream_enc_status (&intel_dp->mst_mgr, - connector->port, &reply); -if (ret) { -drm_dbg_kms (&i915->drm, -"[CONNECTOR:%d:%s] failed QSES ret=%d\n" , - connector->base.base.id, connector->base.name, ret); -return false; - } - -return reply.auth_completed && reply.encryption_enabled; -} -static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .write_an_aksv = intel_dp_hdcp_write_an_aksv, .read_bksv = intel_dp_hdcp_read_bksv,@@ -674,7 +650,7 @@ static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .read_ksv_fifo = intel_dp_hdcp_read_ksv_fifo, .read_v_prime_part = intel_dp_hdcp_read_v_prime_part, .toggle_signalling = intel_dp_mst_hdcp_toggle_signalling, - .check_link = intel_dp_mst_hdcp_check_link, + .check_link = intel_dp_hdcp_check_link, .hdcp_capable = intel_dp_hdcp_capable, .protocol = HDCP_PROTOCOL_DP, --Sean Paul, Software Engineer, Google / Chromium OS
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 4 lines
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 44 lines · Sean Paul
Quoted 22 lines · Daniel Vetter
Quoted 20 lines · Sean Paul
Quoted 9 lines · Anshuman Gupta
Quoted 3 lines · Sean Paul
From: Sean Paul <[email protected]>
The HDCP 1.4 spec does not require the
QUERY_STREAM_ENCRYPTION_STATUSIMHO DP 1.4 vesa specs I.3.5 mark QSES as desirale for both HDCP 1.4 and HDCP 2.2. "The MST Source device may use a
QUERY_STREAM_ENCRYPTION_STATUSmessage transaction to query the downstream status for a particular stream."Quoted 5 lines
I feel it useful for scenario in which a non hdcp supported monitor is hot plugged to MST branch. Source really doesn't know about the hdcp capable device on MST branch, it just know the capability of immediate downstream device. QSES can fetch the HDCP capability from MST topology. We don't require to enable stream encryption for such streams.
I agree it's useful when it works, but unfortunately it's broken on at least 2 MST bridge chips I've encountered :/
Quoted 7 lines
Quoted 3 lines
Until we can figure out a) how to fix them (ie: firmware updates), or
b) how to enumerate all of the broken chips to create quirks, we probably just want to disable QSES for HDCP 1.4.What happens when the user plugs in a non-hdcp screen into a hub which doesn't do QSES? Just black screen?
Good question, thanks for forcing me to explain myself more thoroughly :)
This patch doesn't change that behavior, QSES is currently only used as a means for verifying the stream continues to be encrypted in steady-state (ie: after auth has already completed and the pixels are flowing).
If one wanted to check HDCP 1.4 capability upfront, QSES wouldn't be the way to do it. Instead you would tunnel a remote DPCD to the sink to read the BCAPS register (ie: the same way we check non-MST connectors).
Quoted 4 lines
So QSES is currently only around in HDCP 1.4 as an extra precaution against a bug in the code preventing the MST stream from being encrypted. IMO broken HW overrules suspenders when we already have a belt :)
I think with the above explanation added to the commit message this makes sense to merge. Fwiw, i.e. not much: Acked-by: Daniel Vetter <[email protected]>
Cheers, Daniel
Quoted 88 lines
Sean
Quoted 84 lines
That would suck a bit, otoh with broken hw I don't see how we could do better :-/
-DanielQuoted 65 lines
Sean
Quoted 63 lines
Quoted 7 lines
check, it was always a nice-to-have. After deploying this across various devices, we've determined that some MST bridge chips do not properly support this call for HDCP 1.4 (namely Synaptics and Realtek).
I had considered creating a quirk for this, but I think it's more prudent to just disable the check entirely since I don't have an idea how widespread support is.
May be we can remove it from the link check and can retain as utility ? Thanks,
Anshuman Gupta.Quoted 53 lines
Signed-off-by Sean Paul <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 26 +------------------- 1 file changed, 1 insertion(+), 25 deletions(-)drivers/gpu/drm/i915/display/intel_dp_hdcp.c +1
-26@@ -640,30 +640,6 @@ intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,return ret; } -static -bool intel_dp_mst_hdcp_check_link (struct intel_digital_port *dig_port, -struct intel_connector *connector) -{ -struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); -struct intel_dp *intel_dp = &dig_port->dp; -struct drm_dp_query_stream_enc_status_ack_reply reply; -int ret; - -if (!intel_dp_hdcp_check_link (dig_port, connector)) -return false; - - ret =drm_dp_send_query_stream_enc_status (&intel_dp->mst_mgr, - connector->port, &reply); -if (ret) { -drm_dbg_kms (&i915->drm, -"[CONNECTOR:%d:%s] failed QSES ret=%d\n" , - connector->base.base.id, connector->base.name, ret); -return false; - } - -return reply.auth_completed && reply.encryption_enabled; -} -static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .write_an_aksv = intel_dp_hdcp_write_an_aksv, .read_bksv = intel_dp_hdcp_read_bksv,@@ -674,7 +650,7 @@ static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .read_ksv_fifo = intel_dp_hdcp_read_ksv_fifo, .read_v_prime_part = intel_dp_hdcp_read_v_prime_part, .toggle_signalling = intel_dp_mst_hdcp_toggle_signalling, - .check_link = intel_dp_mst_hdcp_check_link, + .check_link = intel_dp_hdcp_check_link, .hdcp_capable = intel_dp_hdcp_capable, .protocol = HDCP_PROTOCOL_DP, --Sean Paul, Software Engineer, Google / Chromium OS
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Gupta, Anshuman
Reviewed-byQuoted 52 lines
-----Original Message-----
From: Sean Paul <[email protected]>
Sent: Thursday, January 14, 2021 12:04 AM
To: Daniel Vetter <[email protected]>
Cc: Gupta, Anshuman <[email protected]>; David Airlie <[email protected]>; [email protected]; Sean Paul <[email protected]>; [email protected]
Subject: Re: [Intel-gfx] [PATCH] drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MSTQuoted 4 lines · Daniel Vetter
Quoted 2 lines · Sean Paul
On Wed, Jan 13, 2021 at 5:34 AM Anshuman Gupta
Quoted 7 lines · <[email protected]> wrote:
Quoted 7 lines
Quoted 7 lines · Sean Paul
Quoted 4 lines
From: Sean Paul <[email protected]>
The HDCP 1.4 spec does not require the
QUERY_STREAM_ENCRYPTION_STATUSIMHO DP 1.4 vesa specs I.3.5 mark QSES as desirale for both HDCP 1.4
and HDCP 2.2.
Quoted 1 line
Quoted 1 line
Quoted 1 line
"The MST Source device may use a
QUERY_STREAM_ENCRYPTION_STATUSQuoted 1 line
Quoted 1 line
Quoted 1 line
message transaction to query the downstream status for a particular
stream."
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
I feel it useful for scenario in which a non hdcp supported monitor is hot plugged to MST branch. Source really doesn't know about the hdcp capable device on MST branch, it just know the capability of immediate downstream device. QSES can fetch the HDCP
capability from MST topology.
Quoted 5 lines
Quoted 5 lines
Quoted 1 line
We don't require to enable stream encryption for such streams.
I agree it's useful when it works, but unfortunately it's broken on at least 2 MST bridge chips I've encountered :/
Quoted 8 lines
Quoted 4 lines
Until we can figure out a) how to fix them (ie: firmware updates), or
b) how to enumerate all of the broken chips to create quirks, we probably just want to disable QSES for HDCP 1.4.What happens when the user plugs in a non-hdcp screen into a hub which doesn't do QSES? Just black screen?
Good question, thanks for forcing me to explain myself more thoroughly :)
Quoted 7 lines
This patch doesn't change that behavior, QSES is currently only used as a means for verifying the stream continues to be encrypted in steady-state (ie: after auth has already completed and the pixels are flowing).
If one wanted to check HDCP 1.4 capability upfront, QSES wouldn't be the way to do it. Instead you would tunnel a remote DPCD to the sink to read the BCAPS register (ie: the same way we check non-MST connectors).
AFAIK in case of MST topology source can only get BCAPS/RXCAPS of the immediate downstream sink
(in this particular case it will be BCAPS/RXCAPS of MST hub).
Ex. I have a HDCP 2.2 (DP-6 immediate downstream) and HDCP 1.4 (DP-7) connector setup in daisy chain setup, DP-7 just reports the RXCAPS of DP-6. cat /sys/kernel/debug/dri/0/DP-7/i915_hdcp_sink_capability
DP-7:369 HDCP version: HDCP1.4 HDCP2.2
root@linux-Tiger-Lake-Client-Platform:/home/linux# dmesg [180919.808209] [drm:drm_dp_dpcd_read] AUX B/DDI B/PHY B: 0x68028 AUX -> (ret= 1) 03 [180919.809089] [drm:drm_dp_dpcd_read] AUX B/DDI B/PHY B: 0x6921d AUX -> (ret= 3) 02 00 03 I was planning to use QSES to query HDCP in MST topology but now not sure what to do with not supported MST hubs.
However agree with you for this patch, it seems to disable the QSES link check the right thing to do. It would require to rebase.
Quoted 58 lines
So QSES is currently only around in HDCP 1.4 as an extra precaution against a bug in the code preventing the MST stream from being encrypted. IMO broken HW overrules suspenders when we already have a belt :)
Sean
Quoted 8 lines
That would suck a bit, otoh with broken hw I don't see how we could do better :-/ -Daniel
Quoted 5 lines
Sean
Quoted 3 lines
Quoted 3 lines
check, it was always a nice-to-have. After deploying this across various devices, we've determined that some MST bridge chips do not properly support this call for HDCP 1.4 (namely Synaptics and
Realtek).
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
I had considered creating a quirk for this, but I think it's more prudent to just disable the check entirely since I don't have an idea how widespread support is.
May be we can remove it from the link check and can retain as utility
?
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Thanks,
Anshuman Gupta.Quoted 7 lines
Signed-off-by Sean Paul <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 26 +------------------- 1 file changed, 1 insertion(+), 25 deletions(-)Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +0
-0@@ -640,30 +640,6 @@intel_dp_mst_hdcp_toggle_signalling(struct
intel_digital_port*dig_port,Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,
Quoted 5 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +0
-2return ret; } -static -bool intel_dp_mst_hdcp_check_link(struct intel_digital_port
*dig_port,Quoted 13 lines
Quoted 3 lines
Quoted 3 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,
Quoted 3 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +0
-3- struct intel_connector *connector) -{ - struct drm_i915_private *i915 = to_i915(dig_port-base.base.dev);
Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +0
-8-struct intel_dp *intel_dp = &dig_port->dp; -struct drm_dp_query_stream_enc_status_ack_reply reply; -int ret; - -if (!intel_dp_hdcp_check_link (dig_port, connector)) -return false; - - ret = drm_dp_send_query_stream_enc_status(&intel_dp-
mst_mgr,
Quoted 42 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c intel_dp_mst_hdcp_toggle_signalling(struct intel_digital_port *dig_port,
Quoted 5 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +0
-5- connector->port, &reply); -if (ret) { - drm_dbg_kms(&i915->drm, - "[CONNECTOR:%d:%s] failed QSES ret=%d\n", - connector->base.base.id, connector->base.name,ret);
Quoted 36 lines
Quoted 21 lines
Quoted 21 lines
Quoted 21 lines
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +0
-6-return false; - } - -return reply.auth_completed && reply.encryption_enabled; -} -static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .write_an_aksv = intel_dp_hdcp_write_an_aksv, .read_bksv = intel_dp_hdcp_read_bksv, @@ -674,7 +650,7 @@static const struct
intel_hdcp_shimintel_dp_mst_hdcp_shim= {
.read_ksv_fifo =intel_dp_hdcp_read_ksv_fifo, .read_v_prime_part =intel_dp_hdcp_read_v_prime_part, .toggle_signalling =intel_dp_mst_hdcp_toggle_signalling,drivers/gpu/drm/i915/display/intel_dp_hdcp.c +1
-2- .check_link = intel_dp_mst_hdcp_check_link, + .check_link = intel_dp_hdcp_check_link, .hdcp_capable = intel_dp_hdcp_capable, .protocol = HDCP_PROTOCOL_DP, --Sean Paul, Software Engineer, Google / Chromium OS
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v2 1/1 drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
In reply to Sean PaulFrom: Sean Paul <[email protected]>
The HDCP 1.4 spec does not require the QUERY_STREAM_ENCRYPTION_STATUS check, it was always a nice-to-have. After deploying this across various devices, we've determined that some MST bridge chips do not properly support this call for HDCP 1.4 (namely Synaptics and Realtek).
I had considered creating a quirk for this, but I think it's more prudent to just disable the check entirely since I don't have an idea how widespread support is.
Changes in v2:
-Rebased on -tip
--- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-)
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +1 -11
@@ -722,16 +722,6 @@ static bool intel_dp_mst_get_qses_status(struct intel_digital_port *dig_port,return reply.auth_completed && reply.encryption_enabled; } -static -bool intel_dp_mst_hdcp_check_link (struct intel_digital_port *dig_port, -struct intel_connector *connector) -{ -if (!intel_dp_hdcp_check_link (dig_port, connector)) -return false; - -return intel_dp_mst_get_qses_status (dig_port, connector); -} -static int intel_dp_mst_hdcp2_stream_encryption (struct intel_connector *connector,bool enable)
@@ -805,7 +795,7 @@ static const struct intel_hdcp_shim intel_dp_mst_hdcp_shim = { .read_v_prime_part = intel_dp_hdcp_read_v_prime_part, .toggle_signalling = intel_dp_hdcp_toggle_signalling, .stream_encryption = intel_dp_mst_hdcp_stream_encryption, - .check_link = intel_dp_mst_hdcp_check_link, + .check_link = intel_dp_hdcp_check_link, .hdcp_capable = intel_dp_hdcp_capable, .write_2_2_msg = intel_dp_hdcp2_write_msg, .read_2_2_msg = intel_dp_hdcp2_read_msg,
Signature · 6 lines
Sean Paul, Software Engineer, Google / Chromium OS _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
In reply to Sean Paul== Series Details ==
== Series Details ==
Series: drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
URL : https://patchwork.freedesktop.org/series/85555/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9666 -> Patchwork_19447
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_19447 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_19447, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_19447:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@gt_lrc:
- fi-bsw-n3050: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
Known issues
------------
Here are the changes found in Patchwork_19447 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_mmap_gtt@basic:
- fi-tgl-y: [PASS][3] -> [DMESG-WARN][4] ([i915#402]) +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected]
* igt@i915_selftest@live@hugepages:
- fi-bsw-n3050: [PASS][5] -> [SKIP][6] ([fdo#109271]) +20 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@ring_submission:
- fi-bsw-n3050: NOTRUN -> [SKIP][7] ([fdo#109271]) +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@ring_submission.html
* igt@kms_chamelium@dp-crc-fast:
- fi-kbl-7500u: [PASS][8] -> [FAIL][9] ([i915#1161] / [i915#262])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-kbl-7500u/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl-7500u/igt@[email protected]
#### Possible fixes ####
* igt@gem_tiled_blits@basic:
- fi-tgl-y: [DMESG-WARN][10] ([i915#402]) -> [PASS][11] +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected]
#### Warnings ####
* igt@i915_selftest@live@execlists:
- fi-bsw-n3050: [INCOMPLETE][12] ([i915#2940]) -> [SKIP][13] ([fdo#109271])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1161]: https://gitlab.freedesktop.org/drm/intel/issues/1161
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#2940]: https://gitlab.freedesktop.org/drm/intel/issues/2940
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
Participating hosts (41 -> 37)
------------------------------
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u
Build changes
-------------
* Linux: CI_DRM_9666 -> Patchwork_19447
CI-20190529: 20190529
CI_DRM_9666: 9ccbc653bf2948d1f7e9ff300dd7679b888ffa25 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5962: 22e3daaed82ab7890018a2f2aabf5082cd536023 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19447: 69d7db003fa406df7851ab08239dd409a78f4421 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
69d7db003fa4 drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Hi Lakshmi ,
We need to merge the patch https://patchwork.freedesktop.org/series/85555/
Below are the gem failures causing the BAT to fail , those were not seen on Rev1 of this patch. Could you please rereport-the results to trigger CI-IGT run.
Thanks,
Anshuman Gupta.
From: Intel-gfx <[email protected]> On Behalf Of Patchwork
Sent: Friday, January 22, 2021 8:13 AM
To: Sean Paul <[email protected]>
Cc: [email protected]
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Patch Details
Series:
drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
URL:
https://patchwork.freedesktop.org/series/85555/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
CI Bug Log - changes from CI_DRM_9666 -> Patchwork_19447
Summary
FAILURE
Serious unknown changes coming with Patchwork_19447 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_19447, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
Possible new issues
Here are the unknown changes that may have been introduced in Patchwork_19447:
IGT changes
Possible regressions
• igt@i915_selftest@live@gt_lrc:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
Known issues
Here are the changes found in Patchwork_19447 that come from known issues:
IGT changes
Issues hit
• igt@gem_mmap_gtt@basic:
o fi-tgl-y: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/402) +2 similar issues
• igt@i915_selftest@live@hugepages:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +20 similar issues
• igt@i915_selftest@live@ring_submission:
o fi-bsw-n3050: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@ring_submission.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +2 similar issues
• igt@kms_chamelium@dp-crc-fast:
o fi-kbl-7500u: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-kbl-7500u/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl-7500u/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/1161 / https://gitlab.freedesktop.org/drm/intel/issues/262)
Possible fixes
• igt@gem_tiled_blits@basic:
o fi-tgl-y: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/402) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected] +1 similar issue Warnings
• igt@i915_selftest@live@execlists:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2940) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271)
Participating hosts (41 -> 37)
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u
Build changes
• Linux: CI_DRM_9666 -> Patchwork_19447
CI-20190529: 20190529CI_DRM_9666: 9ccbc653bf2948d1f7e9ff300dd7679b888ffa25 @ git://anongit.freedesktop.org/gfx-ci/linuxIGT_5962: 22e3daaed82ab7890018a2f2aabf5082cd536023 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-toolsPatchwork_19447: 69d7db003fa406df7851ab08239dd409a78f4421 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==69d7db003fa4 drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Hi,
CI bug log crashes while creating an issue but I have created bug in gitlab. I will try to create issue in CI bug log again later today.
https://gitlab.freedesktop.org/drm/intel/-/issues/2998
Thanks,
Lakshmi.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Monday, January 25, 2021 7:26 AM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Hi Lakshmi ,
We need to merge the patch https://patchwork.freedesktop.org/series/85555/
Below are the gem failures causing the BAT to fail , those were not seen on Rev1 of this patch. Could you please rereport-the results to trigger CI-IGT run.
Thanks,
Anshuman Gupta.
From: Intel-gfx <[email protected]> On Behalf Of Patchwork
Sent: Friday, January 22, 2021 8:13 AM
To: Sean Paul <[email protected]>
Cc: [email protected]
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Patch Details
Series:
drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
URL:
https://patchwork.freedesktop.org/series/85555/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
CI Bug Log - changes from CI_DRM_9666 -> Patchwork_19447 Summary FAILURE Serious unknown changes coming with Patchwork_19447 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_19447, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
Possible new issues
Here are the unknown changes that may have been introduced in Patchwork_19447:
IGT changes
Possible regressions
• igt@i915_selftest@live@gt_lrc:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
Known issues
Here are the changes found in Patchwork_19447 that come from known issues:
IGT changes
Issues hit
• igt@gem_mmap_gtt@basic:
o fi-tgl-y: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/402) +2 similar issues • igt@i915_selftest@live@hugepages:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +20 similar issues • igt@i915_selftest@live@ring_submission:
o fi-bsw-n3050: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@ring_submission.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +2 similar issues • igt@kms_chamelium@dp-crc-fast:
o fi-kbl-7500u: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-kbl-7500u/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl-7500u/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/1161 / https://gitlab.freedesktop.org/drm/intel/issues/262)
Possible fixes
• igt@gem_tiled_blits@basic:
o fi-tgl-y: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/402) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected] +1 similar issue Warnings • igt@i915_selftest@live@execlists:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2940) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271)
Participating hosts (41 -> 37)
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u Build changes • Linux: CI_DRM_9666 -> Patchwork_19447
CI-20190529: 20190529CI_DRM_9666: 9ccbc653bf2948d1f7e9ff300dd7679b888ffa25 @ git://anongit.freedesktop.org/gfx-ci/linuxIGT_5962: 22e3daaed82ab7890018a2f2aabf5082cd536023 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-toolsPatchwork_19447: 69d7db003fa406df7851ab08239dd409a78f4421 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==69d7db003fa4 drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
In reply to Gupta, AnshumanRe-reported.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Monday, January 25, 2021 7:26 AM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Hi Lakshmi ,
We need to merge the patch https://patchwork.freedesktop.org/series/85555/
Below are the gem failures causing the BAT to fail , those were not seen on Rev1 of this patch. Could you please rereport-the results to trigger CI-IGT run.
Thanks,
Anshuman Gupta.
From: Intel-gfx <[email protected]> On Behalf Of Patchwork
Sent: Friday, January 22, 2021 8:13 AM
To: Sean Paul <[email protected]>
Cc: [email protected]
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Patch Details
Series:
drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
URL:
https://patchwork.freedesktop.org/series/85555/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
CI Bug Log - changes from CI_DRM_9666 -> Patchwork_19447 Summary FAILURE Serious unknown changes coming with Patchwork_19447 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_19447, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
Possible new issues
Here are the unknown changes that may have been introduced in Patchwork_19447:
IGT changes
Possible regressions
• igt@i915_selftest@live@gt_lrc:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
Known issues
Here are the changes found in Patchwork_19447 that come from known issues:
IGT changes
Issues hit
• igt@gem_mmap_gtt@basic:
o fi-tgl-y: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/402) +2 similar issues • igt@i915_selftest@live@hugepages:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +20 similar issues • igt@i915_selftest@live@ring_submission:
o fi-bsw-n3050: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@ring_submission.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +2 similar issues • igt@kms_chamelium@dp-crc-fast:
o fi-kbl-7500u: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-kbl-7500u/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl-7500u/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/1161 / https://gitlab.freedesktop.org/drm/intel/issues/262)
Possible fixes
• igt@gem_tiled_blits@basic:
o fi-tgl-y: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/402) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected] +1 similar issue Warnings • igt@i915_selftest@live@execlists:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2940) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271)
Participating hosts (41 -> 37)
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u Build changes • Linux: CI_DRM_9666 -> Patchwork_19447
CI-20190529: 20190529CI_DRM_9666: 9ccbc653bf2948d1f7e9ff300dd7679b888ffa25 @ git://anongit.freedesktop.org/gfx-ci/linuxIGT_5962: 22e3daaed82ab7890018a2f2aabf5082cd536023 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-toolsPatchwork_19447: 69d7db003fa406df7851ab08239dd409a78f4421 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==69d7db003fa4 drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Thanks Lakshmi for re-reporting it.
May I know that re-reporting will also trigger a CI-IGT run.
I am not able to see this series in CI Queue https://intel-gfx-ci.01.org/queue/index.html
Currently this patch Rev2 is not showing any CI-IGT results.
Br,
Anshuman
Quoted 111 lines
-----Original Message-----
From: Vudum, Lakshminarayana <[email protected]>
Sent: Monday, January 25, 2021 10:40 PM
To: Gupta, Anshuman <[email protected]>; intel- [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)Re-reported.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Monday, January 25, 2021 7:26 AM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)Hi Lakshmi ,
We need to merge the patch
https://patchwork.freedesktop.org/series/85555/
Below are the gem failures causing the BAT to fail , those were not seen on Rev1 of this patch.
Could you please rereport-the results to trigger CI-IGT run. Thanks,
Anshuman Gupta.From: Intel-gfx <[email protected]> On Behalf Of Patchwork
Sent: Friday, January 22, 2021 8:13 AM
To: Sean Paul <[email protected]>
Cc: [email protected]
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)Patch Details
Series:
drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2) URL:
https://patchwork.freedesktop.org/series/85555/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
CI Bug Log - changes fromCI_DRM_9666->Patchwork_19447Summary FAILURE Serious unknown changes coming withPatchwork_19447absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced inPatchwork_19447, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. External URL: https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/index.html
Possible new issues
Here are the unknown changes that may have been introduced inPatchwork_19447:
IGT changes
Possible regressions
• igt@i915_selftest@live@gt_lrc:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@live@gt_lrc.html -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@live@gt_lrc.html
Known issues
Here are the changes found inPatchwork_19447that come from known issues:
IGT changes
Issues hit
• igt@gem_mmap_gtt@basic:
o fi-tgl-y: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
y/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/fi-tgl-y/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/402) +2 similar issues • igt@i915_selftest@live@hugepages:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@[email protected] -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@[email protected]
(https://bugs.freedesktop.org/show_bug.cgi?id=109271) +20 similar issues
• igt@i915_selftest@live@ring_submission:
o fi-bsw-n3050: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@live@ring_submission.html
(https://bugs.freedesktop.org/show_bug.cgi?id=109271) +2 similar issues
• igt@kms_chamelium@dp-crc-fast:
o fi-kbl-7500u: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
kbl-7500u/igt@[email protected] -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl- 7500u/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/1161 /
https://gitlab.freedesktop.org/drm/intel/issues/262)
Possible fixes
• igt@gem_tiled_blits@basic:
o fi-tgl-y: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
y/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/402) -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl- y/igt@[email protected] +1 similar issue Warnings • igt@i915_selftest@live@execlists:
o fi-bsw-n3050: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/2940) -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@[email protected]
(https://bugs.freedesktop.org/show_bug.cgi?id=109271)
Participating hosts (41 -> 37)
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u Build changes • Linux:CI_DRM_9666->Patchwork_19447
CI-20190529: 20190529CI_DRM_9666:9ccbc653bf2948d1f7e9ff300dd7679b888ffa25@
Quoted 8 lines
git://anongit.freedesktop.org/gfx-ci/linuxIGT_5962:22e3daaed82ab7890018a2f2aabf5082cd536023@git://anongit.freedesktop.org/xorg/app/intel-gpu-toolsPatchwork_19447:69d7db003fa406df7851ab08239dd409a78f4421@git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==69d7db003fa4drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Re-reporting will just re-report the results once more time. Re-reporting will re-check if there is an existing bug for the regression failures or not. If a bug is found, series shows as success (as the failure is not a regression). Regression failures will find a bug when a re-report as I either file a new bug or I will associate the regression failure to an existing bug before I re-report.
But re-reporting will not trigger re-run to see version 2 results. Let me know if you have any further questions.
Thanks,
Lakshmi.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Tuesday, January 26, 2021 9:20 PM
To: Vudum, Lakshminarayana <[email protected]>; [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Thanks Lakshmi for re-reporting it.
May I know that re-reporting will also trigger a CI-IGT run.
I am not able to see this series in CI Queue https://intel-gfx-ci.01.org/queue/index.html
Currently this patch Rev2 is not showing any CI-IGT results.
Br,
Anshuman
Quoted 121 lines
-----Original Message-----
From: Vudum, Lakshminarayana <[email protected]>
Sent: Monday, January 25, 2021 10:40 PM
To: Gupta, Anshuman <[email protected]>; intel- [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
Disable the QSES check for HDCP 1.4 over MST (rev2)Re-reported.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Monday, January 25, 2021 7:26 AM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
Disable the QSES check for HDCP 1.4 over MST (rev2)Hi Lakshmi ,
We need to merge the patch
https://patchwork.freedesktop.org/series/85555/
Below are the gem failures causing the BAT to fail , those were not seen on
Rev1 of this patch.
Could you please rereport-the results to trigger CI-IGT run. Thanks,
Anshuman Gupta.From: Intel-gfx <[email protected]> On Behalf Of Patchwork
Sent: Friday, January 22, 2021 8:13 AM
To: Sean Paul <[email protected]>
Cc: [email protected]
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)Patch Details
Series:
drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2) URL:
https://patchwork.freedesktop.org/series/85555/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
CI Bug Log - changes fromCI_DRM_9666->Patchwork_19447Summary FAILURE Serious unknown changes coming withPatchwork_19447absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced inPatchwork_19447, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. External URL: https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/index.html
Possible new issues
Here are the unknown changes that may have been introduced inPatchwork_19447:
IGT changes
Possible regressions
• igt@i915_selftest@live@gt_lrc:
o fi-bsw-n3050:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@live@gt_lrc.html -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@live@gt_lrc.html
Known issues
Here are the changes found inPatchwork_19447that come from known issues:
IGT changes
Issues hit
• igt@gem_mmap_gtt@basic:
o fi-tgl-y:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
y/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/fi-tgl-y/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/402) +2 similar issues •
igt@i915_selftest@live@hugepages:
o fi-bsw-n3050:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@[email protected] -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@[email protected]
(https://bugs.freedesktop.org/show_bug.cgi?id=109271) +20 similar issues • igt@i915_selftest@live@ring_submission:
o fi-bsw-n3050: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@live@ring_submission.html
(https://bugs.freedesktop.org/show_bug.cgi?id=109271) +2 similar issues • igt@kms_chamelium@dp-crc-fast:
o fi-kbl-7500u:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
kbl-7500u/igt@[email protected] -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl- 7500u/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/1161 /
https://gitlab.freedesktop.org/drm/intel/issues/262)
Possible fixes
• igt@gem_tiled_blits@basic:
o fi-tgl-y:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
y/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/402) ->
https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl- y/igt@[email protected] +1 similar issue Warnings • igt@i915_selftest@live@execlists:
o fi-bsw-n3050:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/2940) ->
https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@[email protected]
(https://bugs.freedesktop.org/show_bug.cgi?id=109271)
Participating hosts (41 -> 37)
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u Build changes • Linux:CI_DRM_9666->Patchwork_19447
CI-20190529: 20190529CI_DRM_9666:9ccbc653bf2948d1f7e9ff300dd7679b888ffa25@
Quoted 8 lines
git://anongit.freedesktop.org/gfx-ci/linuxIGT_5962:22e3daaed82ab7890018a2f2aabf5082cd536023@git://anongit.freedesktop.org/xorg/app/intel-gpu-toolsPatchwork_19447:69d7db003fa406df7851ab08239dd409a78f4421@git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==69d7db003fa4drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Quoted 11 lines
-----Original Message-----
From: Vudum, Lakshminarayana <[email protected]>
Sent: Wednesday, January 27, 2021 11:00 AM
To: Gupta, Anshuman <[email protected]>; intel- [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Quoted 8 lines
Re-reporting will just re-report the results once more time. Re-reporting will re-check if there is an existing bug for the regression failures or not. If a bug is found, series shows as success (as the failure is not a regression). Regression failures will find a bug when a re-report as I either file a new bug or I will associate the regression failure to an existing bug before I re-report.
But re-reporting will not trigger re-run to see version 2 results. Let me know if you have any further questions.
We don't have CI-IGT (full) results for the series https://patchwork.freedesktop.org/series/85555/#rev2 yet. In order to merge this patch we would require CI pre merge results.
Thanks,
Anshuman Gupta.
Quoted 98 lines
Thanks,
Lakshmi.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Tuesday, January 26, 2021 9:20 PM
To: Vudum, Lakshminarayana <[email protected]>; intel- [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)Thanks Lakshmi for re-reporting it.
May I know that re-reporting will also trigger a CI-IGT run. I am not able to see this series in CI Queue https://intel-gfx-
ci.01.org/queue/index.html
Currently this patch Rev2 is not showing any CI-IGT results.Br,
AnshumanQuoted 38 lines
-----Original Message-----
From: Vudum, Lakshminarayana <[email protected]>
Sent: Monday, January 25, 2021 10:40 PM
To: Gupta, Anshuman <[email protected]>; intel- [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
Disable the QSES check for HDCP 1.4 over MST (rev2)Re-reported.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Monday, January 25, 2021 7:26 AM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
Disable the QSES check for HDCP 1.4 over MST (rev2)Hi Lakshmi ,
We need to merge the patch
https://patchwork.freedesktop.org/series/85555/
Below are the gem failures causing the BAT to fail , those were not seen on
Rev1 of this patch.
Could you please rereport-the results to trigger CI-IGT run. Thanks,
Anshuman Gupta.From: Intel-gfx <[email protected]> On Behalf Of Patchwork
Sent: Friday, January 22, 2021 8:13 AM
To: Sean Paul <[email protected]>
Cc: [email protected]
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)Quoted 11 lines
Patch Details
Series:
drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2) URL:
https://patchwork.freedesktop.org/series/85555/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
CI Bug Log - changes fromCI_DRM_9666->Patchwork_19447Summary FAILURE Serious unknown changes coming withPatchwork_19447absolutely
Quoted 4 lines
need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced inPatchwork_19447, please notify your bug team to allow them to document this new failure mode, which will reduce false positivesin CI.
Quoted 14 lines
External URL: https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/index.html
Possible new issues
Here are the unknown changes that may have been introduced inPatchwork_19447:
IGT changes
Possible regressions
• igt@i915_selftest@live@gt_lrc:
o fi-bsw-n3050:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@live@gt_lrc.html -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@live@gt_lrc.html
Known issuesQuoted 8 lines
Here are the changes found in
Patchwork_19447that come from known issues:
IGT changes
Issues hit
• igt@gem_mmap_gtt@basic:
o fi-tgl-y:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
y/igt@[email protected] -> https://intel-gfx-
Quoted 55 lines
ci.01.org/tree/drm-
Quoted 54 lines
tip/Patchwork_19447/fi-tgl-y/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/402) +2 similar issues •
igt@i915_selftest@live@hugepages:
o fi-bsw-n3050:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@[email protected] -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@[email protected]
(https://bugs.freedesktop.org/show_bug.cgi?id=109271) +20 similar issues • igt@i915_selftest@live@ring_submission:
o fi-bsw-n3050: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@live@ring_submission.html
(https://bugs.freedesktop.org/show_bug.cgi?id=109271) +2 similar issues • igt@kms_chamelium@dp-crc-fast:
o fi-kbl-7500u:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
kbl-7500u/igt@[email protected] -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl- 7500u/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/1161 /
https://gitlab.freedesktop.org/drm/intel/issues/262)
Possible fixes
• igt@gem_tiled_blits@basic:
o fi-tgl-y:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
y/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/402) ->
https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl- y/igt@[email protected] +1 similar issue Warnings • igt@i915_selftest@live@execlists:
o fi-bsw-n3050:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/2940) ->
https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@[email protected]
(https://bugs.freedesktop.org/show_bug.cgi?id=109271)
Participating hosts (41 -> 37)
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u Build changes • Linux:CI_DRM_9666->Patchwork_19447
CI-20190529: 20190529CI_DRM_9666:9ccbc653bf2948d1f7e9ff300dd7679b888ffa25@git://anongit.freedesktop.org/gfx-ci/linuxIGT_5962:22e3daaed82ab7890018a2f2aabf5082cd536023@git://anongit.freedesktop.org/xorg/app/intel-gpu-toolsPatchwork_19447:69d7db003fa406df7851ab08239dd409a78f4421@git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==69d7db003fa4drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
I am not totally sure why shard run is not triggered here https://patchwork.freedesktop.org/series/85555/#rev2
@Latvala, Petri any help here?
Thanks,
Lakshmi.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Tuesday, January 26, 2021 11:38 PM
To: Vudum, Lakshminarayana <[email protected]>; [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Quoted 9 lines
-----Original Message-----
From: Vudum, Lakshminarayana <[email protected]>
Sent: Wednesday, January 27, 2021 11:00 AM
To: Gupta, Anshuman <[email protected]>; intel- [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
Disable the QSES check for HDCP 1.4 over MST (rev2)
Quoted 8 lines
Re-reporting will just re-report the results once more time.
Re-reporting will re-check if there is an existing bug for the
regression failures or not. If a bug is found, series shows as success (as the failure is not a regression). Regression failures will find a bug when a re-report as I either file
a new bug or I will associate the regression failure to an existing bug before I re-report.But re-reporting will not trigger re-run to see version 2 results. Let me know if you have any further questions.
We don't have CI-IGT (full) results for the series https://patchwork.freedesktop.org/series/85555/#rev2 yet. In order to merge this patch we would require CI pre merge results.
Thanks,
Anshuman Gupta.
Quoted 99 lines
Thanks,
Lakshmi.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Tuesday, January 26, 2021 9:20 PM
To: Vudum, Lakshminarayana <[email protected]>; intel- [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
Disable the QSES check for HDCP 1.4 over MST (rev2)Thanks Lakshmi for re-reporting it.
May I know that re-reporting will also trigger a CI-IGT run. I am not able to see this series in CI Queue https://intel-gfx-
ci.01.org/queue/index.html Currently this patch Rev2 is not showing any CI-IGT results.Br,
AnshumanQuoted 38 lines
-----Original Message-----
From: Vudum, Lakshminarayana <[email protected]>
Sent: Monday, January 25, 2021 10:40 PM
To: Gupta, Anshuman <[email protected]>; intel- [email protected]
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
Disable the QSES check for HDCP 1.4 over MST (rev2)Re-reported.
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Monday, January 25, 2021 7:26 AM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>
Cc: Sean Paul <[email protected]>
Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp:
Disable the QSES check for HDCP 1.4 over MST (rev2)Hi Lakshmi ,
We need to merge the patch
https://patchwork.freedesktop.org/series/85555/
Below are the gem failures causing the BAT to fail , those were not seen on
Rev1 of this patch.
Could you please rereport-the results to trigger CI-IGT run. Thanks,
Anshuman Gupta.From: Intel-gfx <[email protected]> On Behalf Of Patchwork
Sent: Friday, January 22, 2021 8:13 AM
To: Sean Paul <[email protected]>
Cc: [email protected]
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)Quoted 11 lines
Patch Details
Series:
drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2) URL:
https://patchwork.freedesktop.org/series/85555/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
CI Bug Log - changes fromCI_DRM_9666->Patchwork_19447Summary FAILURE Serious unknown changes coming withPatchwork_19447absolutely
Quoted 5 lines
need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced inPatchwork_19447, please notify your bug team to allow them to document this new failure mode, which will reduce false positivesin CI.
Quoted 14 lines
External URL: https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/index.html
Possible new issues
Here are the unknown changes that may have been introduced inPatchwork_19447:
IGT changes
Possible regressions
• igt@i915_selftest@live@gt_lrc:
o fi-bsw-n3050:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@live@gt_lrc.html -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@live@gt_lrc.html
Known issuesQuoted 8 lines
Here are the changes found in
Patchwork_19447that come from known issues:
IGT changes
Issues hit
• igt@gem_mmap_gtt@basic:
o fi-tgl-y:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
y/igt@[email protected] -> https://intel-gfx-
Quoted 56 lines
ci.01.org/tree/drm-
Quoted 55 lines
tip/Patchwork_19447/fi-tgl-y/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/402) +2 similar issues •
igt@i915_selftest@live@hugepages:
o fi-bsw-n3050:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@[email protected] ->
https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@[email protected]
(https://bugs.freedesktop.org/show_bug.cgi?id=109271) +20 similar issues • igt@i915_selftest@live@ring_submission:
o fi-bsw-n3050: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-
tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@live@ring_submission.html
(https://bugs.freedesktop.org/show_bug.cgi?id=109271) +2 similar issues • igt@kms_chamelium@dp-crc-fast:
o fi-kbl-7500u:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
kbl-7500u/igt@[email protected] -> https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl- 7500u/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/1161 /
https://gitlab.freedesktop.org/drm/intel/issues/262)
Possible fixes
• igt@gem_tiled_blits@basic:
o fi-tgl-y:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-
y/igt@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/402) ->
https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl- y/igt@[email protected] +1 similar issue Warnings • igt@i915_selftest@live@execlists:
o fi-bsw-n3050:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-
bsw-n3050/igt@i915_selftest@[email protected]
(https://gitlab.freedesktop.org/drm/intel/issues/2940) ->
https://intel-gfx-
ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw- n3050/igt@i915_selftest@[email protected]
(https://bugs.freedesktop.org/show_bug.cgi?id=109271)
Participating hosts (41 -> 37)
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u Build changes • Linux:CI_DRM_9666->Patchwork_19447
CI-20190529: 20190529CI_DRM_9666:9ccbc653bf2948d1f7e9ff300dd7679b888ffa25@git://anongit.freedesktop.org/gfx-ci/linuxIGT_5962:22e3daaed82ab7890018a2f2aabf5082cd536023@git://anongit.freedesktop.org/xorg/app/intel-gpu-toolsPatchwork_19447:69d7db003fa406df7851ab08239dd409a78f4421@git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==69d7db003fa4drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Quoted 2 lines · Lakshminarayana
I am not totally sure why shard run is not triggered here https://patchwork.freedesktop.org/series/85555/#rev2
@Latvala, Petri any help here?
The results were there but reporting it failed. Re-reported it and it's now on patchwork.
Signature · 5 lines
Petri Latvala _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
In reply to Sean Paul== Series Details ==
== Series Details ==
Series: drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
URL : https://patchwork.freedesktop.org/series/85555/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9666 -> Patchwork_19447
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
Known issues
------------
Here are the changes found in Patchwork_19447 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_mmap_gtt@basic:
- fi-tgl-y: [PASS][1] -> [DMESG-WARN][2] ([i915#402]) +2 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected]
* igt@i915_selftest@live@gt_lrc:
- fi-bsw-n3050: [PASS][3] -> [DMESG-FAIL][4] ([i915#2998])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
* igt@i915_selftest@live@hugepages:
- fi-bsw-n3050: [PASS][5] -> [SKIP][6] ([fdo#109271]) +20 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@ring_submission:
- fi-bsw-n3050: NOTRUN -> [SKIP][7] ([fdo#109271]) +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@live@ring_submission.html
* igt@kms_chamelium@dp-crc-fast:
- fi-kbl-7500u: [PASS][8] -> [FAIL][9] ([i915#1161] / [i915#262])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-kbl-7500u/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-kbl-7500u/igt@[email protected]
#### Possible fixes ####
* igt@gem_tiled_blits@basic:
- fi-tgl-y: [DMESG-WARN][10] ([i915#402]) -> [PASS][11] +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-tgl-y/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-tgl-y/igt@[email protected]
#### Warnings ####
* igt@i915_selftest@live@execlists:
- fi-bsw-n3050: [INCOMPLETE][12] ([i915#2940]) -> [SKIP][13] ([fdo#109271])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9666/fi-bsw-n3050/igt@i915_selftest@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/fi-bsw-n3050/igt@i915_selftest@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1161]: https://gitlab.freedesktop.org/drm/intel/issues/1161
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#2940]: https://gitlab.freedesktop.org/drm/intel/issues/2940
[i915#2998]: https://gitlab.freedesktop.org/drm/intel/issues/2998
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
Participating hosts (43 -> 37)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-bdw-samus bat-jsl-2 bat-jsl-1
Build changes
-------------
* Linux: CI_DRM_9666 -> Patchwork_19447
CI-20190529: 20190529
CI_DRM_9666: 9ccbc653bf2948d1f7e9ff300dd7679b888ffa25 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5962: 22e3daaed82ab7890018a2f2aabf5082cd536023 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19447: 69d7db003fa406df7851ab08239dd409a78f4421 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
69d7db003fa4 drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
In reply to Sean Paul== Series Details ==
== Series Details ==
Series: drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
URL : https://patchwork.freedesktop.org/series/85555/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9666_full -> Patchwork_19447_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
Changes
-------
No changes found
Participating hosts (10 -> 8)
------------------------------
Missing (2): pig-skl-6260u pig-glk-j5005
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_9666 -> Patchwork_19447
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_9666: 9ccbc653bf2948d1f7e9ff300dd7679b888ffa25 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5962: 22e3daaed82ab7890018a2f2aabf5082cd536023 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19447: 69d7db003fa406df7851ab08239dd409a78f4421 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Gupta, Anshuman
AppliedRe: [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Pushed to drm-intel-next.
From: Intel-gfx <[email protected]> On Behalf Of Patchwork
Sent: Thursday, January 28, 2021 12:36 PM
To: Sean Paul <[email protected]>
Cc: [email protected]
Subject: [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
Patch Details
Series:
drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST (rev2)
URL:
https://patchwork.freedesktop.org/series/85555/
State:
success
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
CI Bug Log - changes from CI_DRM_9666_full -> Patchwork_19447_full Summary
SUCCESS
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19447/index.html
Changes
No changes found
Participating hosts (10 -> 8)
Missing (2): pig-skl-6260u pig-glk-j5005
Build changes
* CI: CI-20190529 -> None * Linux: CI_DRM_9666 -> Patchwork_19447 * Piglit: piglit_4509 -> None
CI-20190529: 20190529CI_DRM_9666: 9ccbc653bf2948d1f7e9ff300dd7679b888ffa25 @ git://anongit.freedesktop.org/gfx-ci/linuxIGT_5962: 22e3daaed82ab7890018a2f2aabf5082cd536023 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-toolsPatchwork_19447: 69d7db003fa406df7851ab08239dd409a78f4421 @ git://anongit.freedesktop.org/gfx-ci/linuxpiglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx