* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
2020-08-22 6:48 [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing Khaled Almahallawy
@ 2020-08-22 7:08 ` Patchwork
2020-08-22 7:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
` (7 subsequent siblings)
8 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2020-08-22 7:08 UTC (permalink / raw)
To: Khaled Almahallawy; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
URL : https://patchwork.freedesktop.org/series/80911/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
dc95490056af drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
-:9: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#9:
there is a retimer between source and sink and the retimer implements AUX_CH
-:26: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#26: FILE: drivers/gpu/drm/i915/display/intel_dp.c:5507:
+ drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_LANE0_SET,
+ intel_dp->train_set, intel_dp->lane_count);
total: 0 errors, 1 warnings, 1 checks, 9 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
2020-08-22 6:48 [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing Khaled Almahallawy
2020-08-22 7:08 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
@ 2020-08-22 7:24 ` Patchwork
2020-08-22 8:35 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
` (6 subsequent siblings)
8 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2020-08-22 7:24 UTC (permalink / raw)
To: Khaled Almahallawy; +Cc: intel-gfx
[-- Attachment #1.1: Type: text/plain, Size: 6313 bytes --]
== Series Details ==
Series: drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
URL : https://patchwork.freedesktop.org/series/80911/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8914 -> Patchwork_18390
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/index.html
Known issues
------------
Here are the changes found in Patchwork_18390 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-kefka: [PASS][1] -> [DMESG-WARN][2] ([i915#1982])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-bsw-kefka/igt@i915_pm_rpm@basic-pci-d3-state.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-bsw-kefka/igt@i915_pm_rpm@basic-pci-d3-state.html
* igt@i915_pm_rpm@module-reload:
- fi-bsw-n3050: [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-bsw-n3050/igt@i915_pm_rpm@module-reload.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-bsw-n3050/igt@i915_pm_rpm@module-reload.html
* igt@i915_selftest@live@gt_lrc:
- fi-tgl-u2: [PASS][5] -> [DMESG-FAIL][6] ([i915#2373])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-tgl-u2/igt@i915_selftest@live@gt_lrc.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-tgl-u2/igt@i915_selftest@live@gt_lrc.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-byt-j1900: [PASS][7] -> [DMESG-WARN][8] ([i915#1982]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-byt-j1900/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-byt-j1900/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_flip@basic-flip-vs-wf_vblank@c-hdmi-a2:
- fi-skl-guc: [PASS][9] -> [DMESG-WARN][10] ([i915#2203])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-skl-guc/igt@kms_flip@basic-flip-vs-wf_vblank@c-hdmi-a2.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-skl-guc/igt@kms_flip@basic-flip-vs-wf_vblank@c-hdmi-a2.html
#### Possible fixes ####
* igt@i915_module_load@reload:
- fi-tgl-u2: [DMESG-WARN][11] ([i915#1982]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-tgl-u2/igt@i915_module_load@reload.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-tgl-u2/igt@i915_module_load@reload.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-bsw-n3050: [DMESG-WARN][13] ([i915#1982]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
#### Warnings ####
* igt@gem_exec_suspend@basic-s3:
- fi-kbl-x1275: [DMESG-WARN][15] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][16] ([i915#1982] / [i915#62] / [i915#92] / [i915#95])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-kbl-x1275/igt@gem_exec_suspend@basic-s3.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-kbl-x1275/igt@gem_exec_suspend@basic-s3.html
* igt@i915_pm_rpm@module-reload:
- fi-kbl-guc: [DMESG-WARN][17] ([i915#2203]) -> [DMESG-FAIL][18] ([i915#2203])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-kbl-guc/igt@i915_pm_rpm@module-reload.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-kbl-guc/igt@i915_pm_rpm@module-reload.html
* igt@kms_force_connector_basic@force-edid:
- fi-kbl-x1275: [DMESG-WARN][19] ([i915#62] / [i915#92]) -> [DMESG-WARN][20] ([i915#62] / [i915#92] / [i915#95]) +5 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-kbl-x1275/igt@kms_force_connector_basic@force-edid.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-kbl-x1275/igt@kms_force_connector_basic@force-edid.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-kbl-x1275: [DMESG-WARN][21] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][22] ([i915#62] / [i915#92]) +2 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/fi-kbl-x1275/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/fi-kbl-x1275/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2100]: https://gitlab.freedesktop.org/drm/intel/issues/2100
[i915#2203]: https://gitlab.freedesktop.org/drm/intel/issues/2203
[i915#2249]: https://gitlab.freedesktop.org/drm/intel/issues/2249
[i915#2373]: https://gitlab.freedesktop.org/drm/intel/issues/2373
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (38 -> 34)
------------------------------
Missing (4): fi-byt-clapper fi-ilk-m540 fi-byt-squawks fi-bsw-cyan
Build changes
-------------
* Linux: CI_DRM_8914 -> Patchwork_18390
CI-20190529: 20190529
CI_DRM_8914: 1339d80a19c0da27c443a4430fd0fe8a9d924b97 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5770: f1d0c240ea2e631dfb9f493f37f8fb61cb2b1cf2 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18390: dc95490056af3c9a4efefef05de333a56a00f888 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
dc95490056af drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/index.html
[-- Attachment #1.2: Type: text/html, Size: 8359 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
2020-08-22 6:48 [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing Khaled Almahallawy
2020-08-22 7:08 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-08-22 7:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
@ 2020-08-22 8:35 ` Patchwork
2020-08-24 21:12 ` [Intel-gfx] [PATCH] " Navare, Manasi
` (5 subsequent siblings)
8 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2020-08-22 8:35 UTC (permalink / raw)
To: Khaled Almahallawy; +Cc: intel-gfx
[-- Attachment #1.1: Type: text/plain, Size: 15602 bytes --]
== Series Details ==
Series: drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
URL : https://patchwork.freedesktop.org/series/80911/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8914_full -> Patchwork_18390_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_18390_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_18390_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_18390_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_ctx_persistence@processes:
- shard-skl: NOTRUN -> [FAIL][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-skl1/igt@gem_ctx_persistence@processes.html
Known issues
------------
Here are the changes found in Patchwork_18390_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_whisper@basic-forked-all:
- shard-glk: [PASS][2] -> [DMESG-WARN][3] ([i915#118] / [i915#95])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-glk6/igt@gem_exec_whisper@basic-forked-all.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-glk8/igt@gem_exec_whisper@basic-forked-all.html
* igt@kms_big_fb@x-tiled-8bpp-rotate-0:
- shard-kbl: [PASS][4] -> [DMESG-WARN][5] ([i915#1982])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-kbl2/igt@kms_big_fb@x-tiled-8bpp-rotate-0.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-kbl4/igt@kms_big_fb@x-tiled-8bpp-rotate-0.html
* igt@kms_big_fb@y-tiled-64bpp-rotate-0:
- shard-glk: [PASS][6] -> [DMESG-WARN][7] ([i915#1982])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-glk1/igt@kms_big_fb@y-tiled-64bpp-rotate-0.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-glk6/igt@kms_big_fb@y-tiled-64bpp-rotate-0.html
* igt@kms_color@pipe-c-ctm-green-to-red:
- shard-skl: [PASS][8] -> [DMESG-WARN][9] ([i915#1982]) +10 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-skl5/igt@kms_color@pipe-c-ctm-green-to-red.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-skl7/igt@kms_color@pipe-c-ctm-green-to-red.html
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic:
- shard-glk: [PASS][10] -> [FAIL][11] ([i915#72])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-glk2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-glk2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html
* igt@kms_draw_crc@draw-method-xrgb2101010-pwrite-ytiled:
- shard-apl: [PASS][12] -> [DMESG-WARN][13] ([i915#1635] / [i915#1982]) +1 similar issue
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-apl7/igt@kms_draw_crc@draw-method-xrgb2101010-pwrite-ytiled.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-apl4/igt@kms_draw_crc@draw-method-xrgb2101010-pwrite-ytiled.html
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][14] -> [FAIL][15] ([i915#79])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-glk2/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-glk2/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: [PASS][16] -> [DMESG-WARN][17] ([i915#180]) +4 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-kbl2/igt@kms_flip@flip-vs-suspend@c-dp1.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-kbl4/igt@kms_flip@flip-vs-suspend@c-dp1.html
* igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1:
- shard-skl: [PASS][18] -> [FAIL][19] ([i915#2122])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-skl10/igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-skl8/igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt:
- shard-tglb: [PASS][20] -> [DMESG-WARN][21] ([i915#1982])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt.html
* igt@kms_hdr@bpc-switch:
- shard-skl: [PASS][22] -> [FAIL][23] ([i915#1188])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-skl9/igt@kms_hdr@bpc-switch.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-skl7/igt@kms_hdr@bpc-switch.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][24] -> [SKIP][25] ([fdo#109441])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-iclb8/igt@kms_psr@psr2_primary_page_flip.html
* igt@perf@blocking-parameterized:
- shard-iclb: [PASS][26] -> [FAIL][27] ([i915#1542])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-iclb5/igt@perf@blocking-parameterized.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-iclb7/igt@perf@blocking-parameterized.html
* igt@prime_busy@hang@bcs0:
- shard-hsw: [PASS][28] -> [FAIL][29] ([i915#2258]) +4 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-hsw8/igt@prime_busy@hang@bcs0.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-hsw4/igt@prime_busy@hang@bcs0.html
#### Possible fixes ####
* igt@gem_exec_balancer@bonded-early:
- shard-kbl: [FAIL][30] ([i915#2079]) -> [PASS][31]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-kbl2/igt@gem_exec_balancer@bonded-early.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-kbl1/igt@gem_exec_balancer@bonded-early.html
* igt@gem_exec_endless@dispatch@rcs0:
- shard-tglb: [INCOMPLETE][32] ([i915#1958]) -> [PASS][33]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-tglb8/igt@gem_exec_endless@dispatch@rcs0.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-tglb8/igt@gem_exec_endless@dispatch@rcs0.html
* igt@gem_exec_whisper@basic-forked:
- shard-glk: [DMESG-WARN][34] ([i915#118] / [i915#95]) -> [PASS][35]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-glk7/igt@gem_exec_whisper@basic-forked.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-glk1/igt@gem_exec_whisper@basic-forked.html
* igt@kms_big_fb@x-tiled-64bpp-rotate-0:
- shard-glk: [DMESG-FAIL][36] ([i915#118] / [i915#95]) -> [PASS][37] +1 similar issue
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-glk8/igt@kms_big_fb@x-tiled-64bpp-rotate-0.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-glk7/igt@kms_big_fb@x-tiled-64bpp-rotate-0.html
* igt@kms_big_fb@x-tiled-8bpp-rotate-0:
- shard-apl: [DMESG-WARN][38] ([i915#1635] / [i915#1982]) -> [PASS][39]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-apl2/igt@kms_big_fb@x-tiled-8bpp-rotate-0.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-apl7/igt@kms_big_fb@x-tiled-8bpp-rotate-0.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-skl: [FAIL][40] ([i915#2346]) -> [PASS][41]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-skl5/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-skl7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: [DMESG-WARN][42] ([i915#180]) -> [PASS][43] +4 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-kbl1/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-kbl4/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-cpu:
- shard-iclb: [DMESG-WARN][44] ([i915#1982]) -> [PASS][45]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-iclb6/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-cpu.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-cpu.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc:
- shard-tglb: [DMESG-WARN][46] ([i915#1982]) -> [PASS][47] +2 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-shrfb-draw-mmap-gtt:
- shard-skl: [FAIL][48] ([i915#49]) -> [PASS][49]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-skl7/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-shrfb-draw-mmap-gtt.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-skl5/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-shrfb-draw-mmap-gtt.html
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [FAIL][50] ([fdo#108145] / [i915#265]) -> [PASS][51]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-skl4/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-skl9/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][52] ([fdo#109642] / [fdo#111068]) -> [PASS][53]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-iclb1/igt@kms_psr2_su@frontbuffer.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-iclb2/igt@kms_psr2_su@frontbuffer.html
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [SKIP][54] ([fdo#109441]) -> [PASS][55] +3 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-iclb3/igt@kms_psr@psr2_cursor_plane_onoff.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@kms_vblank@crtc-id:
- shard-kbl: [DMESG-WARN][56] ([i915#1982]) -> [PASS][57]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-kbl4/igt@kms_vblank@crtc-id.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-kbl2/igt@kms_vblank@crtc-id.html
* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- shard-skl: [INCOMPLETE][58] ([i915#198]) -> [PASS][59] +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-skl10/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-skl6/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
* igt@perf@gen8-unprivileged-single-ctx-counters:
- shard-skl: [DMESG-WARN][60] ([i915#1982]) -> [PASS][61] +10 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-skl9/igt@perf@gen8-unprivileged-single-ctx-counters.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-skl7/igt@perf@gen8-unprivileged-single-ctx-counters.html
#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][62] ([i915#658]) -> [SKIP][63] ([i915#588])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-iclb1/igt@i915_pm_dc@dc3co-vpb-simulation.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-iclb2/igt@i915_pm_dc@dc3co-vpb-simulation.html
* igt@kms_content_protection@atomic:
- shard-kbl: [TIMEOUT][64] ([i915#1319] / [i915#1958]) -> [TIMEOUT][65] ([i915#1319])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8914/shard-kbl4/igt@kms_content_protection@atomic.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18390/shard-kbl2/igt@kms_content_protection@atomic.html
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[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
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2079]: https://gitlab.freedesktop.org/drm/intel/issues/2079
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2258]: https://gitlab.freedesktop.org/drm/intel/issues/2258
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#72]: https://gitlab.freedesktop.org/drm/intel/issues/72
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8914 -> Patchwork_18390
CI-20190529: 20190529
CI_DRM_8914: 1339d80a19c0da27c443a4430fd0fe8a9d924b97 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5770: f1d0c240ea2e631dfb9f493f37f8fb61cb2b1cf2 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18390: dc95490056af3c9a4efefef05de333a56a00f888 @ 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_18390/index.html
[-- Attachment #1.2: Type: text/html, Size: 18225 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
2020-08-22 6:48 [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing Khaled Almahallawy
` (2 preceding siblings ...)
2020-08-22 8:35 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
@ 2020-08-24 21:12 ` Navare, Manasi
2021-01-13 15:04 ` Imre Deak
` (4 subsequent siblings)
8 siblings, 0 replies; 14+ messages in thread
From: Navare, Manasi @ 2020-08-24 21:12 UTC (permalink / raw)
To: Khaled Almahallawy; +Cc: Intel-gfx
On Fri, Aug 21, 2020 at 11:48:37PM -0700, Khaled Almahallawy wrote:
> Source needs to write DPCD 103-106 after receiving a PHY request to change
> swing/pre-emphasis after reading DPCD 206-207. This is especially needed if
> there is a retimer between source and sink and the retimer implements AUX_CH
> interception scheme to manage DP PHY settings (e.g. adjusting Swing/Pre-emphasis
> equalization level) for DP output channel . If the source doesn't write to
> DPCD 103-106, the retimer may not output the requested swing/pre-emphasis and
> eventually we fail compliance.
>
> Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 79c27f91f42c..5044201ca742 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -5503,6 +5503,9 @@ void intel_dp_process_phy_request(struct intel_dp *intel_dp)
>
> intel_dp_autotest_phy_ddi_enable(intel_dp, data->num_lanes);
>
> + drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_LANE0_SET,
> + intel_dp->train_set, intel_dp->lane_count);
Does this also help with spitting out the correct voltage levels during the actual training
Does this fix LT failure seen on Type C ports with retimers?
Manasi
> +
> drm_dp_set_phy_test_pattern(&intel_dp->aux, data,
> link_status[DP_DPCD_REV]);
> }
> --
> 2.17.1
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
2020-08-22 6:48 [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing Khaled Almahallawy
` (3 preceding siblings ...)
2020-08-24 21:12 ` [Intel-gfx] [PATCH] " Navare, Manasi
@ 2021-01-13 15:04 ` Imre Deak
2021-01-19 7:43 ` Almahallawy, Khaled
2021-02-26 8:15 ` [Intel-gfx] [PATCH v2] " Khaled Almahallawy
` (3 subsequent siblings)
8 siblings, 1 reply; 14+ messages in thread
From: Imre Deak @ 2021-01-13 15:04 UTC (permalink / raw)
To: Khaled Almahallawy; +Cc: Intel-gfx
On Fri, Aug 21, 2020 at 11:48:37PM -0700, Khaled Almahallawy wrote:
> Source needs to write DPCD 103-106 after receiving a PHY request to change
> swing/pre-emphasis after reading DPCD 206-207. This is especially needed if
> there is a retimer between source and sink and the retimer implements AUX_CH
> interception scheme to manage DP PHY settings (e.g. adjusting Swing/Pre-emphasis
> equalization level) for DP output channel . If the source doesn't write to
> DPCD 103-106, the retimer may not output the requested swing/pre-emphasis and
> eventually we fail compliance.
>
> Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 79c27f91f42c..5044201ca742 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -5503,6 +5503,9 @@ void intel_dp_process_phy_request(struct intel_dp *intel_dp)
>
> intel_dp_autotest_phy_ddi_enable(intel_dp, data->num_lanes);
>
> + drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_LANE0_SET,
> + intel_dp->train_set, intel_dp->lane_count);
This should be rebased on a recent change using instead
crtc_state->lane_count. That's also not completely correct since it's
not guaranteed that the output is enabled (having up-to-date link params
in crtc_state) at the time of this test request. Also
compliance.test_data.phytest has its own link params that may be
different from the ones in crtc_state.
I'm also not sure how intel_dp_autotest_phy_ddi_disable()/enable()
affects the vswing/pre-emp setting of the source (DPTX) that got inited
when the output was last enabled. The vs/pe programming sequence should
be also part of the port enabling. Maybe the HW retains the config
across the the above port disable/enable calls and so this happens not
to be a problem.
There's been a discussion earlier that instead of open-coding here all
the port enabling/disabling and link training programming sequences the
driver's actual modesetting and link training code should be used
instead, making those aware of the modified PHY test request link
parameters. I suppose until that's done we could still merge this patch
with the above intel_dp/crtc_state fix after you can confirm that this
PHY test functionality actually works atm.
--Imre
> +
> drm_dp_set_phy_test_pattern(&intel_dp->aux, data,
> link_status[DP_DPCD_REV]);
> }
> --
> 2.17.1
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
2021-01-13 15:04 ` Imre Deak
@ 2021-01-19 7:43 ` Almahallawy, Khaled
2021-01-19 17:26 ` Imre Deak
0 siblings, 1 reply; 14+ messages in thread
From: Almahallawy, Khaled @ 2021-01-19 7:43 UTC (permalink / raw)
To: Deak, Imre; +Cc: Intel-gfx
On Wed, 2021-01-13 at 17:04 +0200, Imre Deak wrote:
> On Fri, Aug 21, 2020 at 11:48:37PM -0700, Khaled Almahallawy wrote:
> > Source needs to write DPCD 103-106 after receiving a PHY request to
> > change
> > swing/pre-emphasis after reading DPCD 206-207. This is especially
> > needed if
> > there is a retimer between source and sink and the retimer
> > implements AUX_CH
> > interception scheme to manage DP PHY settings (e.g. adjusting
> > Swing/Pre-emphasis
> > equalization level) for DP output channel . If the source doesn't
> > write to
> > DPCD 103-106, the retimer may not output the requested swing/pre-
> > emphasis and
> > eventually we fail compliance.
> >
> > Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_dp.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
> > b/drivers/gpu/drm/i915/display/intel_dp.c
> > index 79c27f91f42c..5044201ca742 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> > @@ -5503,6 +5503,9 @@ void intel_dp_process_phy_request(struct
> > intel_dp *intel_dp)
> >
> > intel_dp_autotest_phy_ddi_enable(intel_dp, data->num_lanes);
> >
> > + drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_LANE0_SET,
> > + intel_dp->train_set, intel_dp-
> > >lane_count);
>
> This should be rebased on a recent change using instead
> crtc_state->lane_count. That's also not completely correct since it's
> not guaranteed that the output is enabled (having up-to-date link
> params
> in crtc_state) at the time of this test request. Also
Sure, I will rebase, test and resend.
> compliance.test_data.phytest has its own link params that may be
> different from the ones in crtc_state.
Actually, the request to change vswing/pre-emp and PHY test pattern
comes after the request to change Lane count and Link rate. Matter of
fact I think phytest.num_lanes and phytest.link_rate may be not
necessarily needed. However I cannot make this assertion yet until I
exhaust all automation options in the scope.
>
> I'm also not sure how intel_dp_autotest_phy_ddi_disable()/enable()
> affects the vswing/pre-emp setting of the source (DPTX) that got
> inited
> when the output was last enabled. The vs/pe programming sequence
> should
> be also part of the port enabling. Maybe the HW retains the config
> across the the above port disable/enable calls and so this happens
> not
> to be a problem.
>
The requested Vswing/Pre-emph from test scope is coming as part of
short HPD not as part of Link Training, so I’m not sure how we can use
these requested vswing/pre-emph values as we do for lane count and Link
rate as in : intel_dp_adjust_compliance_config
However the rationale behind
intel_dp_autotest_phy_ddi_disable()/enable() is based on Specs:50482
which said TRANS_CONF and TRANS_DDI_FUNC_CTL must be disabled prior to
enabling the test pattern
> There's been a discussion earlier that instead of open-coding here
> all
> the port enabling/disabling and link training programming sequences
> the
> driver's actual modesetting and link training code should be used
> instead, making those aware of the modified PHY test request link
> parameters.
Actually, Ville already did most of the work and I tested his code
intel_dp_phy_test
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -6299,7 +6299,8 @@ intel_dp_short_pulse(struct intel_dp *intel_dp)
* FIXME get rid of the ad-hoc phy test modeset code
* and properly incorporate it into the normal modeset.
*/
- return false;
+ intel_dp_phy_test(encoder);
+ break;
}
return true;
This code even works with quirks of scripting mode of the scope as
well.
However, I am still struggling with scheduling a long HPD. I’m planning
to reply to Ville's patch he sent yesterday: “drm/i915: Fix the PHY
compliance test vs. hotplug mishap” to provide more info about test
automation.
Thank You for you feedback and review.
Khaled
> I suppose until that's done we could still merge this patch
> with the above intel_dp/crtc_state fix after you can confirm that
> this
> PHY test functionality actually works atm.
>
> --Imre
>
> > +
> > drm_dp_set_phy_test_pattern(&intel_dp->aux, data,
> > link_status[DP_DPCD_REV]);
> > }
> > --
> > 2.17.1
> >
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing.
2021-01-19 7:43 ` Almahallawy, Khaled
@ 2021-01-19 17:26 ` Imre Deak
0 siblings, 0 replies; 14+ messages in thread
From: Imre Deak @ 2021-01-19 17:26 UTC (permalink / raw)
To: Almahallawy, Khaled; +Cc: Intel-gfx
On Tue, Jan 19, 2021 at 09:43:56AM +0200, Almahallawy, Khaled wrote:
> > > [...]
> > > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
> > > b/drivers/gpu/drm/i915/display/intel_dp.c
> > > index 79c27f91f42c..5044201ca742 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_dp.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> > > @@ -5503,6 +5503,9 @@ void intel_dp_process_phy_request(struct
> > > intel_dp *intel_dp)
> > >
> > > intel_dp_autotest_phy_ddi_enable(intel_dp, data->num_lanes);
> > >
> > > +drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_LANE0_SET,
> > > +intel_dp->train_set, intel_dp-
> > > >lane_count);
> >
> > This should be rebased on a recent change using instead
> > crtc_state->lane_count.
>
> > That's also not completely correct since it's
> > not guaranteed that the output is enabled (having up-to-date link
> > params in crtc_state) at the time of this test request.
Actually intel_dp_prep_phy_test() makes sure that the output is enabled,
so nvm the above.
> [...]
> > I'm also not sure how intel_dp_autotest_phy_ddi_disable()/enable()
> > affects the vswing/pre-emp setting of the source (DPTX) that got
> > inited when the output was last enabled. The vs/pe programming
> > sequence should be also part of the port enabling. Maybe the HW
> > retains the config across the the above port disable/enable calls
> > and so this happens not to be a problem.
>
> The requested Vswing/Pre-emph from test scope is coming as part of
> short HPD not as part of Link Training, so I’m not sure how we can use
> these requested vswing/pre-emph values as we do for lane count and Link
> rate as in : intel_dp_adjust_compliance_config
Looks like during PHY testing a regular link training should be
performed (including any LTTPRs on the link), and then for DPRX instead
of the regular cr/eq just set the requested vs/pe levels and the test
pattern. If TEST_LANE_COUNT/RATE changes the link needs to be retrained
again, if only the requested test pattern or vs/pe levels change then
changing only these w/o retraining the link should be ok.
> However the rationale behind
> intel_dp_autotest_phy_ddi_disable()/enable() is based on Specs:50482
> which said TRANS_CONF and TRANS_DDI_FUNC_CTL must be disabled prior to
> enabling the test pattern
Ok, makes sense, so this indeed seems to need special casing for PHY
testing.
--Imre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] [PATCH v2] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing
2020-08-22 6:48 [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing Khaled Almahallawy
` (4 preceding siblings ...)
2021-01-13 15:04 ` Imre Deak
@ 2021-02-26 8:15 ` Khaled Almahallawy
2021-07-06 22:30 ` Almahallawy, Khaled
2021-07-29 16:50 ` Imre Deak
2021-02-26 8:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing. (rev2) Patchwork
` (2 subsequent siblings)
8 siblings, 2 replies; 14+ messages in thread
From: Khaled Almahallawy @ 2021-02-26 8:15 UTC (permalink / raw)
To: intel-gfx
Source needs to write DPCD 103-106 after receiving a PHY request to change
swing/pre-emphasis after reading DPCD 206-207. This is especially needed if
there is a retimer between source and sink and the retimer implements AUX_CH
interception scheme to manage DP PHY settings (e.g. adjusting Swing/Pre-emphasis
equalization level) for DP output channel. If the source doesn't write to
DPCD 103-106, the retimer may not output the requested swing/pre-emphasis and
eventually we fail compliance.
v2: Rebase and use crtc->lane_count (Imre)
Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
---
drivers/gpu/drm/i915/display/intel_dp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index 2ec82a5c9f24..1ccf8602b3ef 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -4471,6 +4471,9 @@ static void intel_dp_process_phy_request(struct intel_dp *intel_dp,
intel_dp_autotest_phy_ddi_enable(intel_dp, crtc_state);
+ drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_LANE0_SET,
+ intel_dp->train_set, crtc_state->lane_count);
+
drm_dp_set_phy_test_pattern(&intel_dp->aux, data,
link_status[DP_DPCD_REV]);
}
--
2.25.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing
2021-02-26 8:15 ` [Intel-gfx] [PATCH v2] " Khaled Almahallawy
@ 2021-07-06 22:30 ` Almahallawy, Khaled
2021-07-29 16:50 ` Imre Deak
1 sibling, 0 replies; 14+ messages in thread
From: Almahallawy, Khaled @ 2021-07-06 22:30 UTC (permalink / raw)
To: intel-gfx
Hi Imre,
I applied this patch to today drm-tip and it applied cleanely.
Could you please help with mergin it?
Thanks
Khaled
On Fri, 2021-02-26 at 00:15 -0800, Almahallawy, Khaled wrote:
> Source needs to write DPCD 103-106 after receiving a PHY request to
> change
> swing/pre-emphasis after reading DPCD 206-207. This is especially
> needed if
> there is a retimer between source and sink and the retimer implements
> AUX_CH
> interception scheme to manage DP PHY settings (e.g. adjusting
> Swing/Pre-emphasis
> equalization level) for DP output channel. If the source doesn't
> write to
> DPCD 103-106, the retimer may not output the requested swing/pre-
> emphasis and
> eventually we fail compliance.
>
> v2: Rebase and use crtc->lane_count (Imre)
>
> Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
> b/drivers/gpu/drm/i915/display/intel_dp.c
> index 2ec82a5c9f24..1ccf8602b3ef 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -4471,6 +4471,9 @@ static void intel_dp_process_phy_request(struct
> intel_dp *intel_dp,
>
> intel_dp_autotest_phy_ddi_enable(intel_dp, crtc_state);
>
> + drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_LANE0_SET,
> + intel_dp->train_set, crtc_state->lane_count);
> +
> drm_dp_set_phy_test_pattern(&intel_dp->aux, data,
> link_status[DP_DPCD_REV]);
> }
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing
2021-02-26 8:15 ` [Intel-gfx] [PATCH v2] " Khaled Almahallawy
2021-07-06 22:30 ` Almahallawy, Khaled
@ 2021-07-29 16:50 ` Imre Deak
1 sibling, 0 replies; 14+ messages in thread
From: Imre Deak @ 2021-07-29 16:50 UTC (permalink / raw)
To: Khaled Almahallawy; +Cc: intel-gfx
On Fri, Feb 26, 2021 at 12:15:54AM -0800, Khaled Almahallawy wrote:
> Source needs to write DPCD 103-106 after receiving a PHY request to change
> swing/pre-emphasis after reading DPCD 206-207. This is especially needed if
> there is a retimer between source and sink and the retimer implements AUX_CH
> interception scheme to manage DP PHY settings (e.g. adjusting Swing/Pre-emphasis
> equalization level) for DP output channel. If the source doesn't write to
> DPCD 103-106, the retimer may not output the requested swing/pre-emphasis and
> eventually we fail compliance.
>
> v2: Rebase and use crtc->lane_count (Imre)
>
> Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
Reviewed-by: Imre Deak <imre.deak>
Sorry for the delay, pushed now, thanks for the patch.
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 2ec82a5c9f24..1ccf8602b3ef 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -4471,6 +4471,9 @@ static void intel_dp_process_phy_request(struct intel_dp *intel_dp,
>
> intel_dp_autotest_phy_ddi_enable(intel_dp, crtc_state);
>
> + drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_LANE0_SET,
> + intel_dp->train_set, crtc_state->lane_count);
> +
> drm_dp_set_phy_test_pattern(&intel_dp->aux, data,
> link_status[DP_DPCD_REV]);
> }
> --
> 2.25.1
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing. (rev2)
2020-08-22 6:48 [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing Khaled Almahallawy
` (5 preceding siblings ...)
2021-02-26 8:15 ` [Intel-gfx] [PATCH v2] " Khaled Almahallawy
@ 2021-02-26 8:52 ` Patchwork
2021-02-26 9:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-02-26 11:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
8 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2021-02-26 8:52 UTC (permalink / raw)
To: Khaled Almahallawy; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing. (rev2)
URL : https://patchwork.freedesktop.org/series/80911/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a9246c77517c drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing
-:9: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#9:
there is a retimer between source and sink and the retimer implements AUX_CH
-:28: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#28: FILE: drivers/gpu/drm/i915/display/intel_dp.c:4475:
+ drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_LANE0_SET,
+ intel_dp->train_set, crtc_state->lane_count);
total: 0 errors, 1 warnings, 1 checks, 9 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing. (rev2)
2020-08-22 6:48 [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing Khaled Almahallawy
` (6 preceding siblings ...)
2021-02-26 8:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing. (rev2) Patchwork
@ 2021-02-26 9:23 ` Patchwork
2021-02-26 11:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
8 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2021-02-26 9:23 UTC (permalink / raw)
To: Khaled Almahallawy; +Cc: intel-gfx
[-- Attachment #1.1: Type: text/plain, Size: 3788 bytes --]
== Series Details ==
Series: drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing. (rev2)
URL : https://patchwork.freedesktop.org/series/80911/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9810 -> Patchwork_19731
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/index.html
Known issues
------------
Here are the changes found in Patchwork_19731 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s0:
- fi-tgl-u2: [PASS][1] -> [FAIL][2] ([i915#1888])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/fi-tgl-u2/igt@gem_exec_suspend@basic-s0.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/fi-tgl-u2/igt@gem_exec_suspend@basic-s0.html
* igt@gem_linear_blits@basic:
- fi-kbl-8809g: [PASS][3] -> [TIMEOUT][4] ([i915#2502])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/fi-kbl-8809g/igt@gem_linear_blits@basic.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/fi-kbl-8809g/igt@gem_linear_blits@basic.html
* igt@gem_mmap_gtt@basic:
- fi-tgl-y: [PASS][5] -> [DMESG-WARN][6] ([i915#402]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/fi-tgl-y/igt@gem_mmap_gtt@basic.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/fi-tgl-y/igt@gem_mmap_gtt@basic.html
#### Possible fixes ####
* igt@debugfs_test@read_all_entries:
- fi-tgl-y: [DMESG-WARN][7] ([i915#402]) -> [PASS][8] +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/fi-tgl-y/igt@debugfs_test@read_all_entries.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/fi-tgl-y/igt@debugfs_test@read_all_entries.html
* igt@gem_exec_gttfill@basic:
- fi-kbl-8809g: [TIMEOUT][9] -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
* igt@kms_chamelium@dp-crc-fast:
- fi-kbl-7500u: [DMESG-WARN][11] ([i915#165] / [i915#1982] / [i915#262]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/fi-kbl-7500u/igt@kms_chamelium@dp-crc-fast.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/fi-kbl-7500u/igt@kms_chamelium@dp-crc-fast.html
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2502]: https://gitlab.freedesktop.org/drm/intel/issues/2502
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
Participating hosts (41 -> 37)
------------------------------
Missing (4): fi-ctg-p8600 fi-ilk-m540 fi-bsw-cyan fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_9810 -> Patchwork_19731
CI-20190529: 20190529
CI_DRM_9810: a93586ed1f733634ebb220ff072195ce86b112a9 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6015: aa44cddf4ef689f8a3726fcbeedc03f08b12bd82 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19731: a9246c77517c7e5bcd47ca7ed694193b8336cc78 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a9246c77517c drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/index.html
[-- Attachment #1.2: Type: text/html, Size: 4601 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing. (rev2)
2020-08-22 6:48 [Intel-gfx] [PATCH] drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing Khaled Almahallawy
` (7 preceding siblings ...)
2021-02-26 9:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
@ 2021-02-26 11:24 ` Patchwork
8 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2021-02-26 11:24 UTC (permalink / raw)
To: Khaled Almahallawy; +Cc: intel-gfx
[-- Attachment #1.1: Type: text/plain, Size: 30324 bytes --]
== Series Details ==
Series: drm/i915/dp: DPTX writes Swing/Pre-emphs(DPCD 0x103-0x106) requested during PHY Layer testing. (rev2)
URL : https://patchwork.freedesktop.org/series/80911/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9810_full -> Patchwork_19731_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_19731_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_19731_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_19731_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_pwrite_crc:
- shard-skl: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl5/igt@kms_pwrite_crc.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl5/igt@kms_pwrite_crc.html
#### Warnings ####
* igt@runner@aborted:
- shard-kbl: ([FAIL][3], [FAIL][4], [FAIL][5], [FAIL][6], [FAIL][7], [FAIL][8], [FAIL][9], [FAIL][10], [FAIL][11]) ([i915#1436] / [i915#180] / [i915#1814] / [i915#3002] / [i915#602] / [i915#92]) -> ([FAIL][12], [FAIL][13], [FAIL][14], [FAIL][15], [FAIL][16], [FAIL][17], [FAIL][18], [FAIL][19], [FAIL][20]) ([i915#1436] / [i915#180] / [i915#1814] / [i915#2724] / [i915#3002] / [i915#602])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl4/igt@runner@aborted.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl1/igt@runner@aborted.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl2/igt@runner@aborted.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl1/igt@runner@aborted.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl1/igt@runner@aborted.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl1/igt@runner@aborted.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl7/igt@runner@aborted.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl7/igt@runner@aborted.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl7/igt@runner@aborted.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl1/igt@runner@aborted.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl7/igt@runner@aborted.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl7/igt@runner@aborted.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl1/igt@runner@aborted.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl1/igt@runner@aborted.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl2/igt@runner@aborted.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl3/igt@runner@aborted.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl1/igt@runner@aborted.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl7/igt@runner@aborted.html
Known issues
------------
Here are the changes found in Patchwork_19731_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_create@create-massive:
- shard-apl: NOTRUN -> [DMESG-WARN][21] ([i915#3002])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl3/igt@gem_create@create-massive.html
* igt@gem_ctx_persistence@process:
- shard-snb: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#1099]) +4 similar issues
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-snb7/igt@gem_ctx_persistence@process.html
* igt@gem_ctx_sseu@invalid-args:
- shard-tglb: NOTRUN -> [SKIP][23] ([i915#280])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb2/igt@gem_ctx_sseu@invalid-args.html
* igt@gem_eio@in-flight-suspend:
- shard-skl: [PASS][24] -> [INCOMPLETE][25] ([i915#146] / [i915#198])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl3/igt@gem_eio@in-flight-suspend.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl2/igt@gem_eio@in-flight-suspend.html
* igt@gem_eio@unwedge-stress:
- shard-skl: [PASS][26] -> [TIMEOUT][27] ([i915#2771])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl5/igt@gem_eio@unwedge-stress.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl3/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-tglb: [PASS][28] -> [FAIL][29] ([i915#2842])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-tglb8/igt@gem_exec_fair@basic-none-share@rcs0.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb6/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [PASS][30] -> [FAIL][31] ([i915#2842])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-glk5/igt@gem_exec_fair@basic-pace-share@rcs0.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-glk4/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-kbl: [PASS][32] -> [FAIL][33] ([i915#2842]) +2 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl6/igt@gem_exec_fair@basic-pace@rcs0.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl2/igt@gem_exec_fair@basic-pace@rcs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [PASS][34] -> [FAIL][35] ([i915#2849])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-iclb3/igt@gem_exec_fair@basic-throttle@rcs0.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-iclb7/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@gem_exec_schedule@pi-common@vecs0:
- shard-skl: [PASS][36] -> [DMESG-WARN][37] ([i915#1982])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl5/igt@gem_exec_schedule@pi-common@vecs0.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl5/igt@gem_exec_schedule@pi-common@vecs0.html
* igt@gem_exec_schedule@u-fairslice@bcs0:
- shard-tglb: [PASS][38] -> [DMESG-WARN][39] ([i915#2803])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-tglb7/igt@gem_exec_schedule@u-fairslice@bcs0.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb6/igt@gem_exec_schedule@u-fairslice@bcs0.html
* igt@gem_exec_schedule@u-fairslice@vecs0:
- shard-apl: [PASS][40] -> [DMESG-WARN][41] ([i915#1610])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-apl6/igt@gem_exec_schedule@u-fairslice@vecs0.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl6/igt@gem_exec_schedule@u-fairslice@vecs0.html
* igt@gem_huc_copy@huc-copy:
- shard-kbl: NOTRUN -> [SKIP][42] ([fdo#109271] / [i915#2190])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl6/igt@gem_huc_copy@huc-copy.html
* igt@gem_pread@exhaustion:
- shard-apl: NOTRUN -> [WARN][43] ([i915#2658])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl3/igt@gem_pread@exhaustion.html
* igt@gem_userptr_blits@input-checking:
- shard-snb: NOTRUN -> [DMESG-WARN][44] ([i915#3002])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-snb6/igt@gem_userptr_blits@input-checking.html
* igt@gem_userptr_blits@process-exit-mmap-busy@uc:
- shard-kbl: NOTRUN -> [SKIP][45] ([fdo#109271] / [i915#1699]) +3 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl6/igt@gem_userptr_blits@process-exit-mmap-busy@uc.html
* igt@gem_userptr_blits@process-exit-mmap@wb:
- shard-apl: NOTRUN -> [SKIP][46] ([fdo#109271] / [i915#1699]) +3 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl3/igt@gem_userptr_blits@process-exit-mmap@wb.html
* igt@gem_userptr_blits@vma-merge:
- shard-apl: NOTRUN -> [INCOMPLETE][47] ([i915#2502] / [i915#2667])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl1/igt@gem_userptr_blits@vma-merge.html
- shard-kbl: NOTRUN -> [INCOMPLETE][48] ([i915#2502] / [i915#2667])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl3/igt@gem_userptr_blits@vma-merge.html
* igt@gen7_exec_parse@batch-without-end:
- shard-tglb: NOTRUN -> [SKIP][49] ([fdo#109289]) +1 similar issue
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb2/igt@gen7_exec_parse@batch-without-end.html
* igt@i915_pm_rc6_residency@media-rc6-accuracy:
- shard-tglb: NOTRUN -> [SKIP][50] ([fdo#111719])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb2/igt@i915_pm_rc6_residency@media-rc6-accuracy.html
* igt@i915_selftest@live@hangcheck:
- shard-hsw: [PASS][51] -> [INCOMPLETE][52] ([i915#2782])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-hsw4/igt@i915_selftest@live@hangcheck.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-hsw4/igt@i915_selftest@live@hangcheck.html
* igt@i915_suspend@forcewake:
- shard-apl: [PASS][53] -> [DMESG-WARN][54] ([i915#180])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-apl2/igt@i915_suspend@forcewake.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl8/igt@i915_suspend@forcewake.html
* igt@i915_suspend@sysfs-reader:
- shard-kbl: [PASS][55] -> [DMESG-WARN][56] ([i915#180]) +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl6/igt@i915_suspend@sysfs-reader.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl7/igt@i915_suspend@sysfs-reader.html
* igt@kms_async_flips@alternate-sync-async-flip:
- shard-skl: [PASS][57] -> [FAIL][58] ([i915#2521])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl5/igt@kms_async_flips@alternate-sync-async-flip.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl5/igt@kms_async_flips@alternate-sync-async-flip.html
* igt@kms_big_joiner@basic:
- shard-skl: NOTRUN -> [SKIP][59] ([fdo#109271] / [i915#2705])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl4/igt@kms_big_joiner@basic.html
* igt@kms_ccs@pipe-c-crc-sprite-planes-basic:
- shard-skl: NOTRUN -> [SKIP][60] ([fdo#109271] / [fdo#111304]) +1 similar issue
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl4/igt@kms_ccs@pipe-c-crc-sprite-planes-basic.html
* igt@kms_chamelium@dp-mode-timings:
- shard-apl: NOTRUN -> [SKIP][61] ([fdo#109271] / [fdo#111827]) +16 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl6/igt@kms_chamelium@dp-mode-timings.html
* igt@kms_chamelium@vga-edid-read:
- shard-glk: NOTRUN -> [SKIP][62] ([fdo#109271] / [fdo#111827]) +1 similar issue
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-glk2/igt@kms_chamelium@vga-edid-read.html
* igt@kms_color_chamelium@pipe-a-ctm-0-75:
- shard-kbl: NOTRUN -> [SKIP][63] ([fdo#109271] / [fdo#111827]) +8 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl6/igt@kms_color_chamelium@pipe-a-ctm-0-75.html
* igt@kms_color_chamelium@pipe-b-ctm-blue-to-red:
- shard-tglb: NOTRUN -> [SKIP][64] ([fdo#109284] / [fdo#111827])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb2/igt@kms_color_chamelium@pipe-b-ctm-blue-to-red.html
* igt@kms_color_chamelium@pipe-c-ctm-red-to-blue:
- shard-snb: NOTRUN -> [SKIP][65] ([fdo#109271] / [fdo#111827]) +22 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-snb7/igt@kms_color_chamelium@pipe-c-ctm-red-to-blue.html
* igt@kms_color_chamelium@pipe-invalid-ctm-matrix-sizes:
- shard-skl: NOTRUN -> [SKIP][66] ([fdo#109271] / [fdo#111827]) +7 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl6/igt@kms_color_chamelium@pipe-invalid-ctm-matrix-sizes.html
* igt@kms_cursor_crc@pipe-a-cursor-256x85-random:
- shard-skl: NOTRUN -> [FAIL][67] ([i915#54])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl4/igt@kms_cursor_crc@pipe-a-cursor-256x85-random.html
* igt@kms_cursor_crc@pipe-b-cursor-64x21-random:
- shard-skl: [PASS][68] -> [FAIL][69] ([i915#54]) +3 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl6/igt@kms_cursor_crc@pipe-b-cursor-64x21-random.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl7/igt@kms_cursor_crc@pipe-b-cursor-64x21-random.html
* igt@kms_cursor_crc@pipe-b-cursor-64x64-onscreen:
- shard-kbl: [PASS][70] -> [FAIL][71] ([i915#54])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl6/igt@kms_cursor_crc@pipe-b-cursor-64x64-onscreen.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl2/igt@kms_cursor_crc@pipe-b-cursor-64x64-onscreen.html
- shard-apl: [PASS][72] -> [FAIL][73] ([i915#54])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-apl2/igt@kms_cursor_crc@pipe-b-cursor-64x64-onscreen.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl8/igt@kms_cursor_crc@pipe-b-cursor-64x64-onscreen.html
* igt@kms_cursor_crc@pipe-d-cursor-suspend:
- shard-kbl: NOTRUN -> [SKIP][74] ([fdo#109271]) +55 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl3/igt@kms_cursor_crc@pipe-d-cursor-suspend.html
* igt@kms_cursor_legacy@pipe-d-torture-bo:
- shard-apl: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#533]) +2 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl7/igt@kms_cursor_legacy@pipe-d-torture-bo.html
* igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@a-edp1:
- shard-tglb: NOTRUN -> [FAIL][76] ([i915#2122])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb2/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@a-edp1.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
- shard-skl: [PASS][77] -> [FAIL][78] ([i915#79]) +1 similar issue
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl1/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl5/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html
* igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1:
- shard-skl: [PASS][79] -> [FAIL][80] ([i915#2122])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl6/igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl6/igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile:
- shard-apl: NOTRUN -> [FAIL][81] ([i915#2641])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl3/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-indfb-plflip-blt:
- shard-skl: NOTRUN -> [SKIP][82] ([fdo#109271]) +43 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl4/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-indfb-plflip-blt.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-shrfb-msflip-blt:
- shard-snb: NOTRUN -> [SKIP][83] ([fdo#109271]) +386 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-snb7/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-shrfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-cur-indfb-draw-mmap-cpu:
- shard-tglb: NOTRUN -> [SKIP][84] ([fdo#111825]) +2 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb2/igt@kms_frontbuffer_tracking@psr-2p-primscrn-cur-indfb-draw-mmap-cpu.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-pwrite:
- shard-apl: NOTRUN -> [SKIP][85] ([fdo#109271]) +157 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl2/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-shrfb-msflip-blt:
- shard-glk: NOTRUN -> [SKIP][86] ([fdo#109271]) +13 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-glk2/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-shrfb-msflip-blt.html
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-max:
- shard-skl: NOTRUN -> [FAIL][87] ([fdo#108145] / [i915#265]) +2 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl4/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-max.html
* igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb:
- shard-apl: NOTRUN -> [FAIL][88] ([fdo#108145] / [i915#265]) +2 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl1/igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb.html
- shard-kbl: NOTRUN -> [FAIL][89] ([fdo#108145] / [i915#265]) +1 similar issue
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl3/igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb.html
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [PASS][90] -> [FAIL][91] ([fdo#108145] / [i915#265]) +2 similar issues
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl10/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl10/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-5:
- shard-apl: NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#658]) +1 similar issue
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-5.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-2:
- shard-skl: NOTRUN -> [SKIP][93] ([fdo#109271] / [i915#658])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl4/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-2.html
* igt@kms_psr2_su@page_flip:
- shard-kbl: NOTRUN -> [SKIP][94] ([fdo#109271] / [i915#658])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl6/igt@kms_psr2_su@page_flip.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [PASS][95] -> [DMESG-WARN][96] ([i915#180] / [i915#295])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl1/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
* igt@kms_writeback@writeback-fb-id:
- shard-apl: NOTRUN -> [SKIP][97] ([fdo#109271] / [i915#2437])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl7/igt@kms_writeback@writeback-fb-id.html
* igt@runner@aborted:
- shard-snb: NOTRUN -> [FAIL][98] ([i915#3002] / [i915#698])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-snb6/igt@runner@aborted.html
* igt@sysfs_clients@recycle:
- shard-snb: NOTRUN -> [FAIL][99] ([i915#3028])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-snb2/igt@sysfs_clients@recycle.html
* igt@sysfs_clients@recycle-many:
- shard-iclb: [PASS][100] -> [FAIL][101] ([i915#3028])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-iclb5/igt@sysfs_clients@recycle-many.html
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-iclb6/igt@sysfs_clients@recycle-many.html
- shard-skl: [PASS][102] -> [FAIL][103] ([i915#3028])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl7/igt@sysfs_clients@recycle-many.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl9/igt@sysfs_clients@recycle-many.html
* igt@sysfs_heartbeat_interval@mixed@rcs0:
- shard-skl: [PASS][104] -> [INCOMPLETE][105] ([i915#1731] / [i915#198])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl7/igt@sysfs_heartbeat_interval@mixed@rcs0.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl10/igt@sysfs_heartbeat_interval@mixed@rcs0.html
#### Possible fixes ####
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-skl: [INCOMPLETE][106] ([i915#146] / [i915#198]) -> [PASS][107]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl6/igt@gem_ctx_isolation@preservation-s3@bcs0.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl6/igt@gem_ctx_isolation@preservation-s3@bcs0.html
* igt@gem_ctx_persistence@close-replace-race:
- shard-glk: [TIMEOUT][108] ([i915#2918]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-glk3/igt@gem_ctx_persistence@close-replace-race.html
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-glk8/igt@gem_ctx_persistence@close-replace-race.html
* igt@gem_eio@unwedge-stress:
- shard-tglb: [TIMEOUT][110] ([i915#3063]) -> [PASS][111]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-tglb7/igt@gem_eio@unwedge-stress.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb5/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [FAIL][112] ([i915#2846]) -> [PASS][113]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl6/igt@gem_exec_fair@basic-deadline.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl3/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-iclb: [FAIL][114] ([i915#2842]) -> [PASS][115]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-iclb8/igt@gem_exec_fair@basic-none-share@rcs0.html
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-iclb1/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-kbl: [FAIL][116] ([i915#2842]) -> [PASS][117] +1 similar issue
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl2/igt@gem_exec_fair@basic-none-solo@rcs0.html
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl6/igt@gem_exec_fair@basic-none-solo@rcs0.html
* igt@gem_exec_fair@basic-none-vip@rcs0:
- shard-glk: [FAIL][118] ([i915#2842]) -> [PASS][119]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-glk4/igt@gem_exec_fair@basic-none-vip@rcs0.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-glk5/igt@gem_exec_fair@basic-none-vip@rcs0.html
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-tglb: [FAIL][120] ([i915#2842]) -> [PASS][121]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-tglb2/igt@gem_exec_fair@basic-pace@rcs0.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb5/igt@gem_exec_fair@basic-pace@rcs0.html
* igt@gem_exec_schedule@u-fairslice@rcs0:
- shard-apl: [DMESG-WARN][122] ([i915#1610]) -> [PASS][123]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-apl6/igt@gem_exec_schedule@u-fairslice@rcs0.html
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl6/igt@gem_exec_schedule@u-fairslice@rcs0.html
* igt@gem_vm_create@destroy-race:
- shard-tglb: [FAIL][124] ([i915#2822]) -> [PASS][125]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-tglb1/igt@gem_vm_create@destroy-race.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb2/igt@gem_vm_create@destroy-race.html
* igt@gen9_exec_parse@allowed-all:
- shard-glk: [DMESG-WARN][126] ([i915#1436] / [i915#716]) -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-glk3/igt@gen9_exec_parse@allowed-all.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-glk2/igt@gen9_exec_parse@allowed-all.html
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][128] ([i915#454]) -> [PASS][129]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-iclb6/igt@i915_pm_dc@dc6-psr.html
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-iclb8/igt@i915_pm_dc@dc6-psr.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-hsw: [WARN][130] ([i915#1519]) -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-hsw2/igt@i915_pm_rc6_residency@rc6-idle.html
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-hsw2/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@kms_color@pipe-c-ctm-0-75:
- shard-skl: [DMESG-WARN][132] ([i915#1982]) -> [PASS][133]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl9/igt@kms_color@pipe-c-ctm-0-75.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl10/igt@kms_color@pipe-c-ctm-0-75.html
* igt@kms_cursor_crc@pipe-a-cursor-128x42-onscreen:
- shard-skl: [FAIL][134] ([i915#54]) -> [PASS][135] +5 similar issues
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl10/igt@kms_cursor_crc@pipe-a-cursor-128x42-onscreen.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl4/igt@kms_cursor_crc@pipe-a-cursor-128x42-onscreen.html
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
- shard-hsw: [FAIL][136] ([i915#96]) -> [PASS][137]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-hsw1/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-hsw8/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-skl: [FAIL][138] ([i915#2122]) -> [PASS][139]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl1/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl5/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: [DMESG-WARN][140] ([i915#180]) -> [PASS][141] +7 similar issues
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl7/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-kbl6/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
* igt@kms_hdr@bpc-switch:
- shard-skl: [FAIL][142] ([i915#1188]) -> [PASS][143]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl2/igt@kms_hdr@bpc-switch.html
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl1/igt@kms_hdr@bpc-switch.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-apl: [DMESG-WARN][144] ([i915#180]) -> [PASS][145] +2 similar issues
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-apl1/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-apl6/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
* igt@perf@polling-parameterized:
- shard-skl: [FAIL][146] ([i915#1542]) -> [PASS][147]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-skl4/igt@perf@polling-parameterized.html
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-skl9/igt@perf@polling-parameterized.html
* igt@sysfs_clients@recycle:
- shard-iclb: [FAIL][148] ([i915#3028]) -> [PASS][149]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-iclb1/igt@sysfs_clients@recycle.html
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-iclb8/igt@sysfs_clients@recycle.html
- shard-glk: [FAIL][150] ([i915#3028]) -> [PASS][151]
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-glk4/igt@sysfs_clients@recycle.html
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-glk9/igt@sysfs_clients@recycle.html
* igt@sysfs_clients@recycle-many:
- shard-tglb: [FAIL][152] ([i915#3028]) -> [PASS][153]
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-tglb1/igt@sysfs_clients@recycle-many.html
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/shard-tglb8/igt@sysfs_clients@recycle-many.html
#### Warnings ####
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-kbl: [INCOMPLETE][154] ([i915#155] / [i915#180] / [i915#636]) -> [INCOMPLETE][155] ([i915#155] / [i915#636])
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9810/shard-kbl7/igt@kms_fbcon_fbt
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19731/index.html
[-- Attachment #1.2: Type: text/html, Size: 33847 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 14+ messages in thread