* [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
@ 2021-07-28 4:55 Tejas Upadhyay
2021-07-28 6:15 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
` (6 more replies)
0 siblings, 7 replies; 20+ messages in thread
From: Tejas Upadhyay @ 2021-07-28 4:55 UTC (permalink / raw)
To: igt-dev
some display resolutions like 1366x768 6bpc which does not
have 64B aligned width are creating crc mismatch in
kms_plane_alpha_blend test on Intel platforms.
Also having different alignment requirement by different drivers,
256B aligned width should work for all drm drivers.
amdgpu and radeon, amdgpu_align_pitch: 256B
armada, armada_pitch: 128B
exynos_drm_gem_dumb_create: No alignment required
drm_gem_shmem_dumb_create: 8B
drm_gem_vram_fill_create_dumb: 8B
Thus 256B covers everything we see in the kernel drm drivers.
Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
---
tests/kms_plane_alpha_blend.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/kms_plane_alpha_blend.c b/tests/kms_plane_alpha_blend.c
index d649a09f..864e83f9 100644
--- a/tests/kms_plane_alpha_blend.c
+++ b/tests/kms_plane_alpha_blend.c
@@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe)
w = mode->hdisplay;
h = mode->vdisplay;
+ w = ALIGN(w, 256);
/* recreate all fbs if incompatible */
if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
cairo_t *cr;
--
2.31.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 20+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_alpha_blend: Align width to 256B
2021-07-28 4:55 [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Tejas Upadhyay
@ 2021-07-28 6:15 ` Patchwork
2021-07-28 8:57 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
` (5 subsequent siblings)
6 siblings, 0 replies; 20+ messages in thread
From: Patchwork @ 2021-07-28 6:15 UTC (permalink / raw)
To: Tejas Upadhyay; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 29569 bytes --]
== Series Details ==
Series: tests/kms_plane_alpha_blend: Align width to 256B
URL : https://patchwork.freedesktop.org/series/93095/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10410 -> IGTPW_6068
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/index.html
Known issues
------------
Here are the changes found in IGTPW_6068 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@cs-compute:
- fi-cfl-guc: NOTRUN -> [SKIP][1] ([fdo#109271]) +28 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-guc/igt@amdgpu/amd_basic@cs-compute.html
- fi-elk-e7500: NOTRUN -> [SKIP][2] ([fdo#109271]) +49 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-elk-e7500/igt@amdgpu/amd_basic@cs-compute.html
* igt@amdgpu/amd_basic@cs-gfx:
- fi-hsw-4770: NOTRUN -> [SKIP][3] ([fdo#109271] / [fdo#109315]) +17 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-hsw-4770/igt@amdgpu/amd_basic@cs-gfx.html
- fi-skl-6700k2: NOTRUN -> [SKIP][4] ([fdo#109271]) +33 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-skl-6700k2/igt@amdgpu/amd_basic@cs-gfx.html
* igt@amdgpu/amd_basic@cs-sdma:
- fi-kbl-guc: NOTRUN -> [SKIP][5] ([fdo#109271]) +59 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-guc/igt@amdgpu/amd_basic@cs-sdma.html
- fi-kbl-7500u: NOTRUN -> [SKIP][6] ([fdo#109271]) +30 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-7500u/igt@amdgpu/amd_basic@cs-sdma.html
* igt@amdgpu/amd_basic@memory-alloc:
- fi-cml-u2: NOTRUN -> [SKIP][7] ([fdo#109315]) +17 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cml-u2/igt@amdgpu/amd_basic@memory-alloc.html
* igt@amdgpu/amd_basic@query-info:
- fi-bsw-kefka: NOTRUN -> [SKIP][8] ([fdo#109271]) +34 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bsw-kefka/igt@amdgpu/amd_basic@query-info.html
- fi-tgl-u2: NOTRUN -> [SKIP][9] ([fdo#109315])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-u2/igt@amdgpu/amd_basic@query-info.html
- fi-tgl-1115g4: NOTRUN -> [SKIP][10] ([fdo#109315])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@amdgpu/amd_basic@query-info.html
* igt@amdgpu/amd_basic@semaphore:
- fi-icl-y: NOTRUN -> [SKIP][11] ([fdo#109315]) +17 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-y/igt@amdgpu/amd_basic@semaphore.html
* igt@amdgpu/amd_cs_nop@fork-compute0:
- fi-tgl-u2: NOTRUN -> [SKIP][12] ([fdo#109315] / [i915#2575]) +16 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-u2/igt@amdgpu/amd_cs_nop@fork-compute0.html
- fi-ivb-3770: NOTRUN -> [SKIP][13] ([fdo#109271]) +31 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-ivb-3770/igt@amdgpu/amd_cs_nop@fork-compute0.html
* igt@amdgpu/amd_cs_nop@nop-compute0:
- fi-ilk-650: NOTRUN -> [SKIP][14] ([fdo#109271]) +35 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-ilk-650/igt@amdgpu/amd_cs_nop@nop-compute0.html
* igt@amdgpu/amd_cs_nop@nop-gfx0:
- fi-tgl-1115g4: NOTRUN -> [SKIP][15] ([fdo#109315] / [i915#2575]) +16 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@amdgpu/amd_cs_nop@nop-gfx0.html
* igt@amdgpu/amd_prime@amd-to-i915:
- fi-kbl-x1275: NOTRUN -> [SKIP][16] ([fdo#109271]) +28 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-x1275/igt@amdgpu/amd_prime@amd-to-i915.html
* igt@amdgpu/amd_prime@i915-to-amd:
- fi-snb-2520m: NOTRUN -> [SKIP][17] ([fdo#109271]) +37 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-snb-2520m/igt@amdgpu/amd_prime@i915-to-amd.html
* igt@core_hotunplug@unbind-rebind:
- fi-hsw-4770: NOTRUN -> [WARN][18] ([i915#3718])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-hsw-4770/igt@core_hotunplug@unbind-rebind.html
* igt@fbdev@write:
- fi-bdw-gvtdvm: NOTRUN -> [SKIP][19] ([fdo#109271]) +5 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bdw-gvtdvm/igt@fbdev@write.html
* igt@gem_exec_fence@basic-busy@bcs0:
- fi-kbl-soraka: NOTRUN -> [SKIP][20] ([fdo#109271]) +26 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-soraka/igt@gem_exec_fence@basic-busy@bcs0.html
- fi-apl-guc: NOTRUN -> [SKIP][21] ([fdo#109271]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-apl-guc/igt@gem_exec_fence@basic-busy@bcs0.html
- fi-cml-u2: NOTRUN -> [SKIP][22] ([i915#1208]) +1 similar issue
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cml-u2/igt@gem_exec_fence@basic-busy@bcs0.html
* igt@gem_exec_suspend@basic-s0:
- fi-bdw-gvtdvm: NOTRUN -> [INCOMPLETE][23] ([i915#146])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bdw-gvtdvm/igt@gem_exec_suspend@basic-s0.html
- fi-tgl-1115g4: NOTRUN -> [FAIL][24] ([i915#1888])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@gem_exec_suspend@basic-s0.html
* igt@gem_exec_suspend@basic-s3:
- fi-bwr-2160: NOTRUN -> [SKIP][25] ([fdo#109271]) +60 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bwr-2160/igt@gem_exec_suspend@basic-s3.html
* igt@gem_huc_copy@huc-copy:
- fi-cml-u2: NOTRUN -> [SKIP][26] ([i915#2190])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cml-u2/igt@gem_huc_copy@huc-copy.html
- fi-tgl-u2: NOTRUN -> [SKIP][27] ([i915#2190])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-u2/igt@gem_huc_copy@huc-copy.html
- fi-hsw-4770: NOTRUN -> [SKIP][28] ([fdo#109271]) +6 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-hsw-4770/igt@gem_huc_copy@huc-copy.html
- fi-cfl-guc: NOTRUN -> [SKIP][29] ([fdo#109271] / [i915#2190])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-guc/igt@gem_huc_copy@huc-copy.html
- fi-skl-6700k2: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#2190])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-skl-6700k2/igt@gem_huc_copy@huc-copy.html
- fi-kbl-soraka: NOTRUN -> [SKIP][31] ([fdo#109271] / [i915#2190])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-soraka/igt@gem_huc_copy@huc-copy.html
- fi-glk-dsi: NOTRUN -> [SKIP][32] ([fdo#109271] / [i915#2190])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-glk-dsi/igt@gem_huc_copy@huc-copy.html
- fi-kbl-x1275: NOTRUN -> [SKIP][33] ([fdo#109271] / [i915#2190])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-x1275/igt@gem_huc_copy@huc-copy.html
- fi-kbl-7500u: NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#2190])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-7500u/igt@gem_huc_copy@huc-copy.html
- fi-kbl-guc: NOTRUN -> [SKIP][35] ([fdo#109271] / [i915#2190])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-guc/igt@gem_huc_copy@huc-copy.html
- fi-skl-guc: NOTRUN -> [SKIP][36] ([fdo#109271] / [i915#2190])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-skl-guc/igt@gem_huc_copy@huc-copy.html
- fi-kbl-8809g: NOTRUN -> [SKIP][37] ([fdo#109271] / [i915#2190])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-8809g/igt@gem_huc_copy@huc-copy.html
- fi-kbl-7567u: NOTRUN -> [SKIP][38] ([fdo#109271] / [i915#2190])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-7567u/igt@gem_huc_copy@huc-copy.html
- fi-tgl-1115g4: NOTRUN -> [SKIP][39] ([i915#2190])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@gem_huc_copy@huc-copy.html
- fi-icl-y: NOTRUN -> [SKIP][40] ([i915#2190])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-y/igt@gem_huc_copy@huc-copy.html
- fi-cfl-8109u: NOTRUN -> [SKIP][41] ([fdo#109271] / [i915#2190])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8109u/igt@gem_huc_copy@huc-copy.html
- fi-bxt-dsi: NOTRUN -> [SKIP][42] ([fdo#109271] / [i915#2190])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bxt-dsi/igt@gem_huc_copy@huc-copy.html
- fi-cfl-8700k: NOTRUN -> [SKIP][43] ([fdo#109271] / [i915#2190])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8700k/igt@gem_huc_copy@huc-copy.html
* igt@i915_hangman@error-state-basic:
- fi-apl-guc: NOTRUN -> [DMESG-WARN][44] ([i915#1610])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-apl-guc/igt@i915_hangman@error-state-basic.html
* igt@i915_pm_backlight@basic-brightness:
- fi-hsw-4770: NOTRUN -> [SKIP][45] ([fdo#109271] / [i915#3012])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-hsw-4770/igt@i915_pm_backlight@basic-brightness.html
- fi-tgl-1115g4: NOTRUN -> [SKIP][46] ([i915#1155])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@i915_pm_backlight@basic-brightness.html
* igt@i915_pm_rpm@basic-rte:
- fi-kbl-7500u: NOTRUN -> [FAIL][47] ([i915#579])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-7500u/igt@i915_pm_rpm@basic-rte.html
- fi-kbl-guc: NOTRUN -> [FAIL][48] ([i915#579])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-guc/igt@i915_pm_rpm@basic-rte.html
- fi-cml-u2: NOTRUN -> [FAIL][49] ([i915#579])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cml-u2/igt@i915_pm_rpm@basic-rte.html
- fi-bxt-dsi: NOTRUN -> [FAIL][50] ([i915#579])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bxt-dsi/igt@i915_pm_rpm@basic-rte.html
- fi-hsw-4770: NOTRUN -> [FAIL][51] ([i915#579])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-hsw-4770/igt@i915_pm_rpm@basic-rte.html
- fi-tgl-1115g4: NOTRUN -> [FAIL][52] ([i915#579])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@i915_pm_rpm@basic-rte.html
- fi-cfl-guc: NOTRUN -> [FAIL][53] ([i915#579])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-guc/igt@i915_pm_rpm@basic-rte.html
- fi-skl-guc: NOTRUN -> [FAIL][54] ([i915#579])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-skl-guc/igt@i915_pm_rpm@basic-rte.html
- fi-tgl-u2: NOTRUN -> [FAIL][55] ([i915#579])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-u2/igt@i915_pm_rpm@basic-rte.html
- fi-cfl-8700k: NOTRUN -> [FAIL][56] ([i915#579])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8700k/igt@i915_pm_rpm@basic-rte.html
- fi-icl-y: NOTRUN -> [FAIL][57] ([i915#579])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-y/igt@i915_pm_rpm@basic-rte.html
- fi-skl-6700k2: NOTRUN -> [FAIL][58] ([i915#579])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-skl-6700k2/igt@i915_pm_rpm@basic-rte.html
- fi-glk-dsi: NOTRUN -> [FAIL][59] ([i915#579])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-glk-dsi/igt@i915_pm_rpm@basic-rte.html
- fi-kbl-x1275: NOTRUN -> [FAIL][60] ([i915#579])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-x1275/igt@i915_pm_rpm@basic-rte.html
- fi-bsw-kefka: NOTRUN -> [FAIL][61] ([i915#3855])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bsw-kefka/igt@i915_pm_rpm@basic-rte.html
- fi-cfl-8109u: NOTRUN -> [FAIL][62] ([i915#579])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8109u/igt@i915_pm_rpm@basic-rte.html
- fi-kbl-soraka: NOTRUN -> [FAIL][63] ([i915#579])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-soraka/igt@i915_pm_rpm@basic-rte.html
* igt@i915_pm_rpm@module-reload:
- fi-cfl-8109u: NOTRUN -> [SKIP][64] ([fdo#109271]) +28 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8109u/igt@i915_pm_rpm@module-reload.html
- fi-cfl-8700k: NOTRUN -> [SKIP][65] ([fdo#109271]) +28 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8700k/igt@i915_pm_rpm@module-reload.html
- fi-tgl-u2: NOTRUN -> [SKIP][66] ([i915#579]) +1 similar issue
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-u2/igt@i915_pm_rpm@module-reload.html
- fi-icl-y: NOTRUN -> [SKIP][67] ([i915#579]) +1 similar issue
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-y/igt@i915_pm_rpm@module-reload.html
- fi-tgl-1115g4: NOTRUN -> [SKIP][68] ([i915#579]) +1 similar issue
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@i915_pm_rpm@module-reload.html
- fi-cml-u2: NOTRUN -> [SKIP][69] ([i915#579]) +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cml-u2/igt@i915_pm_rpm@module-reload.html
* igt@i915_selftest@live@gt_pm:
- fi-kbl-soraka: NOTRUN -> [DMESG-FAIL][70] ([i915#1886] / [i915#2291])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-bxt-dsi: NOTRUN -> [SKIP][71] ([fdo#109271] / [fdo#111827]) +8 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bxt-dsi/igt@kms_chamelium@common-hpd-after-suspend.html
- fi-hsw-4770: NOTRUN -> [SKIP][72] ([fdo#109271] / [fdo#111827]) +8 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-hsw-4770/igt@kms_chamelium@common-hpd-after-suspend.html
- fi-tgl-1115g4: NOTRUN -> [SKIP][73] ([fdo#111827]) +8 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@kms_chamelium@common-hpd-after-suspend.html
- fi-kbl-soraka: NOTRUN -> [SKIP][74] ([fdo#109271] / [fdo#111827]) +8 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-soraka/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@dp-crc-fast:
- fi-skl-guc: NOTRUN -> [SKIP][75] ([fdo#109271] / [fdo#111827]) +8 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-skl-guc/igt@kms_chamelium@dp-crc-fast.html
- fi-kbl-7567u: NOTRUN -> [SKIP][76] ([fdo#109271] / [fdo#111827]) +8 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-7567u/igt@kms_chamelium@dp-crc-fast.html
- fi-icl-y: NOTRUN -> [SKIP][77] ([fdo#109284] / [fdo#111827]) +8 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-y/igt@kms_chamelium@dp-crc-fast.html
- fi-bsw-nick: NOTRUN -> [SKIP][78] ([fdo#109271] / [fdo#111827]) +8 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bsw-nick/igt@kms_chamelium@dp-crc-fast.html
* igt@kms_chamelium@dp-edid-read:
- fi-cfl-guc: NOTRUN -> [SKIP][79] ([fdo#109271] / [fdo#111827]) +8 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-guc/igt@kms_chamelium@dp-edid-read.html
* igt@kms_chamelium@dp-hpd-fast:
- fi-ilk-650: NOTRUN -> [SKIP][80] ([fdo#109271] / [fdo#111827]) +8 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-ilk-650/igt@kms_chamelium@dp-hpd-fast.html
- fi-ivb-3770: NOTRUN -> [SKIP][81] ([fdo#109271] / [fdo#111827]) +8 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-ivb-3770/igt@kms_chamelium@dp-hpd-fast.html
- fi-tgl-u2: NOTRUN -> [SKIP][82] ([fdo#109284] / [fdo#111827]) +8 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-u2/igt@kms_chamelium@dp-hpd-fast.html
- fi-cml-u2: NOTRUN -> [SKIP][83] ([fdo#109284] / [fdo#111827]) +8 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cml-u2/igt@kms_chamelium@dp-hpd-fast.html
* igt@kms_chamelium@hdmi-crc-fast:
- fi-kbl-x1275: NOTRUN -> [SKIP][84] ([fdo#109271] / [fdo#111827]) +8 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-x1275/igt@kms_chamelium@hdmi-crc-fast.html
* igt@kms_chamelium@hdmi-edid-read:
- fi-kbl-8809g: NOTRUN -> [SKIP][85] ([fdo#109271] / [fdo#111827]) +8 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-8809g/igt@kms_chamelium@hdmi-edid-read.html
- fi-bsw-kefka: NOTRUN -> [SKIP][86] ([fdo#109271] / [fdo#111827]) +8 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bsw-kefka/igt@kms_chamelium@hdmi-edid-read.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-glk-dsi: NOTRUN -> [SKIP][87] ([fdo#109271] / [fdo#111827]) +8 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-glk-dsi/igt@kms_chamelium@hdmi-hpd-fast.html
- fi-snb-2520m: NOTRUN -> [SKIP][88] ([fdo#109271] / [fdo#111827]) +8 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-snb-2520m/igt@kms_chamelium@hdmi-hpd-fast.html
- fi-cfl-8109u: NOTRUN -> [SKIP][89] ([fdo#109271] / [fdo#111827]) +8 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8109u/igt@kms_chamelium@hdmi-hpd-fast.html
* igt@kms_chamelium@vga-edid-read:
- fi-cfl-8700k: NOTRUN -> [SKIP][90] ([fdo#109271] / [fdo#111827]) +8 similar issues
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8700k/igt@kms_chamelium@vga-edid-read.html
* igt@kms_chamelium@vga-hpd-fast:
- fi-kbl-guc: NOTRUN -> [SKIP][91] ([fdo#109271] / [fdo#111827]) +8 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-guc/igt@kms_chamelium@vga-hpd-fast.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-bxt-dsi: NOTRUN -> [SKIP][92] ([fdo#109271]) +30 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bxt-dsi/igt@kms_force_connector_basic@force-load-detect.html
- fi-tgl-1115g4: NOTRUN -> [SKIP][93] ([fdo#109285])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@kms_force_connector_basic@force-load-detect.html
- fi-cml-u2: NOTRUN -> [SKIP][94] ([fdo#109285])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cml-u2/igt@kms_force_connector_basic@force-load-detect.html
- fi-tgl-u2: NOTRUN -> [SKIP][95] ([fdo#109285])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-u2/igt@kms_force_connector_basic@force-load-detect.html
- fi-icl-y: NOTRUN -> [SKIP][96] ([fdo#109285])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-y/igt@kms_force_connector_basic@force-load-detect.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-hsw-4770: NOTRUN -> [SKIP][97] ([fdo#109271] / [i915#533])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-hsw-4770/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-kbl-7500u: NOTRUN -> [SKIP][98] ([fdo#109271] / [i915#533])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-7500u/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-kbl-guc: NOTRUN -> [SKIP][99] ([fdo#109271] / [i915#533])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-guc/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-cml-u2: NOTRUN -> [SKIP][100] ([fdo#109278] / [i915#533])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cml-u2/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-cfl-8700k: NOTRUN -> [SKIP][101] ([fdo#109271] / [i915#533])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8700k/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-bxt-dsi: NOTRUN -> [SKIP][102] ([fdo#109271] / [i915#533])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bxt-dsi/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-kbl-soraka: NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#533])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-soraka/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-cfl-guc: NOTRUN -> [SKIP][104] ([fdo#109271] / [i915#533])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-guc/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-skl-6700k2: NOTRUN -> [SKIP][105] ([fdo#109271] / [i915#533])
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-skl-6700k2/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-kbl-x1275: NOTRUN -> [SKIP][106] ([fdo#109271] / [i915#533])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-x1275/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-cfl-8109u: NOTRUN -> [SKIP][107] ([fdo#109271] / [i915#533])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cfl-8109u/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-glk-dsi: NOTRUN -> [SKIP][108] ([fdo#109271] / [i915#533])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-glk-dsi/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-icl-y: NOTRUN -> [SKIP][109] ([fdo#109278])
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-y/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-kbl-8809g: NOTRUN -> [SKIP][110] ([fdo#109271] / [i915#533])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-8809g/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-kbl-7567u: NOTRUN -> [SKIP][111] ([fdo#109271] / [i915#533])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-7567u/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-skl-guc: NOTRUN -> [SKIP][112] ([fdo#109271] / [i915#533])
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-skl-guc/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@kms_pipe_crc_basic@read-crc-pipe-c:
- fi-kbl-7567u: NOTRUN -> [SKIP][113] ([fdo#109271]) +59 similar issues
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-7567u/igt@kms_pipe_crc_basic@read-crc-pipe-c.html
* igt@kms_psr@cursor_plane_move:
- fi-kbl-8809g: NOTRUN -> [SKIP][114] ([fdo#109271]) +37 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-kbl-8809g/igt@kms_psr@cursor_plane_move.html
* igt@kms_psr@primary_mmap_gtt:
- fi-skl-guc: NOTRUN -> [SKIP][115] ([fdo#109271]) +28 similar issues
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-skl-guc/igt@kms_psr@primary_mmap_gtt.html
- fi-icl-y: NOTRUN -> [SKIP][116] ([fdo#110189]) +3 similar issues
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-y/igt@kms_psr@primary_mmap_gtt.html
- fi-hsw-4770: NOTRUN -> [SKIP][117] ([fdo#109271] / [i915#1072]) +3 similar issues
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-hsw-4770/igt@kms_psr@primary_mmap_gtt.html
- fi-tgl-1115g4: NOTRUN -> [SKIP][118] ([i915#1072]) +3 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@kms_psr@primary_mmap_gtt.html
* igt@kms_psr@primary_page_flip:
- fi-glk-dsi: NOTRUN -> [SKIP][119] ([fdo#109271]) +30 similar issues
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-glk-dsi/igt@kms_psr@primary_page_flip.html
* igt@prime_vgem@basic-fence-flip:
- fi-bsw-nick: NOTRUN -> [SKIP][120] ([fdo#109271]) +63 similar issues
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bsw-nick/igt@prime_vgem@basic-fence-flip.html
* igt@prime_vgem@basic-userptr:
- fi-pnv-d510: NOTRUN -> [SKIP][121] ([fdo#109271]) +53 similar issues
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-pnv-d510/igt@prime_vgem@basic-userptr.html
- fi-tgl-u2: NOTRUN -> [SKIP][122] ([i915#3301])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-u2/igt@prime_vgem@basic-userptr.html
- fi-tgl-1115g4: NOTRUN -> [SKIP][123] ([i915#3301])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-tgl-1115g4/igt@prime_vgem@basic-userptr.html
- fi-icl-y: NOTRUN -> [SKIP][124] ([i915#3301])
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-y/igt@prime_vgem@basic-userptr.html
- fi-cml-u2: NOTRUN -> [SKIP][125] ([i915#3301])
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-cml-u2/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-icl-u2: NOTRUN -> [FAIL][126] ([i915#1814] / [i915#3363])
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-icl-u2/igt@runner@aborted.html
- fi-apl-guc: NOTRUN -> [FAIL][127] ([i915#2426] / [i915#3363])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-apl-guc/igt@runner@aborted.html
- fi-bdw-5557u: NOTRUN -> [FAIL][128] ([i915#1602] / [i915#2029])
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/fi-bdw-5557u/igt@runner@aborted.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#1208]: https://gitlab.freedesktop.org/drm/intel/issues/1208
[i915#146]: https://gitlab.freedesktop.org/drm/intel/issues/146
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#1610]: https://gitlab.freedesktop.org/drm/intel/issues/1610
[i915#1759]: https://gitlab.freedesktop.org/drm/intel/issues/1759
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#2029]: https://gitlab.freedesktop.org/drm/intel/issues/2029
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
[i915#2373]: https://gitlab.freedesktop.org/drm/intel/issues/2373
[i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#3004]: https://gitlab.freedesktop.org/drm/intel/issues/3004
[i915#3005]: https://gitlab.freedesktop.org/drm/intel/issues/3005
[i915#3011]: https://gitlab.freedesktop.org/drm/intel/issues/3011
[i915#3012]: https://gitlab.freedesktop.org/drm/intel/issues/3012
[i915#3014]: https://gitlab.freedesktop.org/drm/intel/issues/3014
[i915#3015]: https://gitlab.freedesktop.org/drm/intel/issues/3015
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363
[i915#3717]: https://gitlab.freedesktop.org/drm/intel/issues/3717
[i915#3718]: https://gitlab.freedesktop.org/drm/intel/issues/3718
[i915#3844]: https://gitlab.freedesktop.org/drm/intel/issues/3844
[i915#3855]: https://gitlab.freedesktop.org/drm/intel/issues/3855
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#579]: https://gitlab.freedesktop.org/drm/intel/issues/579
Participating hosts (40 -> 35)
------------------------------
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan bat-jsl-1 fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_6153 -> IGTPW_6068
CI-20190529: 20190529
CI_DRM_10410: 82b063ef61ac0ad7002bc8b4ecf3c73aeb53fbd6 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_6068: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/index.html
IGT_6153: a5dffe7499a2f7189718ddf1ccf49060b7c1529d @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/index.html
[-- Attachment #1.2: Type: text/html, Size: 41918 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 20+ messages in thread
* [igt-dev] ✗ GitLab.Pipeline: warning for tests/kms_plane_alpha_blend: Align width to 256B
2021-07-28 4:55 [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Tejas Upadhyay
2021-07-28 6:15 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
@ 2021-07-28 8:57 ` Patchwork
2021-07-28 14:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
` (4 subsequent siblings)
6 siblings, 0 replies; 20+ messages in thread
From: Patchwork @ 2021-07-28 8:57 UTC (permalink / raw)
To: Tejas Upadhyay; +Cc: igt-dev
== Series Details ==
Series: tests/kms_plane_alpha_blend: Align width to 256B
URL : https://patchwork.freedesktop.org/series/93095/
State : warning
== Summary ==
Pipeline status: FAILED.
see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/368942 for the overview.
test:ninja-test-arm64 has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/12237718):
return options.run_func(options)
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 805, in run
return th.doit()
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 555, in doit
self.run_tests(tests)
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 715, in run_tests
self.drain_futures(futures)
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 732, in drain_futures
self.print_stats(numlen, tests, name, result.result(), i)
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 505, in print_stats
result_str += "\n\n" + result.get_log()
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 178, in get_log
res += self.stde
TypeError: can only concatenate str (not "bytes") to str
FAILED: meson-test
/usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
section_end:1627462521:step_script
ERROR: Job failed: execution took longer than 1h0m0s seconds
test:ninja-test-armhf has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/12237719):
return options.run_func(options)
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 805, in run
return th.doit()
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 555, in doit
self.run_tests(tests)
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 715, in run_tests
self.drain_futures(futures)
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 732, in drain_futures
self.print_stats(numlen, tests, name, result.result(), i)
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 505, in print_stats
result_str += "\n\n" + result.get_log()
File "/usr/lib/python3/dist-packages/mesonbuild/mtest.py", line 178, in get_log
res += self.stde
TypeError: can only concatenate str (not "bytes") to str
FAILED: meson-test
/usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
section_end:1627462521:step_script
ERROR: Job failed: execution took longer than 1h0m0s seconds
test:ninja-test-clang has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/12237717):
9/305 lib igt_exit_handler TIMEOUT 30.06 s
--- command ---
/builds/gfx-ci/igt-ci-tags/build/lib/tests/igt_exit_handler
-------
10/305 lib igt_fork TIMEOUT 30.04 s
--- command ---
/builds/gfx-ci/igt-ci-tags/build/lib/tests/igt_fork
-------
Full log written to /builds/gfx-ci/igt-ci-tags/build/meson-logs/testlog.txt
FAILED: meson-test
/usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
section_end:1627462520:step_script
ERROR: Job failed: execution took longer than 1h0m0s seconds
== Logs ==
For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/368942
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 20+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_plane_alpha_blend: Align width to 256B
2021-07-28 4:55 [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Tejas Upadhyay
2021-07-28 6:15 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-07-28 8:57 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
@ 2021-07-28 14:21 ` Patchwork
2021-07-29 8:39 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_alpha_blend: Align width to 256B (rev2) Patchwork
` (3 subsequent siblings)
6 siblings, 0 replies; 20+ messages in thread
From: Patchwork @ 2021-07-28 14:21 UTC (permalink / raw)
To: Tejas Upadhyay; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 30266 bytes --]
== Series Details ==
Series: tests/kms_plane_alpha_blend: Align width to 256B
URL : https://patchwork.freedesktop.org/series/93095/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10410_full -> IGTPW_6068_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_6068_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_6068_full, 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/IGTPW_6068/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_6068_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_selftest@all@damage_iter_no_damage:
- shard-apl: NOTRUN -> [INCOMPLETE][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl8/igt@kms_selftest@all@damage_iter_no_damage.html
New tests
---------
New tests have been introduced between CI_DRM_10410_full and IGTPW_6068_full:
### New IGT tests (1) ###
* igt@kms_busy@extended-pageflip-hang-oldfb@pipe-b:
- Statuses : 1 pass(s)
- Exec time: [0.14] s
Known issues
------------
Here are the changes found in IGTPW_6068_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@chamelium:
- shard-tglb: NOTRUN -> [SKIP][2] ([fdo#111827])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb8/igt@feature_discovery@chamelium.html
- shard-iclb: NOTRUN -> [SKIP][3] ([fdo#111827])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb1/igt@feature_discovery@chamelium.html
* igt@gem_ctx_persistence@legacy-engines-mixed:
- shard-snb: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#1099]) +7 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-snb7/igt@gem_ctx_persistence@legacy-engines-mixed.html
* igt@gem_ctx_sseu@mmap-args:
- shard-tglb: NOTRUN -> [SKIP][5] ([i915#280])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb1/igt@gem_ctx_sseu@mmap-args.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [PASS][6] -> [FAIL][7] ([i915#2846])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-kbl2/igt@gem_exec_fair@basic-deadline.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl6/igt@gem_exec_fair@basic-deadline.html
- shard-apl: NOTRUN -> [FAIL][8] ([i915#2846])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl3/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-tglb: NOTRUN -> [FAIL][9] ([i915#2842])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb7/igt@gem_exec_fair@basic-none-rrul@rcs0.html
* igt@gem_exec_fair@basic-none@vcs1:
- shard-iclb: NOTRUN -> [FAIL][10] ([i915#2842])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb1/igt@gem_exec_fair@basic-none@vcs1.html
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-glk: [PASS][11] -> [FAIL][12] ([i915#2842]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-glk4/igt@gem_exec_fair@basic-pace@vecs0.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk8/igt@gem_exec_fair@basic-pace@vecs0.html
* igt@gem_exec_params@no-blt:
- shard-tglb: NOTRUN -> [SKIP][13] ([fdo#109283])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb3/igt@gem_exec_params@no-blt.html
- shard-iclb: NOTRUN -> [SKIP][14] ([fdo#109283])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb3/igt@gem_exec_params@no-blt.html
* igt@gem_huc_copy@huc-copy:
- shard-kbl: NOTRUN -> [SKIP][15] ([fdo#109271] / [i915#2190])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl1/igt@gem_huc_copy@huc-copy.html
* igt@gem_pread@exhaustion:
- shard-apl: NOTRUN -> [WARN][16] ([i915#2658])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl8/igt@gem_pread@exhaustion.html
* igt@gem_pwrite@basic-exhaustion:
- shard-kbl: NOTRUN -> [WARN][17] ([i915#2658])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl1/igt@gem_pwrite@basic-exhaustion.html
* igt@gem_userptr_blits@access-control:
- shard-tglb: NOTRUN -> [SKIP][18] ([i915#3297])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb2/igt@gem_userptr_blits@access-control.html
* igt@gem_userptr_blits@coherency-sync:
- shard-tglb: NOTRUN -> [SKIP][19] ([fdo#110542])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb7/igt@gem_userptr_blits@coherency-sync.html
* igt@gem_userptr_blits@input-checking:
- shard-tglb: NOTRUN -> [DMESG-WARN][20] ([i915#3002])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb2/igt@gem_userptr_blits@input-checking.html
- shard-apl: NOTRUN -> [DMESG-WARN][21] ([i915#3002])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl8/igt@gem_userptr_blits@input-checking.html
- shard-glk: NOTRUN -> [DMESG-WARN][22] ([i915#3002])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk3/igt@gem_userptr_blits@input-checking.html
- shard-iclb: NOTRUN -> [DMESG-WARN][23] ([i915#3002])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb7/igt@gem_userptr_blits@input-checking.html
- shard-kbl: NOTRUN -> [DMESG-WARN][24] ([i915#3002])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl2/igt@gem_userptr_blits@input-checking.html
- shard-snb: NOTRUN -> [DMESG-WARN][25] ([i915#3002])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-snb7/igt@gem_userptr_blits@input-checking.html
* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][26] ([i915#2724])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-snb7/igt@gem_userptr_blits@vma-merge.html
- shard-tglb: NOTRUN -> [FAIL][27] ([i915#3318])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb8/igt@gem_userptr_blits@vma-merge.html
* igt@gen7_exec_parse@basic-allowed:
- shard-iclb: NOTRUN -> [SKIP][28] ([fdo#109289]) +1 similar issue
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb5/igt@gen7_exec_parse@basic-allowed.html
* igt@gen7_exec_parse@cmd-crossing-page:
- shard-tglb: NOTRUN -> [SKIP][29] ([fdo#109289]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb5/igt@gen7_exec_parse@cmd-crossing-page.html
* igt@gen9_exec_parse@bb-start-far:
- shard-iclb: NOTRUN -> [SKIP][30] ([i915#2856])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb7/igt@gen9_exec_parse@bb-start-far.html
* igt@gen9_exec_parse@shadow-peek:
- shard-tglb: NOTRUN -> [SKIP][31] ([i915#2856]) +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb2/igt@gen9_exec_parse@shadow-peek.html
* igt@i915_pm_backlight@bad-brightness:
- shard-glk: NOTRUN -> [SKIP][32] ([fdo#109271]) +80 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk6/igt@i915_pm_backlight@bad-brightness.html
* igt@i915_pm_dc@dc6-dpms:
- shard-kbl: NOTRUN -> [FAIL][33] ([i915#545])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl6/igt@i915_pm_dc@dc6-dpms.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-kbl: NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#1937])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl7/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp.html
* igt@i915_pm_rc6_residency@media-rc6-accuracy:
- shard-tglb: NOTRUN -> [SKIP][35] ([fdo#109289] / [fdo#111719])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb1/igt@i915_pm_rc6_residency@media-rc6-accuracy.html
* igt@i915_pm_rpm@basic-rte:
- shard-tglb: NOTRUN -> [FAIL][36] ([i915#579])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb6/igt@i915_pm_rpm@basic-rte.html
* igt@i915_pm_rpm@fences:
- shard-tglb: NOTRUN -> [SKIP][37] ([i915#579]) +2 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb6/igt@i915_pm_rpm@fences.html
* igt@i915_pm_rpm@pc8-residency:
- shard-iclb: NOTRUN -> [SKIP][38] ([i915#579])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb8/igt@i915_pm_rpm@pc8-residency.html
* igt@kms_big_fb@linear-32bpp-rotate-0:
- shard-glk: [PASS][39] -> [DMESG-WARN][40] ([i915#118] / [i915#95]) +1 similar issue
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-glk7/igt@kms_big_fb@linear-32bpp-rotate-0.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk1/igt@kms_big_fb@linear-32bpp-rotate-0.html
* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-glk: NOTRUN -> [DMESG-WARN][41] ([i915#118] / [i915#95])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk5/igt@kms_big_fb@linear-32bpp-rotate-180.html
* igt@kms_big_fb@x-tiled-8bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][42] ([fdo#111614])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb8/igt@kms_big_fb@x-tiled-8bpp-rotate-270.html
* igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-kbl: NOTRUN -> [SKIP][43] ([fdo#109271] / [i915#3777]) +2 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl7/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip.html
* igt@kms_big_fb@y-tiled-32bpp-rotate-180:
- shard-iclb: [PASS][44] -> [DMESG-WARN][45] ([i915#3621])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-iclb6/igt@kms_big_fb@y-tiled-32bpp-rotate-180.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb1/igt@kms_big_fb@y-tiled-32bpp-rotate-180.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-glk: NOTRUN -> [SKIP][46] ([fdo#109271] / [i915#3777])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk4/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-180-hflip:
- shard-apl: NOTRUN -> [SKIP][47] ([fdo#109271] / [i915#3777]) +1 similar issue
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl1/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-180-hflip.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0:
- shard-apl: NOTRUN -> [SKIP][48] ([fdo#109271]) +240 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl1/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-tglb: NOTRUN -> [SKIP][49] ([fdo#111615])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb7/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-hflip.html
- shard-iclb: NOTRUN -> [SKIP][50] ([fdo#110723])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb8/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-hflip.html
* igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][51] ([fdo#109278]) +10 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb7/igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-random-ccs-data-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][52] ([i915#3689]) +8 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb8/igt@kms_ccs@pipe-c-random-ccs-data-yf_tiled_ccs.html
* igt@kms_chamelium@hdmi-edid-change-during-suspend:
- shard-apl: NOTRUN -> [SKIP][53] ([fdo#109271] / [fdo#111827]) +17 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl2/igt@kms_chamelium@hdmi-edid-change-during-suspend.html
* igt@kms_chamelium@hdmi-hpd-fast:
- shard-iclb: NOTRUN -> [SKIP][54] ([fdo#109284] / [fdo#111827]) +1 similar issue
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb4/igt@kms_chamelium@hdmi-hpd-fast.html
* igt@kms_chamelium@hdmi-mode-timings:
- shard-snb: NOTRUN -> [SKIP][55] ([fdo#109271] / [fdo#111827]) +24 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-snb5/igt@kms_chamelium@hdmi-mode-timings.html
* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-kbl: NOTRUN -> [SKIP][56] ([fdo#109271] / [fdo#111827]) +13 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl1/igt@kms_color_chamelium@pipe-a-ctm-blue-to-red.html
* igt@kms_color_chamelium@pipe-b-ctm-limited-range:
- shard-tglb: NOTRUN -> [SKIP][57] ([fdo#109284] / [fdo#111827]) +4 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb7/igt@kms_color_chamelium@pipe-b-ctm-limited-range.html
- shard-glk: NOTRUN -> [SKIP][58] ([fdo#109271] / [fdo#111827]) +4 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk1/igt@kms_color_chamelium@pipe-b-ctm-limited-range.html
* igt@kms_color_chamelium@pipe-d-ctm-negative:
- shard-iclb: NOTRUN -> [SKIP][59] ([fdo#109278] / [fdo#109284] / [fdo#111827])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb2/igt@kms_color_chamelium@pipe-d-ctm-negative.html
* igt@kms_content_protection@atomic-dpms:
- shard-kbl: NOTRUN -> [TIMEOUT][60] ([i915#1319])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl2/igt@kms_content_protection@atomic-dpms.html
* igt@kms_content_protection@type1:
- shard-tglb: NOTRUN -> [SKIP][61] ([fdo#111828])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb2/igt@kms_content_protection@type1.html
* igt@kms_content_protection@uevent:
- shard-apl: NOTRUN -> [FAIL][62] ([i915#2105])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl2/igt@kms_content_protection@uevent.html
* igt@kms_cursor_crc@pipe-a-cursor-32x10-offscreen:
- shard-tglb: NOTRUN -> [SKIP][63] ([i915#3359]) +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb6/igt@kms_cursor_crc@pipe-a-cursor-32x10-offscreen.html
* igt@kms_cursor_crc@pipe-a-cursor-512x170-onscreen:
- shard-tglb: NOTRUN -> [SKIP][64] ([fdo#109279] / [i915#3359]) +2 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb8/igt@kms_cursor_crc@pipe-a-cursor-512x170-onscreen.html
* igt@kms_cursor_crc@pipe-b-cursor-512x512-offscreen:
- shard-iclb: NOTRUN -> [SKIP][65] ([fdo#109278] / [fdo#109279]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb6/igt@kms_cursor_crc@pipe-b-cursor-512x512-offscreen.html
* igt@kms_cursor_crc@pipe-d-cursor-256x256-onscreen:
- shard-kbl: NOTRUN -> [SKIP][66] ([fdo#109271]) +211 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl4/igt@kms_cursor_crc@pipe-d-cursor-256x256-onscreen.html
* igt@kms_cursor_crc@pipe-d-cursor-32x32-sliding:
- shard-tglb: NOTRUN -> [SKIP][67] ([i915#3319])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb2/igt@kms_cursor_crc@pipe-d-cursor-32x32-sliding.html
* igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge:
- shard-snb: NOTRUN -> [SKIP][68] ([fdo#109271]) +401 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-snb6/igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge.html
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy:
- shard-iclb: NOTRUN -> [SKIP][69] ([fdo#109274] / [fdo#109278]) +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb1/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy.html
* igt@kms_flip@2x-nonexisting-fb-interruptible:
- shard-iclb: NOTRUN -> [SKIP][70] ([fdo#109274]) +1 similar issue
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb1/igt@kms_flip@2x-nonexisting-fb-interruptible.html
* igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
- shard-apl: NOTRUN -> [DMESG-WARN][71] ([i915#180])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl7/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: NOTRUN -> [DMESG-WARN][72] ([i915#180]) +3 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl4/igt@kms_flip@flip-vs-suspend@c-dp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs:
- shard-kbl: NOTRUN -> [SKIP][73] ([fdo#109271] / [i915#2672]) +1 similar issue
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl4/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs.html
* igt@kms_frontbuffer_tracking@fbc-2p-rte:
- shard-tglb: NOTRUN -> [SKIP][74] ([fdo#111825]) +18 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-2p-rte.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [PASS][75] -> [DMESG-WARN][76] ([i915#180]) +2 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-suspend.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl4/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-draw-pwrite:
- shard-iclb: NOTRUN -> [SKIP][77] ([fdo#109280]) +8 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-draw-pwrite.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- shard-apl: NOTRUN -> [SKIP][78] ([fdo#109271] / [i915#533]) +1 similar issue
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl2/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- shard-glk: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#533])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk2/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@kms_pipe_crc_basic@read-crc-pipe-d-frame-sequence:
- shard-kbl: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#533]) +1 similar issue
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl3/igt@kms_pipe_crc_basic@read-crc-pipe-d-frame-sequence.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][81] ([i915#265])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl3/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html
* igt@kms_plane_alpha_blend@pipe-a-coverage-vs-premult-vs-constant:
- shard-iclb: [PASS][82] -> [SKIP][83] ([fdo#109278])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-iclb3/igt@kms_plane_alpha_blend@pipe-a-coverage-vs-premult-vs-constant.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb2/igt@kms_plane_alpha_blend@pipe-a-coverage-vs-premult-vs-constant.html
* igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max:
- shard-apl: NOTRUN -> [FAIL][84] ([fdo#108145] / [i915#265]) +4 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl8/igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max.html
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max:
- shard-kbl: NOTRUN -> [FAIL][85] ([fdo#108145] / [i915#265]) +2 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl1/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max.html
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-tglb: NOTRUN -> [SKIP][86] ([i915#3536])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb5/igt@kms_plane_lowres@pipe-a-tiling-x.html
* igt@kms_plane_multiple@atomic-pipe-c-tiling-yf:
- shard-tglb: NOTRUN -> [SKIP][87] ([fdo#112054])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb8/igt@kms_plane_multiple@atomic-pipe-c-tiling-yf.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2:
- shard-apl: NOTRUN -> [SKIP][88] ([fdo#109271] / [i915#658]) +5 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl8/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-3:
- shard-kbl: NOTRUN -> [SKIP][89] ([fdo#109271] / [i915#658]) +2 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl3/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-3.html
* igt@kms_psr2_sf@plane-move-sf-dmg-area-1:
- shard-tglb: NOTRUN -> [SKIP][90] ([i915#2920])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb6/igt@kms_psr2_sf@plane-move-sf-dmg-area-1.html
- shard-glk: NOTRUN -> [SKIP][91] ([fdo#109271] / [i915#658])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk7/igt@kms_psr2_sf@plane-move-sf-dmg-area-1.html
- shard-iclb: NOTRUN -> [SKIP][92] ([i915#658])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb6/igt@kms_psr2_sf@plane-move-sf-dmg-area-1.html
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: NOTRUN -> [SKIP][93] ([fdo#109441])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb4/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [PASS][94] -> [SKIP][95] ([fdo#109441])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb3/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-tglb: NOTRUN -> [FAIL][96] ([i915#132] / [i915#3467]) +1 similar issue
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb8/igt@kms_psr@psr2_sprite_mmap_gtt.html
* igt@kms_sysfs_edid_timing:
- shard-apl: NOTRUN -> [FAIL][97] ([IGT#2])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl6/igt@kms_sysfs_edid_timing.html
- shard-kbl: NOTRUN -> [FAIL][98] ([IGT#2])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl2/igt@kms_sysfs_edid_timing.html
* igt@kms_writeback@writeback-check-output:
- shard-kbl: NOTRUN -> [SKIP][99] ([fdo#109271] / [i915#2437])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl3/igt@kms_writeback@writeback-check-output.html
* igt@nouveau_crc@pipe-a-source-outp-complete:
- shard-tglb: NOTRUN -> [SKIP][100] ([i915#2530])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb1/igt@nouveau_crc@pipe-a-source-outp-complete.html
- shard-iclb: NOTRUN -> [SKIP][101] ([i915#2530])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb5/igt@nouveau_crc@pipe-a-source-outp-complete.html
* igt@perf_pmu@rc6-runtime-pm:
- shard-tglb: NOTRUN -> [SKIP][102] ([fdo#111719])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb7/igt@perf_pmu@rc6-runtime-pm.html
* igt@prime_nv_api@nv_self_import_to_different_fd:
- shard-tglb: NOTRUN -> [SKIP][103] ([fdo#109291])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb8/igt@prime_nv_api@nv_self_import_to_different_fd.html
- shard-iclb: NOTRUN -> [SKIP][104] ([fdo#109291])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb1/igt@prime_nv_api@nv_self_import_to_different_fd.html
* igt@sysfs_clients@fair-3:
- shard-kbl: NOTRUN -> [SKIP][105] ([fdo#109271] / [i915#2994]) +3 similar issues
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl7/igt@sysfs_clients@fair-3.html
* igt@sysfs_clients@pidname:
- shard-iclb: NOTRUN -> [SKIP][106] ([i915#2994])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb6/igt@sysfs_clients@pidname.html
- shard-glk: NOTRUN -> [SKIP][107] ([fdo#109271] / [i915#2994]) +1 similar issue
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk7/igt@sysfs_clients@pidname.html
- shard-tglb: NOTRUN -> [SKIP][108] ([i915#2994])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb6/igt@sysfs_clients@pidname.html
* igt@sysfs_clients@sema-50:
- shard-apl: NOTRUN -> [SKIP][109] ([fdo#109271] / [i915#2994]) +2 similar issues
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-apl7/igt@sysfs_clients@sema-50.html
#### Possible fixes ####
* igt@gem_eio@in-flight-contexts-1us:
- shard-iclb: [TIMEOUT][110] ([i915#3070]) -> [PASS][111]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-iclb1/igt@gem_eio@in-flight-contexts-1us.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb2/igt@gem_eio@in-flight-contexts-1us.html
* igt@gem_exec_fair@basic-deadline:
- shard-glk: [FAIL][112] ([i915#2846]) -> [PASS][113]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-glk7/igt@gem_exec_fair@basic-deadline.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk5/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [FAIL][114] ([i915#2842]) -> [PASS][115] +1 similar issue
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-kbl1/igt@gem_exec_fair@basic-none@vcs0.html
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl1/igt@gem_exec_fair@basic-none@vcs0.html
* igt@gem_exec_fair@basic-none@vecs0:
- shard-glk: [FAIL][116] ([i915#2842] / [i915#3468]) -> [PASS][117]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-glk2/igt@gem_exec_fair@basic-none@vecs0.html
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk5/igt@gem_exec_fair@basic-none@vecs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [FAIL][118] ([i915#2842]) -> [PASS][119] +2 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-tglb1/igt@gem_exec_fair@basic-pace-share@rcs0.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb1/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-kbl: [SKIP][120] ([fdo#109271]) -> [PASS][121]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-kbl1/igt@gem_exec_fair@basic-pace@vcs0.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl4/igt@gem_exec_fair@basic-pace@vcs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [FAIL][122] ([i915#2842]) -> [PASS][123] +2 similar issues
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-glk1/igt@gem_exec_fair@basic-throttle@rcs0.html
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk2/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@kms_big_fb@x-tiled-32bpp-rotate-180:
- shard-glk: [DMESG-WARN][124] ([i915#118] / [i915#95]) -> [PASS][125] +1 similar issue
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-glk9/igt@kms_big_fb@x-tiled-32bpp-rotate-180.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk9/igt@kms_big_fb@x-tiled-32bpp-rotate-180.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-glk: [FAIL][126] ([i915#2346]) -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-glk3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-glk2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: [DMESG-WARN][128] ([i915#180]) -> [PASS][129] +3 similar issues
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-kbl4/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-kbl3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
* igt@kms_plane_multiple@atomic-pipe-a-tiling-y:
- shard-tglb: [INCOMPLETE][130] -> [PASS][131] +1 similar issue
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-tglb8/igt@kms_plane_multiple@atomic-pipe-a-tiling-y.html
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-tglb5/igt@kms_plane_multiple@atomic-pipe-a-tiling-y.html
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][132] ([fdo#109642] / [fdo#111068] / [i915#658]) -> [PASS][133]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10410/shard-iclb8/igt@kms_psr2_su@frontbuffer.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/shard-iclb2/igt@kms_psr2_su@frontbuffer.html
* igt@kms_psr@psr2_basic:
- shard-iclb: [SKIP][134] ([fdo#109441]
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6068/index.html
[-- Attachment #1.2: Type: text/html, Size: 33951 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 20+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_alpha_blend: Align width to 256B (rev2)
2021-07-28 4:55 [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Tejas Upadhyay
` (2 preceding siblings ...)
2021-07-28 14:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
@ 2021-07-29 8:39 ` Patchwork
2021-07-29 11:23 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
` (2 subsequent siblings)
6 siblings, 0 replies; 20+ messages in thread
From: Patchwork @ 2021-07-29 8:39 UTC (permalink / raw)
To: Surendrakumar Upadhyay, TejaskumarX; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 4252 bytes --]
== Series Details ==
Series: tests/kms_plane_alpha_blend: Align width to 256B (rev2)
URL : https://patchwork.freedesktop.org/series/93095/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10417 -> IGTPW_6073
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/index.html
Known issues
------------
Here are the changes found in IGTPW_6073 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_fence@basic-busy@bcs0:
- fi-kbl-soraka: NOTRUN -> [SKIP][1] ([fdo#109271]) +26 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/fi-kbl-soraka/igt@gem_exec_fence@basic-busy@bcs0.html
* igt@gem_exec_suspend@basic-s3:
- fi-tgl-u2: [PASS][2] -> [FAIL][3] ([i915#1888])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html
* igt@gem_huc_copy@huc-copy:
- fi-kbl-soraka: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#2190])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/fi-kbl-soraka/igt@gem_huc_copy@huc-copy.html
* igt@i915_pm_rpm@basic-rte:
- fi-kbl-soraka: NOTRUN -> [FAIL][5] ([i915#579])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/fi-kbl-soraka/igt@i915_pm_rpm@basic-rte.html
* igt@i915_selftest@live@gt_pm:
- fi-kbl-soraka: NOTRUN -> [DMESG-FAIL][6] ([i915#1886] / [i915#2291])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-soraka: NOTRUN -> [SKIP][7] ([fdo#109271] / [fdo#111827]) +8 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/fi-kbl-soraka/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@hdmi-crc-fast:
- fi-kbl-7500u: [PASS][8] -> [DMESG-FAIL][9] ([i915#165])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-fast.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-fast.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-kbl-soraka: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#533])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/fi-kbl-soraka/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s0:
- fi-tgl-1115g4: [FAIL][11] ([i915#1888]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/fi-tgl-1115g4/igt@gem_exec_suspend@basic-s0.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/fi-tgl-1115g4/igt@gem_exec_suspend@basic-s0.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#579]: https://gitlab.freedesktop.org/drm/intel/issues/579
Participating hosts (39 -> 34)
------------------------------
Additional (1): fi-kbl-soraka
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-bdw-samus bat-jsl-1
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_6156 -> IGTPW_6073
CI-20190529: 20190529
CI_DRM_10417: 6ceb5605cd217d203ddb9519b5cb21669ac6c193 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_6073: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/index.html
IGT_6156: 354638455597ac48ac433606b24b82a4d7b65d20 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/index.html
[-- Attachment #1.2: Type: text/html, Size: 5326 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 20+ messages in thread
* [igt-dev] ✗ GitLab.Pipeline: warning for tests/kms_plane_alpha_blend: Align width to 256B (rev2)
2021-07-28 4:55 [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Tejas Upadhyay
` (3 preceding siblings ...)
2021-07-29 8:39 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_alpha_blend: Align width to 256B (rev2) Patchwork
@ 2021-07-29 11:23 ` Patchwork
2021-07-29 16:04 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2021-07-30 5:50 ` [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Sharma, Swati2
6 siblings, 0 replies; 20+ messages in thread
From: Patchwork @ 2021-07-29 11:23 UTC (permalink / raw)
To: Surendrakumar Upadhyay, TejaskumarX; +Cc: igt-dev
== Series Details ==
Series: tests/kms_plane_alpha_blend: Align width to 256B (rev2)
URL : https://patchwork.freedesktop.org/series/93095/
State : warning
== Summary ==
Pipeline status: FAILED.
see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/370032 for the overview.
test:ninja-test has failed (https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/12301269):
9/305 lib igt_exit_handler TIMEOUT 30.05 s
--- command ---
/builds/gfx-ci/igt-ci-tags/build/lib/tests/igt_exit_handler
-------
10/305 lib igt_fork TIMEOUT 30.05 s
--- command ---
/builds/gfx-ci/igt-ci-tags/build/lib/tests/igt_fork
-------
Full log written to /builds/gfx-ci/igt-ci-tags/build/meson-logs/testlog.txt
FAILED: meson-test
/usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
section_end:1627557519:step_script
ERROR: Job failed: execution took longer than 1h0m0s seconds
== Logs ==
For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/pipelines/370032
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 20+ messages in thread
* [igt-dev] ✓ Fi.CI.IGT: success for tests/kms_plane_alpha_blend: Align width to 256B (rev2)
2021-07-28 4:55 [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Tejas Upadhyay
` (4 preceding siblings ...)
2021-07-29 11:23 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
@ 2021-07-29 16:04 ` Patchwork
2021-07-30 5:50 ` [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Sharma, Swati2
6 siblings, 0 replies; 20+ messages in thread
From: Patchwork @ 2021-07-29 16:04 UTC (permalink / raw)
To: Surendrakumar Upadhyay, TejaskumarX; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 30273 bytes --]
== Series Details ==
Series: tests/kms_plane_alpha_blend: Align width to 256B (rev2)
URL : https://patchwork.freedesktop.org/series/93095/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10417_full -> IGTPW_6073_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/index.html
Known issues
------------
Here are the changes found in IGTPW_6073_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@preservation-s3@rcs0:
- shard-apl: [PASS][1] -> [DMESG-WARN][2] ([i915#180])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-apl7/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl1/igt@gem_ctx_isolation@preservation-s3@rcs0.html
* igt@gem_ctx_isolation@preservation-s3@vcs0:
- shard-kbl: [PASS][3] -> [DMESG-WARN][4] ([i915#180]) +3 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-kbl1/igt@gem_ctx_isolation@preservation-s3@vcs0.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl6/igt@gem_ctx_isolation@preservation-s3@vcs0.html
* igt@gem_ctx_persistence@smoketest:
- shard-snb: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#1099]) +6 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-snb7/igt@gem_ctx_persistence@smoketest.html
* igt@gem_eio@unwedge-stress:
- shard-snb: NOTRUN -> [FAIL][6] ([i915#3354])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-snb5/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [PASS][7] -> [FAIL][8] ([i915#2846])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-kbl2/igt@gem_exec_fair@basic-deadline.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl3/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-glk: NOTRUN -> [FAIL][9] ([i915#2842])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk3/igt@gem_exec_fair@basic-none-solo@rcs0.html
- shard-iclb: NOTRUN -> [FAIL][10] ([i915#2842])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb1/igt@gem_exec_fair@basic-none-solo@rcs0.html
- shard-tglb: NOTRUN -> [FAIL][11] ([i915#2842])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb2/igt@gem_exec_fair@basic-none-solo@rcs0.html
* igt@gem_exec_fair@basic-none-vip@rcs0:
- shard-glk: [PASS][12] -> [FAIL][13] ([i915#2842])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-glk5/igt@gem_exec_fair@basic-none-vip@rcs0.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk9/igt@gem_exec_fair@basic-none-vip@rcs0.html
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-tglb: [PASS][14] -> [FAIL][15] ([i915#2842])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-tglb5/igt@gem_exec_fair@basic-pace@rcs0.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb7/igt@gem_exec_fair@basic-pace@rcs0.html
* igt@gem_mmap_gtt@cpuset-big-copy-odd:
- shard-iclb: [PASS][16] -> [FAIL][17] ([i915#307])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb7/igt@gem_mmap_gtt@cpuset-big-copy-odd.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb4/igt@gem_mmap_gtt@cpuset-big-copy-odd.html
* igt@gem_userptr_blits@coherency-sync:
- shard-tglb: NOTRUN -> [SKIP][18] ([fdo#110542])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb6/igt@gem_userptr_blits@coherency-sync.html
- shard-iclb: NOTRUN -> [SKIP][19] ([fdo#109290])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb3/igt@gem_userptr_blits@coherency-sync.html
* igt@gem_userptr_blits@coherency-unsync:
- shard-tglb: NOTRUN -> [SKIP][20] ([i915#3297])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb5/igt@gem_userptr_blits@coherency-unsync.html
- shard-iclb: NOTRUN -> [SKIP][21] ([i915#3297]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb7/igt@gem_userptr_blits@coherency-unsync.html
* igt@gem_userptr_blits@dmabuf-sync:
- shard-kbl: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#3323])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl4/igt@gem_userptr_blits@dmabuf-sync.html
- shard-iclb: NOTRUN -> [SKIP][23] ([i915#3323])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb5/igt@gem_userptr_blits@dmabuf-sync.html
- shard-apl: NOTRUN -> [SKIP][24] ([fdo#109271] / [i915#3323])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl3/igt@gem_userptr_blits@dmabuf-sync.html
- shard-glk: NOTRUN -> [SKIP][25] ([fdo#109271] / [i915#3323])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk5/igt@gem_userptr_blits@dmabuf-sync.html
- shard-tglb: NOTRUN -> [SKIP][26] ([i915#3323])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb7/igt@gem_userptr_blits@dmabuf-sync.html
* igt@gen3_render_tiledy_blits:
- shard-tglb: NOTRUN -> [SKIP][27] ([fdo#109289]) +3 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb3/igt@gen3_render_tiledy_blits.html
* igt@gen9_exec_parse@cmd-crossing-page:
- shard-iclb: NOTRUN -> [SKIP][28] ([i915#2856])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb7/igt@gen9_exec_parse@cmd-crossing-page.html
* igt@i915_pm_backlight@fade_with_dpms:
- shard-iclb: NOTRUN -> [SKIP][29] ([i915#579]) +4 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb7/igt@i915_pm_backlight@fade_with_dpms.html
* igt@i915_pm_rpm@dpms-mode-unset-lpsp:
- shard-tglb: NOTRUN -> [SKIP][30] ([i915#579]) +2 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb3/igt@i915_pm_rpm@dpms-mode-unset-lpsp.html
* igt@i915_query@query-topology-known-pci-ids:
- shard-tglb: NOTRUN -> [SKIP][31] ([fdo#109303])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb6/igt@i915_query@query-topology-known-pci-ids.html
- shard-iclb: NOTRUN -> [SKIP][32] ([fdo#109303])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb3/igt@i915_query@query-topology-known-pci-ids.html
* igt@i915_suspend@forcewake:
- shard-kbl: NOTRUN -> [DMESG-WARN][33] ([i915#180]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl6/igt@i915_suspend@forcewake.html
* igt@kms_big_fb@linear-16bpp-rotate-90:
- shard-iclb: NOTRUN -> [SKIP][34] ([fdo#110725] / [fdo#111614]) +1 similar issue
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb1/igt@kms_big_fb@linear-16bpp-rotate-90.html
* igt@kms_big_fb@x-tiled-16bpp-rotate-90:
- shard-tglb: NOTRUN -> [SKIP][35] ([fdo#111614])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb5/igt@kms_big_fb@x-tiled-16bpp-rotate-90.html
* igt@kms_big_fb@x-tiled-32bpp-rotate-0:
- shard-glk: [PASS][36] -> [DMESG-WARN][37] ([i915#118] / [i915#95]) +1 similar issue
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-glk8/igt@kms_big_fb@x-tiled-32bpp-rotate-0.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk6/igt@kms_big_fb@x-tiled-32bpp-rotate-0.html
* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-kbl: NOTRUN -> [SKIP][38] ([fdo#109271] / [i915#3777])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl1/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip.html
* igt@kms_big_fb@yf-tiled-8bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][39] ([fdo#110723]) +1 similar issue
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb4/igt@kms_big_fb@yf-tiled-8bpp-rotate-270.html
- shard-tglb: NOTRUN -> [SKIP][40] ([fdo#111615])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb8/igt@kms_big_fb@yf-tiled-8bpp-rotate-270.html
* igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][41] ([i915#3689]) +3 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb6/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-d-bad-pixel-format-y_tiled_ccs:
- shard-snb: NOTRUN -> [SKIP][42] ([fdo#109271]) +432 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-snb5/igt@kms_ccs@pipe-d-bad-pixel-format-y_tiled_ccs.html
* igt@kms_chamelium@hdmi-hpd-for-each-pipe:
- shard-kbl: NOTRUN -> [SKIP][43] ([fdo#109271] / [fdo#111827]) +16 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl7/igt@kms_chamelium@hdmi-hpd-for-each-pipe.html
* igt@kms_color_chamelium@pipe-a-ctm-0-25:
- shard-snb: NOTRUN -> [SKIP][44] ([fdo#109271] / [fdo#111827]) +18 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-snb7/igt@kms_color_chamelium@pipe-a-ctm-0-25.html
* igt@kms_color_chamelium@pipe-a-ctm-limited-range:
- shard-apl: NOTRUN -> [SKIP][45] ([fdo#109271] / [fdo#111827]) +23 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl2/igt@kms_color_chamelium@pipe-a-ctm-limited-range.html
* igt@kms_color_chamelium@pipe-c-ctm-0-5:
- shard-iclb: NOTRUN -> [SKIP][46] ([fdo#109284] / [fdo#111827]) +7 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb8/igt@kms_color_chamelium@pipe-c-ctm-0-5.html
- shard-glk: NOTRUN -> [SKIP][47] ([fdo#109271] / [fdo#111827]) +5 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk9/igt@kms_color_chamelium@pipe-c-ctm-0-5.html
* igt@kms_color_chamelium@pipe-c-degamma:
- shard-tglb: NOTRUN -> [SKIP][48] ([fdo#109284] / [fdo#111827]) +5 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb2/igt@kms_color_chamelium@pipe-c-degamma.html
* igt@kms_content_protection@dp-mst-lic-type-1:
- shard-iclb: NOTRUN -> [SKIP][49] ([i915#3116])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb7/igt@kms_content_protection@dp-mst-lic-type-1.html
- shard-tglb: NOTRUN -> [SKIP][50] ([i915#3116])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb5/igt@kms_content_protection@dp-mst-lic-type-1.html
* igt@kms_content_protection@srm:
- shard-apl: NOTRUN -> [TIMEOUT][51] ([i915#1319])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl1/igt@kms_content_protection@srm.html
* igt@kms_cursor_crc@pipe-a-cursor-32x32-onscreen:
- shard-tglb: NOTRUN -> [SKIP][52] ([i915#3319])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb8/igt@kms_cursor_crc@pipe-a-cursor-32x32-onscreen.html
* igt@kms_cursor_crc@pipe-a-cursor-max-size-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][53] ([i915#3359]) +3 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb6/igt@kms_cursor_crc@pipe-a-cursor-max-size-rapid-movement.html
* igt@kms_cursor_crc@pipe-c-cursor-512x170-random:
- shard-iclb: NOTRUN -> [SKIP][54] ([fdo#109278] / [fdo#109279]) +1 similar issue
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb1/igt@kms_cursor_crc@pipe-c-cursor-512x170-random.html
* igt@kms_cursor_crc@pipe-c-cursor-512x512-random:
- shard-tglb: NOTRUN -> [SKIP][55] ([fdo#109279] / [i915#3359]) +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb8/igt@kms_cursor_crc@pipe-c-cursor-512x512-random.html
* igt@kms_cursor_legacy@2x-flip-vs-cursor-atomic:
- shard-iclb: NOTRUN -> [SKIP][56] ([fdo#109274] / [fdo#109278]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb4/igt@kms_cursor_legacy@2x-flip-vs-cursor-atomic.html
* igt@kms_flip@2x-nonexisting-fb:
- shard-iclb: NOTRUN -> [SKIP][57] ([fdo#109274]) +5 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb7/igt@kms_flip@2x-nonexisting-fb.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt:
- shard-kbl: NOTRUN -> [SKIP][58] ([fdo#109271]) +229 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl3/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-move:
- shard-iclb: NOTRUN -> [SKIP][59] ([fdo#109280]) +12 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb1/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-move.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-move:
- shard-tglb: NOTRUN -> [SKIP][60] ([fdo#111825]) +12 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb6/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-move.html
* igt@kms_hdmi_inject@inject-audio:
- shard-tglb: [PASS][61] -> [SKIP][62] ([i915#433])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-tglb8/igt@kms_hdmi_inject@inject-audio.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb3/igt@kms_hdmi_inject@inject-audio.html
* igt@kms_hdr@static-toggle-suspend:
- shard-iclb: NOTRUN -> [SKIP][63] ([i915#1187])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb8/igt@kms_hdr@static-toggle-suspend.html
* igt@kms_pipe_b_c_ivb@from-pipe-c-to-b-with-3-lanes:
- shard-iclb: NOTRUN -> [SKIP][64] ([fdo#109289]) +3 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb2/igt@kms_pipe_b_c_ivb@from-pipe-c-to-b-with-3-lanes.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- shard-apl: NOTRUN -> [SKIP][65] ([fdo#109271] / [i915#533]) +2 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl3/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d:
- shard-kbl: NOTRUN -> [SKIP][66] ([fdo#109271] / [i915#533]) +1 similar issue
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl3/igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][67] ([fdo#108145] / [i915#265]) +1 similar issue
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl1/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-basic:
- shard-apl: NOTRUN -> [FAIL][68] ([fdo#108145] / [i915#265]) +2 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl6/igt@kms_plane_alpha_blend@pipe-a-alpha-basic.html
* igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][69] ([i915#265])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl2/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html
- shard-kbl: NOTRUN -> [FAIL][70] ([i915#265])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl3/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html
* igt@kms_plane_alpha_blend@pipe-d-constant-alpha-min:
- shard-iclb: NOTRUN -> [SKIP][71] ([fdo#109278]) +33 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb2/igt@kms_plane_alpha_blend@pipe-d-constant-alpha-min.html
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-iclb: NOTRUN -> [SKIP][72] ([i915#3536])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb4/igt@kms_plane_lowres@pipe-a-tiling-x.html
* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-apl: NOTRUN -> [SKIP][73] ([fdo#109271] / [i915#2733])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl3/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1:
- shard-iclb: NOTRUN -> [SKIP][74] ([i915#658])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb7/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1:
- shard-kbl: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#658]) +3 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl1/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1.html
* igt@kms_psr2_sf@plane-move-sf-dmg-area-2:
- shard-apl: NOTRUN -> [SKIP][76] ([fdo#109271] / [i915#658]) +5 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl7/igt@kms_psr2_sf@plane-move-sf-dmg-area-2.html
* igt@kms_psr2_su@frontbuffer:
- shard-glk: NOTRUN -> [SKIP][77] ([fdo#109271] / [i915#658])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk2/igt@kms_psr2_su@frontbuffer.html
- shard-tglb: NOTRUN -> [SKIP][78] ([i915#1911])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb8/igt@kms_psr2_su@frontbuffer.html
- shard-iclb: NOTRUN -> [SKIP][79] ([fdo#109642] / [fdo#111068] / [i915#658])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb3/igt@kms_psr2_su@frontbuffer.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: NOTRUN -> [SKIP][80] ([fdo#109441])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb7/igt@kms_psr@psr2_cursor_mmap_cpu.html
- shard-tglb: NOTRUN -> [FAIL][81] ([i915#132] / [i915#3467])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb5/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][82] -> [SKIP][83] ([fdo#109441]) +1 similar issue
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb5/igt@kms_psr@psr2_no_drrs.html
* igt@kms_sysfs_edid_timing:
- shard-apl: NOTRUN -> [FAIL][84] ([IGT#2])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl6/igt@kms_sysfs_edid_timing.html
* igt@kms_tv_load_detect@load-detect:
- shard-iclb: NOTRUN -> [SKIP][85] ([fdo#109309])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb7/igt@kms_tv_load_detect@load-detect.html
* igt@kms_vblank@pipe-d-ts-continuation-idle:
- shard-apl: NOTRUN -> [SKIP][86] ([fdo#109271]) +299 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl2/igt@kms_vblank@pipe-d-ts-continuation-idle.html
* igt@kms_vblank@pipe-d-ts-continuation-modeset-hang:
- shard-glk: NOTRUN -> [SKIP][87] ([fdo#109271]) +52 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk6/igt@kms_vblank@pipe-d-ts-continuation-modeset-hang.html
* igt@kms_writeback@writeback-fb-id:
- shard-apl: NOTRUN -> [SKIP][88] ([fdo#109271] / [i915#2437])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl1/igt@kms_writeback@writeback-fb-id.html
* igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame:
- shard-tglb: NOTRUN -> [SKIP][89] ([i915#2530]) +1 similar issue
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb8/igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame.html
- shard-iclb: NOTRUN -> [SKIP][90] ([i915#2530]) +2 similar issues
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb4/igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame.html
* igt@nouveau_crc@pipe-d-source-rg:
- shard-iclb: NOTRUN -> [SKIP][91] ([fdo#109278] / [i915#2530])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb6/igt@nouveau_crc@pipe-d-source-rg.html
* igt@prime_nv_pcopy@test3_3:
- shard-iclb: NOTRUN -> [SKIP][92] ([fdo#109291]) +1 similar issue
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb2/igt@prime_nv_pcopy@test3_3.html
* igt@prime_nv_test@i915_blt_fill_nv_read:
- shard-tglb: NOTRUN -> [SKIP][93] ([fdo#109291]) +1 similar issue
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb6/igt@prime_nv_test@i915_blt_fill_nv_read.html
* igt@prime_vgem@coherency-gtt:
- shard-tglb: NOTRUN -> [SKIP][94] ([fdo#111656])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb6/igt@prime_vgem@coherency-gtt.html
- shard-iclb: NOTRUN -> [SKIP][95] ([fdo#109292])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb8/igt@prime_vgem@coherency-gtt.html
* igt@sysfs_clients@sema-10:
- shard-apl: NOTRUN -> [SKIP][96] ([fdo#109271] / [i915#2994]) +4 similar issues
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl8/igt@sysfs_clients@sema-10.html
* igt@sysfs_clients@sema-25:
- shard-kbl: NOTRUN -> [SKIP][97] ([fdo#109271] / [i915#2994]) +1 similar issue
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl1/igt@sysfs_clients@sema-25.html
* igt@sysfs_preempt_timeout@timeout@vecs0:
- shard-glk: [PASS][98] -> [FAIL][99] ([i915#1755])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-glk9/igt@sysfs_preempt_timeout@timeout@vecs0.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk4/igt@sysfs_preempt_timeout@timeout@vecs0.html
#### Possible fixes ####
* igt@gem_eio@in-flight-contexts-10ms:
- shard-tglb: [TIMEOUT][100] ([i915#3063]) -> [PASS][101]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-tglb2/igt@gem_eio@in-flight-contexts-10ms.html
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb7/igt@gem_eio@in-flight-contexts-10ms.html
* igt@gem_exec_fair@basic-deadline:
- shard-glk: [FAIL][102] ([i915#2846]) -> [PASS][103]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-glk9/igt@gem_exec_fair@basic-deadline.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk5/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-tglb: [FAIL][104] ([i915#2842]) -> [PASS][105]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-tglb8/igt@gem_exec_fair@basic-none-share@rcs0.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb7/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [FAIL][106] ([i915#2842]) -> [PASS][107]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-glk4/igt@gem_exec_fair@basic-pace-share@rcs0.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk9/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [FAIL][108] ([i915#2842]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb3/igt@gem_exec_fair@basic-throttle@rcs0.html
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb5/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [DMESG-WARN][110] ([i915#118] / [i915#95]) -> [PASS][111]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-glk4/igt@gem_exec_whisper@basic-queues-forked-all.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-glk5/igt@gem_exec_whisper@basic-queues-forked-all.html
* igt@gem_mmap_gtt@cpuset-big-copy:
- shard-iclb: [FAIL][112] ([i915#2428]) -> [PASS][113]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb5/igt@gem_mmap_gtt@cpuset-big-copy.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb5/igt@gem_mmap_gtt@cpuset-big-copy.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [WARN][114] ([i915#2684]) -> [PASS][115]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb2/igt@i915_pm_rc6_residency@rc6-idle.html
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb4/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@i915_selftest@live@hangcheck:
- shard-snb: [INCOMPLETE][116] ([i915#2782]) -> [PASS][117]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-snb2/igt@i915_selftest@live@hangcheck.html
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-snb5/igt@i915_selftest@live@hangcheck.html
* igt@kms_big_fb@x-tiled-64bpp-rotate-180:
- shard-iclb: [DMESG-WARN][118] ([i915#3621]) -> [PASS][119]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb1/igt@kms_big_fb@x-tiled-64bpp-rotate-180.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb8/igt@kms_big_fb@x-tiled-64bpp-rotate-180.html
* igt@kms_flip@flip-vs-expired-vblank@b-edp1:
- shard-tglb: [FAIL][120] ([i915#79]) -> [PASS][121]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-tglb3/igt@kms_flip@flip-vs-expired-vblank@b-edp1.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb3/igt@kms_flip@flip-vs-expired-vblank@b-edp1.html
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: [DMESG-WARN][122] ([i915#180]) -> [PASS][123] +6 similar issues
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-kbl6/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl3/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
* igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
- shard-apl: [DMESG-WARN][124] ([i915#180]) -> [PASS][125]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-apl8/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
* igt@kms_psr@psr2_primary_mmap_gtt:
- shard-iclb: [SKIP][126] ([fdo#109441]) -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb3/igt@kms_psr@psr2_primary_mmap_gtt.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb2/igt@kms_psr@psr2_primary_mmap_gtt.html
#### Warnings ####
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-iclb: [FAIL][128] ([i915#2842]) -> [FAIL][129] ([i915#2852])
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb4/igt@gem_exec_fair@basic-none-rrul@rcs0.html
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb4/igt@gem_exec_fair@basic-none-rrul@rcs0.html
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: [WARN][130] ([i915#2684]) -> [WARN][131] ([i915#1804] / [i915#2684])
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb2/igt@i915_pm_rc6_residency@rc6-fence.html
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb7/igt@i915_pm_rc6_residency@rc6-fence.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-tglb: [WARN][132] ([i915#2681] / [i915#2684]) -> [FAIL][133] ([i915#3591])
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-tglb3/igt@i915_pm_rc6_residency@rc6-idle.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-tglb8/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][134] ([i915#180]) -> [INCOMPLETE][135] ([i915#155])
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-suspend.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-kbl4/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_psr2_sf@plane-move-sf-dmg-area-0:
- shard-iclb: [SKIP][136] ([i915#658]) -> [SKIP][137] ([i915#2920]) +1 similar issue
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb4/igt@kms_psr2_sf@plane-move-sf-dmg-area-0.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb2/igt@kms_psr2_sf@plane-move-sf-dmg-area-0.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-iclb: [SKIP][138] ([i915#2920]) -> [SKIP][139] ([i915#658]) +2 similar issues
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10417/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/shard-iclb8/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1.html
* igt@runner@aborted:
- shard-kbl: ([FAIL][140], [FAIL][141], [FAIL][142], [FAIL][143], [FAIL][144], [FAIL][145], [FAIL][146], [FAIL][147], [FAIL][148], [FAIL][149], [FAIL][150], [FAIL][151]) ([fdo#109271] / [i915#1436] / [i915#180] / [i915#1814] / [i915#2426] / [i915#2505] / [i915#3002] / [i915#3363] / [i915#92]) -> ([FAIL][152], [FAIL][153], [FAIL][154], [FAIL][155], [FAIL][156], [FAIL][157], [FAIL][158], [FAIL][159], [FAIL][160], [FAIL][161]) ([i915#1436] / [i915#180] / [i915#1814] / [i
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6073/index.html
[-- Attachment #1.2: Type: text/html, Size: 33775 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-07-28 4:55 [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Tejas Upadhyay
` (5 preceding siblings ...)
2021-07-29 16:04 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
@ 2021-07-30 5:50 ` Sharma, Swati2
2021-08-02 12:12 ` Juha-Pekka Heikkila
6 siblings, 1 reply; 20+ messages in thread
From: Sharma, Swati2 @ 2021-07-30 5:50 UTC (permalink / raw)
To: Tejas Upadhyay, igt-dev
Reviewed-by:
Swati Sharma <swati2.sharma@intel.com>
On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
> some display resolutions like 1366x768 6bpc which does not
> have 64B aligned width are creating crc mismatch in
> kms_plane_alpha_blend test on Intel platforms.
>
> Also having different alignment requirement by different drivers,
> 256B aligned width should work for all drm drivers.
>
> amdgpu and radeon, amdgpu_align_pitch: 256B
> armada, armada_pitch: 128B
> exynos_drm_gem_dumb_create: No alignment required
> drm_gem_shmem_dumb_create: 8B
> drm_gem_vram_fill_create_dumb: 8B
>
> Thus 256B covers everything we see in the kernel drm drivers.
> Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
> ---
> tests/kms_plane_alpha_blend.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/kms_plane_alpha_blend.c b/tests/kms_plane_alpha_blend.c
> index d649a09f..864e83f9 100644
> --- a/tests/kms_plane_alpha_blend.c
> +++ b/tests/kms_plane_alpha_blend.c
> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe)
> w = mode->hdisplay;
> h = mode->vdisplay;
>
> + w = ALIGN(w, 256);
> /* recreate all fbs if incompatible */
> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
> cairo_t *cr;
>
--
~Swati Sharma
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-07-30 5:50 ` [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Sharma, Swati2
@ 2021-08-02 12:12 ` Juha-Pekka Heikkila
2021-08-02 13:04 ` Sharma, Swati2
0 siblings, 1 reply; 20+ messages in thread
From: Juha-Pekka Heikkila @ 2021-08-02 12:12 UTC (permalink / raw)
To: Sharma, Swati2, Tejas Upadhyay, igt-dev
Hi Tejas, Swati,
I was confused when I read this patch, mind you tell what happen here?
To me it look like nothing matches with each other with the patch.
Even subject is telling other things than what this patch actually does.
On 30.7.2021 8.50, Sharma, Swati2 wrote:
> Reviewed-by:
> Swati Sharma <swati2.sharma@intel.com>
>
> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
>> some display resolutions like 1366x768 6bpc which does not
>> have 64B aligned width are creating crc mismatch in
>> kms_plane_alpha_blend test on Intel platforms.
hm. You are saying none of Intel hw is able to show 1366 wide
framebuffers correctly? And it is fixed by hiding it from being tested?
Memory given from kernel will have 64B alignment. You can easily see by
yourself.
>>
>> Also having different alignment requirement by different drivers,
>> 256B aligned width should work for all drm drivers.
You are saying you are fixing some problem with Intel hw, what does all
this other stuff have to do with it? None of those other drivers are
able to show 1366 pixels wide framebuffers either?
>>
>> amdgpu and radeon, amdgpu_align_pitch: 256B
>> armada, armada_pitch: 128B
>> exynos_drm_gem_dumb_create: No alignment required
>> drm_gem_shmem_dumb_create: 8B
>> drm_gem_vram_fill_create_dumb: 8B
>>
>> Thus 256B covers everything we see in the kernel drm drivers.
>> Signed-off-by: Tejas Upadhyay
>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
>> ---
>> tests/kms_plane_alpha_blend.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/tests/kms_plane_alpha_blend.c
>> b/tests/kms_plane_alpha_blend.c
>> index d649a09f..864e83f9 100644
>> --- a/tests/kms_plane_alpha_blend.c
>> +++ b/tests/kms_plane_alpha_blend.c
>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
>> igt_output_t *output, enum pipe pipe)
>> w = mode->hdisplay;
>> h = mode->vdisplay;
>> + w = ALIGN(w, 256);
This doesn't cause anything to align with 256 bytes. This makes fb width
in pixels divisible by 256. For anything to do with fb alignments..this
has very little to do. Kernel will do viewport clipping hence for actual
intended test this does nothing. FB alignments are handled otherwise as
in this case with with linear fb will have 64 bytes per stride.
>> /* recreate all fbs if incompatible */
>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
>> cairo_t *cr;
>>
>
If this patch actually fixed anything you'll need to create hw wa and
this need to be fixed in kernel. Not testing is not fixing. Imo there
should be no problem for Intel hw to show varying fb sizes, including
1366 wide.
/Juha-Pekka
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-02 12:12 ` Juha-Pekka Heikkila
@ 2021-08-02 13:04 ` Sharma, Swati2
2021-08-02 14:16 ` Juha-Pekka Heikkila
2021-08-02 14:16 ` Surendrakumar Upadhyay, TejaskumarX
0 siblings, 2 replies; 20+ messages in thread
From: Sharma, Swati2 @ 2021-08-02 13:04 UTC (permalink / raw)
To: juhapekka.heikkila, Tejas Upadhyay, igt-dev
Hi JP,
Tejas reapplied the same fix as in
https://patchwork.freedesktop.org/patch/445010/?series=92751&rev=2 which
was reviewed by Daniel.
On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
> Hi Tejas, Swati,
>
> I was confused when I read this patch, mind you tell what happen here?
> To me it look like nothing matches with each other with the patch.
>
> Even subject is telling other things than what this patch actually does.
>
> On 30.7.2021 8.50, Sharma, Swati2 wrote:
>> Reviewed-by:
>> Swati Sharma <swati2.sharma@intel.com>
>>
>> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
>>> some display resolutions like 1366x768 6bpc which does not
>>> have 64B aligned width are creating crc mismatch in
>>> kms_plane_alpha_blend test on Intel platforms.
>
> hm. You are saying none of Intel hw is able to show 1366 wide
> framebuffers correctly? And it is fixed by hiding it from being tested?
>
> Memory given from kernel will have 64B alignment. You can easily see by
> yourself.
>
>>>
>>> Also having different alignment requirement by different drivers,
>>> 256B aligned width should work for all drm drivers.
>
> You are saying you are fixing some problem with Intel hw, what does all
> this other stuff have to do with it? None of those other drivers are
> able to show 1366 pixels wide framebuffers either?
>
>>>
>>> amdgpu and radeon, amdgpu_align_pitch: 256B
>>> armada, armada_pitch: 128B
>>> exynos_drm_gem_dumb_create: No alignment required
>>> drm_gem_shmem_dumb_create: 8B
>>> drm_gem_vram_fill_create_dumb: 8B
>>>
>>> Thus 256B covers everything we see in the kernel drm drivers.
>>> Signed-off-by: Tejas Upadhyay
>>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
>>> ---
>>> tests/kms_plane_alpha_blend.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/tests/kms_plane_alpha_blend.c
>>> b/tests/kms_plane_alpha_blend.c
>>> index d649a09f..864e83f9 100644
>>> --- a/tests/kms_plane_alpha_blend.c
>>> +++ b/tests/kms_plane_alpha_blend.c
>>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
>>> igt_output_t *output, enum pipe pipe)
>>> w = mode->hdisplay;
>>> h = mode->vdisplay;
>>> + w = ALIGN(w, 256);
>
> This doesn't cause anything to align with 256 bytes. This makes fb width
> in pixels divisible by 256. For anything to do with fb alignments..this
> has very little to do. Kernel will do viewport clipping hence for actual
> intended test this does nothing. FB alignments are handled otherwise as
> in this case with with linear fb will have 64 bytes per stride.
>
>>> /* recreate all fbs if incompatible */
>>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
>>> cairo_t *cr;
>>>
>>
>
> If this patch actually fixed anything you'll need to create hw wa and
> this need to be fixed in kernel. Not testing is not fixing. Imo there
> should be no problem for Intel hw to show varying fb sizes, including
> 1366 wide.
>
> /Juha-Pekka
--
~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-02 13:04 ` Sharma, Swati2
@ 2021-08-02 14:16 ` Juha-Pekka Heikkila
2021-08-02 14:16 ` Surendrakumar Upadhyay, TejaskumarX
1 sibling, 0 replies; 20+ messages in thread
From: Juha-Pekka Heikkila @ 2021-08-02 14:16 UTC (permalink / raw)
To: Sharma, Swati2, Tejas Upadhyay, igt-dev
On 2.8.2021 16.04, Sharma, Swati2 wrote:
> Hi JP,
>
> Tejas reapplied the same fix as in
> https://patchwork.freedesktop.org/patch/445010/?series=92751&rev=2 which
> was reviewed by Daniel.
I didn't notice anyone having reviewed that patch but it's different
story. That patch anyway is about vgem driver.
Those comments about alignments apply to that kms_prime patch too, fix
there is not aligning to 256 bytes but 256 pixels. kms_prime use 32bpp
hence it's aligning to 1024B, not to 256B
Fix there is to be able to move buffer memory between devices..and not
trying to be too complex with it. Real fix there would be to do fb stuff
correctly, not like kms_prime now does:
for (size_t idx = 0; idx < scratch->size / sizeof(*ptr); ++idx)
ptr[idx] = color;
On i915 driver itself does agree with itself about alignments. I still
think intel hw will be able to show varying size fb's, not just those
where width is divisible by 256. We have all the juggling with strides
to take care of fb alignments.
As is I see this patch was only hiding some potential real problem and
kms_prime would need proper fix too.
/Juha-Pekka
>
> On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
>> Hi Tejas, Swati,
>>
>> I was confused when I read this patch, mind you tell what happen here?
>> To me it look like nothing matches with each other with the patch.
>>
>> Even subject is telling other things than what this patch actually does.
>>
>> On 30.7.2021 8.50, Sharma, Swati2 wrote:
>>> Reviewed-by:
>>> Swati Sharma <swati2.sharma@intel.com>
>>>
>>> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
>>>> some display resolutions like 1366x768 6bpc which does not
>>>> have 64B aligned width are creating crc mismatch in
>>>> kms_plane_alpha_blend test on Intel platforms.
>>
>> hm. You are saying none of Intel hw is able to show 1366 wide
>> framebuffers correctly? And it is fixed by hiding it from being tested?
>>
>> Memory given from kernel will have 64B alignment. You can easily see
>> by yourself.
>>
>>>>
>>>> Also having different alignment requirement by different drivers,
>>>> 256B aligned width should work for all drm drivers.
>>
>> You are saying you are fixing some problem with Intel hw, what does
>> all this other stuff have to do with it? None of those other drivers
>> are able to show 1366 pixels wide framebuffers either?
>>
>>>>
>>>> amdgpu and radeon, amdgpu_align_pitch: 256B
>>>> armada, armada_pitch: 128B
>>>> exynos_drm_gem_dumb_create: No alignment required
>>>> drm_gem_shmem_dumb_create: 8B
>>>> drm_gem_vram_fill_create_dumb: 8B
>>>>
>>>> Thus 256B covers everything we see in the kernel drm drivers.
>>>> Signed-off-by: Tejas Upadhyay
>>>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
>>>> ---
>>>> tests/kms_plane_alpha_blend.c | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/tests/kms_plane_alpha_blend.c
>>>> b/tests/kms_plane_alpha_blend.c
>>>> index d649a09f..864e83f9 100644
>>>> --- a/tests/kms_plane_alpha_blend.c
>>>> +++ b/tests/kms_plane_alpha_blend.c
>>>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
>>>> igt_output_t *output, enum pipe pipe)
>>>> w = mode->hdisplay;
>>>> h = mode->vdisplay;
>>>> + w = ALIGN(w, 256);
>>
>> This doesn't cause anything to align with 256 bytes. This makes fb
>> width in pixels divisible by 256. For anything to do with fb
>> alignments..this has very little to do. Kernel will do viewport
>> clipping hence for actual intended test this does nothing. FB
>> alignments are handled otherwise as in this case with with linear fb
>> will have 64 bytes per stride.
>>
>>>> /* recreate all fbs if incompatible */
>>>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
>>>> cairo_t *cr;
>>>>
>>>
>>
>> If this patch actually fixed anything you'll need to create hw wa and
>> this need to be fixed in kernel. Not testing is not fixing. Imo there
>> should be no problem for Intel hw to show varying fb sizes, including
>> 1366 wide.
>>
>> /Juha-Pekka
>
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-02 13:04 ` Sharma, Swati2
2021-08-02 14:16 ` Juha-Pekka Heikkila
@ 2021-08-02 14:16 ` Surendrakumar Upadhyay, TejaskumarX
2021-08-02 14:41 ` Juha-Pekka Heikkila
2021-08-02 19:19 ` Juha-Pekka Heikkilä
1 sibling, 2 replies; 20+ messages in thread
From: Surendrakumar Upadhyay, TejaskumarX @ 2021-08-02 14:16 UTC (permalink / raw)
To: Sharma, Swati2, juhapekka.heikkila, igt-dev
Hi JP,
You are right i915 driver is giving 64B aligned buffer but test uses raw width and thus it requires width to be aligned.
Thanks,
Tejas
> -----Original Message-----
> From: Sharma, Swati2 <swati2.sharma@intel.com>
> Sent: 02 August 2021 18:35
> To: juhapekka.heikkila@gmail.com; Surendrakumar Upadhyay, TejaskumarX
> <tejaskumarx.surendrakumar.upadhyay@intel.com>; igt-
> dev@lists.freedesktop.org
> Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to
> 256B
>
> Hi JP,
>
> Tejas reapplied the same fix as in
> https://patchwork.freedesktop.org/patch/445010/?series=92751&rev=2
> which was reviewed by Daniel.
>
> On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
> > Hi Tejas, Swati,
> >
> > I was confused when I read this patch, mind you tell what happen here?
> > To me it look like nothing matches with each other with the patch.
> >
> > Even subject is telling other things than what this patch actually does.
> >
> > On 30.7.2021 8.50, Sharma, Swati2 wrote:
> >> Reviewed-by:
> >> Swati Sharma <swati2.sharma@intel.com>
> >>
> >> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
> >>> some display resolutions like 1366x768 6bpc which does not have 64B
> >>> aligned width are creating crc mismatch in kms_plane_alpha_blend
> >>> test on Intel platforms.
> >
> > hm. You are saying none of Intel hw is able to show 1366 wide
> > framebuffers correctly? And it is fixed by hiding it from being tested?
> >
> > Memory given from kernel will have 64B alignment. You can easily see
> > by yourself.
> >
> >>>
> >>> Also having different alignment requirement by different drivers,
> >>> 256B aligned width should work for all drm drivers.
> >
> > You are saying you are fixing some problem with Intel hw, what does
> > all this other stuff have to do with it? None of those other drivers
> > are able to show 1366 pixels wide framebuffers either?
> >
> >>>
> >>> amdgpu and radeon, amdgpu_align_pitch: 256B armada, armada_pitch:
> >>> 128B
> >>> exynos_drm_gem_dumb_create: No alignment required
> >>> drm_gem_shmem_dumb_create: 8B
> >>> drm_gem_vram_fill_create_dumb: 8B
> >>>
> >>> Thus 256B covers everything we see in the kernel drm drivers.
> >>> Signed-off-by: Tejas Upadhyay
> >>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> >>> ---
> >>> tests/kms_plane_alpha_blend.c | 1 +
> >>> 1 file changed, 1 insertion(+)
> >>>
> >>> diff --git a/tests/kms_plane_alpha_blend.c
> >>> b/tests/kms_plane_alpha_blend.c index d649a09f..864e83f9 100644
> >>> --- a/tests/kms_plane_alpha_blend.c
> >>> +++ b/tests/kms_plane_alpha_blend.c
> >>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
> >>> igt_output_t *output, enum pipe pipe)
> >>> w = mode->hdisplay;
> >>> h = mode->vdisplay;
> >>> + w = ALIGN(w, 256);
> >
> > This doesn't cause anything to align with 256 bytes. This makes fb
> > width in pixels divisible by 256. For anything to do with fb
> > alignments..this has very little to do. Kernel will do viewport
> > clipping hence for actual intended test this does nothing. FB
> > alignments are handled otherwise as in this case with with linear fb will
> have 64 bytes per stride.
> >
> >>> /* recreate all fbs if incompatible */
> >>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
> >>> cairo_t *cr;
> >>>
> >>
> >
> > If this patch actually fixed anything you'll need to create hw wa and
> > this need to be fixed in kernel. Not testing is not fixing. Imo there
> > should be no problem for Intel hw to show varying fb sizes, including
> > 1366 wide.
> >
> > /Juha-Pekka
>
> --
> ~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-02 14:16 ` Surendrakumar Upadhyay, TejaskumarX
@ 2021-08-02 14:41 ` Juha-Pekka Heikkila
2021-08-02 19:19 ` Juha-Pekka Heikkilä
1 sibling, 0 replies; 20+ messages in thread
From: Juha-Pekka Heikkila @ 2021-08-02 14:41 UTC (permalink / raw)
To: Surendrakumar Upadhyay, TejaskumarX, Sharma, Swati2, igt-dev
On 2.8.2021 17.16, Surendrakumar Upadhyay, TejaskumarX wrote:
> Hi JP,
>
> You are right i915 driver is giving 64B aligned buffer but test uses raw width and thus it requires width to be aligned.
I don't understand what you mean with raw width? This is in use:
mode = igt_output_get_mode(output);
w = mode->hdisplay;
I see on kms_plane_alpha_blend is allocated framebuffer using normal igt
functions like igt_create_fb(..) and then renders onto them with cairo,
just like any other kms test. igt_create_fb(..) will create fb for you
which is all correct, it get alignments from calc_plane_stride(..) which
in this case will say stride alignment is 64 bytes since linear fb is in
use. If these are wrong you will start to see all kms tests fail equally.
/Juha-Pekka
>
> Thanks,
> Tejas
>
>> -----Original Message-----
>> From: Sharma, Swati2 <swati2.sharma@intel.com>
>> Sent: 02 August 2021 18:35
>> To: juhapekka.heikkila@gmail.com; Surendrakumar Upadhyay, TejaskumarX
>> <tejaskumarx.surendrakumar.upadhyay@intel.com>; igt-
>> dev@lists.freedesktop.org
>> Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to
>> 256B
>>
>> Hi JP,
>>
>> Tejas reapplied the same fix as in
>> https://patchwork.freedesktop.org/patch/445010/?series=92751&rev=2
>> which was reviewed by Daniel.
>>
>> On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
>>> Hi Tejas, Swati,
>>>
>>> I was confused when I read this patch, mind you tell what happen here?
>>> To me it look like nothing matches with each other with the patch.
>>>
>>> Even subject is telling other things than what this patch actually does.
>>>
>>> On 30.7.2021 8.50, Sharma, Swati2 wrote:
>>>> Reviewed-by:
>>>> Swati Sharma <swati2.sharma@intel.com>
>>>>
>>>> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
>>>>> some display resolutions like 1366x768 6bpc which does not have 64B
>>>>> aligned width are creating crc mismatch in kms_plane_alpha_blend
>>>>> test on Intel platforms.
>>>
>>> hm. You are saying none of Intel hw is able to show 1366 wide
>>> framebuffers correctly? And it is fixed by hiding it from being tested?
>>>
>>> Memory given from kernel will have 64B alignment. You can easily see
>>> by yourself.
>>>
>>>>>
>>>>> Also having different alignment requirement by different drivers,
>>>>> 256B aligned width should work for all drm drivers.
>>>
>>> You are saying you are fixing some problem with Intel hw, what does
>>> all this other stuff have to do with it? None of those other drivers
>>> are able to show 1366 pixels wide framebuffers either?
>>>
>>>>>
>>>>> amdgpu and radeon, amdgpu_align_pitch: 256B armada, armada_pitch:
>>>>> 128B
>>>>> exynos_drm_gem_dumb_create: No alignment required
>>>>> drm_gem_shmem_dumb_create: 8B
>>>>> drm_gem_vram_fill_create_dumb: 8B
>>>>>
>>>>> Thus 256B covers everything we see in the kernel drm drivers.
>>>>> Signed-off-by: Tejas Upadhyay
>>>>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
>>>>> ---
>>>>> tests/kms_plane_alpha_blend.c | 1 +
>>>>> 1 file changed, 1 insertion(+)
>>>>>
>>>>> diff --git a/tests/kms_plane_alpha_blend.c
>>>>> b/tests/kms_plane_alpha_blend.c index d649a09f..864e83f9 100644
>>>>> --- a/tests/kms_plane_alpha_blend.c
>>>>> +++ b/tests/kms_plane_alpha_blend.c
>>>>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
>>>>> igt_output_t *output, enum pipe pipe)
>>>>> w = mode->hdisplay;
>>>>> h = mode->vdisplay;
>>>>> + w = ALIGN(w, 256);
>>>
>>> This doesn't cause anything to align with 256 bytes. This makes fb
>>> width in pixels divisible by 256. For anything to do with fb
>>> alignments..this has very little to do. Kernel will do viewport
>>> clipping hence for actual intended test this does nothing. FB
>>> alignments are handled otherwise as in this case with with linear fb will
>> have 64 bytes per stride.
>>>
>>>>> /* recreate all fbs if incompatible */
>>>>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
>>>>> cairo_t *cr;
>>>>>
>>>>
>>>
>>> If this patch actually fixed anything you'll need to create hw wa and
>>> this need to be fixed in kernel. Not testing is not fixing. Imo there
>>> should be no problem for Intel hw to show varying fb sizes, including
>>> 1366 wide.
>>>
>>> /Juha-Pekka
>>
>> --
>> ~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-02 14:16 ` Surendrakumar Upadhyay, TejaskumarX
2021-08-02 14:41 ` Juha-Pekka Heikkila
@ 2021-08-02 19:19 ` Juha-Pekka Heikkilä
2021-08-03 4:55 ` Surendrakumar Upadhyay, TejaskumarX
2021-08-03 16:16 ` Srinivas, Vidya
1 sibling, 2 replies; 20+ messages in thread
From: Juha-Pekka Heikkilä @ 2021-08-02 19:19 UTC (permalink / raw)
To: Surendrakumar Upadhyay, TejaskumarX; +Cc: Sharma, Swati2, igt-dev
On Mon, Aug 2, 2021 at 5:16 PM Surendrakumar Upadhyay, TejaskumarX
<tejaskumarx.surendrakumar.upadhyay@intel.com> wrote:
>
> Hi JP,
>
> You are right i915 driver is giving 64B aligned buffer but test uses raw width and thus it requires width to be aligned.
Can you try this on the device which is failing:
https://patchwork.freedesktop.org/series/93317/
It will put on pixel blend and alpha and try different width linear fbs
and compare results with crc. This should tell if alignments somehow can
affect the crc on your test machine. On my ICL everything work as expected.
/Juha-Pekka
>
> Thanks,
> Tejas
>
> > -----Original Message-----
> > From: Sharma, Swati2 <swati2.sharma@intel.com>
> > Sent: 02 August 2021 18:35
> > To: juhapekka.heikkila@gmail.com; Surendrakumar Upadhyay, TejaskumarX
> > <tejaskumarx.surendrakumar.upadhyay@intel.com>; igt-
> > dev@lists.freedesktop.org
> > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to
> > 256B
> >
> > Hi JP,
> >
> > Tejas reapplied the same fix as in
> > https://patchwork.freedesktop.org/patch/445010/?series=92751&rev=2
> > which was reviewed by Daniel.
> >
> > On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
> > > Hi Tejas, Swati,
> > >
> > > I was confused when I read this patch, mind you tell what happen here?
> > > To me it look like nothing matches with each other with the patch.
> > >
> > > Even subject is telling other things than what this patch actually does.
> > >
> > > On 30.7.2021 8.50, Sharma, Swati2 wrote:
> > >> Reviewed-by:
> > >> Swati Sharma <swati2.sharma@intel.com>
> > >>
> > >> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
> > >>> some display resolutions like 1366x768 6bpc which does not have 64B
> > >>> aligned width are creating crc mismatch in kms_plane_alpha_blend
> > >>> test on Intel platforms.
> > >
> > > hm. You are saying none of Intel hw is able to show 1366 wide
> > > framebuffers correctly? And it is fixed by hiding it from being tested?
> > >
> > > Memory given from kernel will have 64B alignment. You can easily see
> > > by yourself.
> > >
> > >>>
> > >>> Also having different alignment requirement by different drivers,
> > >>> 256B aligned width should work for all drm drivers.
> > >
> > > You are saying you are fixing some problem with Intel hw, what does
> > > all this other stuff have to do with it? None of those other drivers
> > > are able to show 1366 pixels wide framebuffers either?
> > >
> > >>>
> > >>> amdgpu and radeon, amdgpu_align_pitch: 256B armada, armada_pitch:
> > >>> 128B
> > >>> exynos_drm_gem_dumb_create: No alignment required
> > >>> drm_gem_shmem_dumb_create: 8B
> > >>> drm_gem_vram_fill_create_dumb: 8B
> > >>>
> > >>> Thus 256B covers everything we see in the kernel drm drivers.
> > >>> Signed-off-by: Tejas Upadhyay
> > >>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > >>> ---
> > >>> tests/kms_plane_alpha_blend.c | 1 +
> > >>> 1 file changed, 1 insertion(+)
> > >>>
> > >>> diff --git a/tests/kms_plane_alpha_blend.c
> > >>> b/tests/kms_plane_alpha_blend.c index d649a09f..864e83f9 100644
> > >>> --- a/tests/kms_plane_alpha_blend.c
> > >>> +++ b/tests/kms_plane_alpha_blend.c
> > >>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
> > >>> igt_output_t *output, enum pipe pipe)
> > >>> w = mode->hdisplay;
> > >>> h = mode->vdisplay;
> > >>> + w = ALIGN(w, 256);
> > >
> > > This doesn't cause anything to align with 256 bytes. This makes fb
> > > width in pixels divisible by 256. For anything to do with fb
> > > alignments..this has very little to do. Kernel will do viewport
> > > clipping hence for actual intended test this does nothing. FB
> > > alignments are handled otherwise as in this case with with linear fb will
> > have 64 bytes per stride.
> > >
> > >>> /* recreate all fbs if incompatible */
> > >>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
> > >>> cairo_t *cr;
> > >>>
> > >>
> > >
> > > If this patch actually fixed anything you'll need to create hw wa and
> > > this need to be fixed in kernel. Not testing is not fixing. Imo there
> > > should be no problem for Intel hw to show varying fb sizes, including
> > > 1366 wide.
> > >
> > > /Juha-Pekka
> >
> > --
> > ~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-02 19:19 ` Juha-Pekka Heikkilä
@ 2021-08-03 4:55 ` Surendrakumar Upadhyay, TejaskumarX
2021-08-03 9:29 ` Juha-Pekka Heikkilä
2021-08-03 16:16 ` Srinivas, Vidya
1 sibling, 1 reply; 20+ messages in thread
From: Surendrakumar Upadhyay, TejaskumarX @ 2021-08-03 4:55 UTC (permalink / raw)
To: Juha-Pekka Heikkilä; +Cc: Sharma, Swati2, igt-dev
Use 1366x768 panel and you should be able to reproduce. I don’t have that panel with me right now. I will check once I get it.
Thanks,
Tejas
> -----Original Message-----
> From: Juha-Pekka Heikkilä <juhapekka.heikkila@gmail.com>
> Sent: 03 August 2021 00:49
> To: Surendrakumar Upadhyay, TejaskumarX
> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> Cc: Sharma, Swati2 <swati2.sharma@intel.com>; igt-
> dev@lists.freedesktop.org
> Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to
> 256B
>
> On Mon, Aug 2, 2021 at 5:16 PM Surendrakumar Upadhyay, TejaskumarX
> <tejaskumarx.surendrakumar.upadhyay@intel.com> wrote:
> >
> > Hi JP,
> >
> > You are right i915 driver is giving 64B aligned buffer but test uses raw width
> and thus it requires width to be aligned.
>
> Can you try this on the device which is failing:
> https://patchwork.freedesktop.org/series/93317/
>
> It will put on pixel blend and alpha and try different width linear fbs and
> compare results with crc. This should tell if alignments somehow can affect
> the crc on your test machine. On my ICL everything work as expected.
>
> /Juha-Pekka
>
> >
> > Thanks,
> > Tejas
> >
> > > -----Original Message-----
> > > From: Sharma, Swati2 <swati2.sharma@intel.com>
> > > Sent: 02 August 2021 18:35
> > > To: juhapekka.heikkila@gmail.com; Surendrakumar Upadhyay,
> > > TejaskumarX <tejaskumarx.surendrakumar.upadhyay@intel.com>; igt-
> > > dev@lists.freedesktop.org
> > > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align
> > > width to 256B
> > >
> > > Hi JP,
> > >
> > > Tejas reapplied the same fix as in
> > > https://patchwork.freedesktop.org/patch/445010/?series=92751&rev=2
> > > which was reviewed by Daniel.
> > >
> > > On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
> > > > Hi Tejas, Swati,
> > > >
> > > > I was confused when I read this patch, mind you tell what happen here?
> > > > To me it look like nothing matches with each other with the patch.
> > > >
> > > > Even subject is telling other things than what this patch actually does.
> > > >
> > > > On 30.7.2021 8.50, Sharma, Swati2 wrote:
> > > >> Reviewed-by:
> > > >> Swati Sharma <swati2.sharma@intel.com>
> > > >>
> > > >> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
> > > >>> some display resolutions like 1366x768 6bpc which does not have
> > > >>> 64B aligned width are creating crc mismatch in
> > > >>> kms_plane_alpha_blend test on Intel platforms.
> > > >
> > > > hm. You are saying none of Intel hw is able to show 1366 wide
> > > > framebuffers correctly? And it is fixed by hiding it from being tested?
> > > >
> > > > Memory given from kernel will have 64B alignment. You can easily
> > > > see by yourself.
> > > >
> > > >>>
> > > >>> Also having different alignment requirement by different
> > > >>> drivers, 256B aligned width should work for all drm drivers.
> > > >
> > > > You are saying you are fixing some problem with Intel hw, what
> > > > does all this other stuff have to do with it? None of those other
> > > > drivers are able to show 1366 pixels wide framebuffers either?
> > > >
> > > >>>
> > > >>> amdgpu and radeon, amdgpu_align_pitch: 256B armada,
> armada_pitch:
> > > >>> 128B
> > > >>> exynos_drm_gem_dumb_create: No alignment required
> > > >>> drm_gem_shmem_dumb_create: 8B
> > > >>> drm_gem_vram_fill_create_dumb: 8B
> > > >>>
> > > >>> Thus 256B covers everything we see in the kernel drm drivers.
> > > >>> Signed-off-by: Tejas Upadhyay
> > > >>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > > >>> ---
> > > >>> tests/kms_plane_alpha_blend.c | 1 +
> > > >>> 1 file changed, 1 insertion(+)
> > > >>>
> > > >>> diff --git a/tests/kms_plane_alpha_blend.c
> > > >>> b/tests/kms_plane_alpha_blend.c index d649a09f..864e83f9 100644
> > > >>> --- a/tests/kms_plane_alpha_blend.c
> > > >>> +++ b/tests/kms_plane_alpha_blend.c
> > > >>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
> > > >>> igt_output_t *output, enum pipe pipe)
> > > >>> w = mode->hdisplay;
> > > >>> h = mode->vdisplay;
> > > >>> + w = ALIGN(w, 256);
> > > >
> > > > This doesn't cause anything to align with 256 bytes. This makes fb
> > > > width in pixels divisible by 256. For anything to do with fb
> > > > alignments..this has very little to do. Kernel will do viewport
> > > > clipping hence for actual intended test this does nothing. FB
> > > > alignments are handled otherwise as in this case with with linear
> > > > fb will
> > > have 64 bytes per stride.
> > > >
> > > >>> /* recreate all fbs if incompatible */
> > > >>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
> > > >>> cairo_t *cr;
> > > >>>
> > > >>
> > > >
> > > > If this patch actually fixed anything you'll need to create hw wa
> > > > and this need to be fixed in kernel. Not testing is not fixing.
> > > > Imo there should be no problem for Intel hw to show varying fb
> > > > sizes, including
> > > > 1366 wide.
> > > >
> > > > /Juha-Pekka
> > >
> > > --
> > > ~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-03 4:55 ` Surendrakumar Upadhyay, TejaskumarX
@ 2021-08-03 9:29 ` Juha-Pekka Heikkilä
0 siblings, 0 replies; 20+ messages in thread
From: Juha-Pekka Heikkilä @ 2021-08-03 9:29 UTC (permalink / raw)
To: Surendrakumar Upadhyay, TejaskumarX; +Cc: Sharma, Swati2, igt-dev
On Tue, Aug 3, 2021 at 7:55 AM Surendrakumar Upadhyay, TejaskumarX
<tejaskumarx.surendrakumar.upadhyay@intel.com> wrote:
>
> Use 1366x768 panel and you should be able to reproduce. I don’t have that panel with me right now. I will check once I get it.
Setting fb size to 1366x768 does not reproduce this issue on my icl. I
don't have such panel nor could I swap such into my lenovo in any
case.
For testing purpose you could try take out your change from
kms_plane_alpha_blend and change all used modifiers to something
different than linear, ie. x or y tile. With different tiling
everything will be different on both sw and hw level while still
testing same hw alpha blending feature.
/Juha-Pekka
>
> Thanks,
> Tejas
>
> > -----Original Message-----
> > From: Juha-Pekka Heikkilä <juhapekka.heikkila@gmail.com>
> > Sent: 03 August 2021 00:49
> > To: Surendrakumar Upadhyay, TejaskumarX
> > <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > Cc: Sharma, Swati2 <swati2.sharma@intel.com>; igt-
> > dev@lists.freedesktop.org
> > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to
> > 256B
> >
> > On Mon, Aug 2, 2021 at 5:16 PM Surendrakumar Upadhyay, TejaskumarX
> > <tejaskumarx.surendrakumar.upadhyay@intel.com> wrote:
> > >
> > > Hi JP,
> > >
> > > You are right i915 driver is giving 64B aligned buffer but test uses raw width
> > and thus it requires width to be aligned.
> >
> > Can you try this on the device which is failing:
> > https://patchwork.freedesktop.org/series/93317/
> >
> > It will put on pixel blend and alpha and try different width linear fbs and
> > compare results with crc. This should tell if alignments somehow can affect
> > the crc on your test machine. On my ICL everything work as expected.
> >
> > /Juha-Pekka
> >
> > >
> > > Thanks,
> > > Tejas
> > >
> > > > -----Original Message-----
> > > > From: Sharma, Swati2 <swati2.sharma@intel.com>
> > > > Sent: 02 August 2021 18:35
> > > > To: juhapekka.heikkila@gmail.com; Surendrakumar Upadhyay,
> > > > TejaskumarX <tejaskumarx.surendrakumar.upadhyay@intel.com>; igt-
> > > > dev@lists.freedesktop.org
> > > > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align
> > > > width to 256B
> > > >
> > > > Hi JP,
> > > >
> > > > Tejas reapplied the same fix as in
> > > > https://patchwork.freedesktop.org/patch/445010/?series=92751&rev=2
> > > > which was reviewed by Daniel.
> > > >
> > > > On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
> > > > > Hi Tejas, Swati,
> > > > >
> > > > > I was confused when I read this patch, mind you tell what happen here?
> > > > > To me it look like nothing matches with each other with the patch.
> > > > >
> > > > > Even subject is telling other things than what this patch actually does.
> > > > >
> > > > > On 30.7.2021 8.50, Sharma, Swati2 wrote:
> > > > >> Reviewed-by:
> > > > >> Swati Sharma <swati2.sharma@intel.com>
> > > > >>
> > > > >> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
> > > > >>> some display resolutions like 1366x768 6bpc which does not have
> > > > >>> 64B aligned width are creating crc mismatch in
> > > > >>> kms_plane_alpha_blend test on Intel platforms.
> > > > >
> > > > > hm. You are saying none of Intel hw is able to show 1366 wide
> > > > > framebuffers correctly? And it is fixed by hiding it from being tested?
> > > > >
> > > > > Memory given from kernel will have 64B alignment. You can easily
> > > > > see by yourself.
> > > > >
> > > > >>>
> > > > >>> Also having different alignment requirement by different
> > > > >>> drivers, 256B aligned width should work for all drm drivers.
> > > > >
> > > > > You are saying you are fixing some problem with Intel hw, what
> > > > > does all this other stuff have to do with it? None of those other
> > > > > drivers are able to show 1366 pixels wide framebuffers either?
> > > > >
> > > > >>>
> > > > >>> amdgpu and radeon, amdgpu_align_pitch: 256B armada,
> > armada_pitch:
> > > > >>> 128B
> > > > >>> exynos_drm_gem_dumb_create: No alignment required
> > > > >>> drm_gem_shmem_dumb_create: 8B
> > > > >>> drm_gem_vram_fill_create_dumb: 8B
> > > > >>>
> > > > >>> Thus 256B covers everything we see in the kernel drm drivers.
> > > > >>> Signed-off-by: Tejas Upadhyay
> > > > >>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > > > >>> ---
> > > > >>> tests/kms_plane_alpha_blend.c | 1 +
> > > > >>> 1 file changed, 1 insertion(+)
> > > > >>>
> > > > >>> diff --git a/tests/kms_plane_alpha_blend.c
> > > > >>> b/tests/kms_plane_alpha_blend.c index d649a09f..864e83f9 100644
> > > > >>> --- a/tests/kms_plane_alpha_blend.c
> > > > >>> +++ b/tests/kms_plane_alpha_blend.c
> > > > >>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
> > > > >>> igt_output_t *output, enum pipe pipe)
> > > > >>> w = mode->hdisplay;
> > > > >>> h = mode->vdisplay;
> > > > >>> + w = ALIGN(w, 256);
> > > > >
> > > > > This doesn't cause anything to align with 256 bytes. This makes fb
> > > > > width in pixels divisible by 256. For anything to do with fb
> > > > > alignments..this has very little to do. Kernel will do viewport
> > > > > clipping hence for actual intended test this does nothing. FB
> > > > > alignments are handled otherwise as in this case with with linear
> > > > > fb will
> > > > have 64 bytes per stride.
> > > > >
> > > > >>> /* recreate all fbs if incompatible */
> > > > >>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
> > > > >>> cairo_t *cr;
> > > > >>>
> > > > >>
> > > > >
> > > > > If this patch actually fixed anything you'll need to create hw wa
> > > > > and this need to be fixed in kernel. Not testing is not fixing.
> > > > > Imo there should be no problem for Intel hw to show varying fb
> > > > > sizes, including
> > > > > 1366 wide.
> > > > >
> > > > > /Juha-Pekka
> > > >
> > > > --
> > > > ~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-02 19:19 ` Juha-Pekka Heikkilä
2021-08-03 4:55 ` Surendrakumar Upadhyay, TejaskumarX
@ 2021-08-03 16:16 ` Srinivas, Vidya
2021-08-03 17:49 ` Juha-Pekka Heikkilä
1 sibling, 1 reply; 20+ messages in thread
From: Srinivas, Vidya @ 2021-08-03 16:16 UTC (permalink / raw)
To: Juha-Pekka Heikkilä, Surendrakumar Upadhyay, TejaskumarX
Cc: Sharma, Swati2, igt-dev
> -----Original Message-----
> From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of Juha-
> Pekka Heikkilä
> Sent: Tuesday, August 3, 2021 12:49 AM
> To: Surendrakumar Upadhyay, TejaskumarX
> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> Cc: Sharma, Swati2 <swati2.sharma@intel.com>; igt-
> dev@lists.freedesktop.org
> Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to
> 256B
>
> On Mon, Aug 2, 2021 at 5:16 PM Surendrakumar Upadhyay, TejaskumarX
> <tejaskumarx.surendrakumar.upadhyay@intel.com> wrote:
> >
> > Hi JP,
> >
> > You are right i915 driver is giving 64B aligned buffer but test uses raw width
> and thus it requires width to be aligned.
>
> Can you try this on the device which is failing:
> https://patchwork.freedesktop.org/series/93317/
>
> It will put on pixel blend and alpha and try different width linear fbs and
> compare results with crc. This should tell if alignments somehow can affect
> the crc on your test machine. On my ICL everything work as expected.
>
Hi Juha-Pekka
With your https://patchwork.freedesktop.org/series/93317/ the test PASSES.
But we need to use both planes and exact same sequence as kms_plane_alpha_blend coverage-premultiplied-constant case
to reproduce the issue.
But with this modification (same as kms_plane_alpha_blend) done here https://patchwork.freedesktop.org/patch/448369/?series=93317&rev=3
It PASS with ALIGN in draw_squares and draw_squares_coverage but fails without the ALIGNMENT.
Kindly have a check. Thank you. Apologies, I pushed rev3 on top of yours to try-bot to maintain context.
Regards
Vidya
> /Juha-Pekka
>
> >
> > Thanks,
> > Tejas
> >
> > > -----Original Message-----
> > > From: Sharma, Swati2 <swati2.sharma@intel.com>
> > > Sent: 02 August 2021 18:35
> > > To: juhapekka.heikkila@gmail.com; Surendrakumar Upadhyay,
> > > TejaskumarX <tejaskumarx.surendrakumar.upadhyay@intel.com>; igt-
> > > dev@lists.freedesktop.org
> > > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align
> > > width to 256B
> > >
> > > Hi JP,
> > >
> > > Tejas reapplied the same fix as in
> > > https://patchwork.freedesktop.org/patch/445010/?series=92751&rev=2
> > > which was reviewed by Daniel.
> > >
> > > On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
> > > > Hi Tejas, Swati,
> > > >
> > > > I was confused when I read this patch, mind you tell what happen here?
> > > > To me it look like nothing matches with each other with the patch.
> > > >
> > > > Even subject is telling other things than what this patch actually does.
> > > >
> > > > On 30.7.2021 8.50, Sharma, Swati2 wrote:
> > > >> Reviewed-by:
> > > >> Swati Sharma <swati2.sharma@intel.com>
> > > >>
> > > >> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
> > > >>> some display resolutions like 1366x768 6bpc which does not have
> > > >>> 64B aligned width are creating crc mismatch in
> > > >>> kms_plane_alpha_blend test on Intel platforms.
> > > >
> > > > hm. You are saying none of Intel hw is able to show 1366 wide
> > > > framebuffers correctly? And it is fixed by hiding it from being tested?
> > > >
> > > > Memory given from kernel will have 64B alignment. You can easily
> > > > see by yourself.
> > > >
> > > >>>
> > > >>> Also having different alignment requirement by different
> > > >>> drivers, 256B aligned width should work for all drm drivers.
> > > >
> > > > You are saying you are fixing some problem with Intel hw, what
> > > > does all this other stuff have to do with it? None of those other
> > > > drivers are able to show 1366 pixels wide framebuffers either?
> > > >
> > > >>>
> > > >>> amdgpu and radeon, amdgpu_align_pitch: 256B armada,
> armada_pitch:
> > > >>> 128B
> > > >>> exynos_drm_gem_dumb_create: No alignment required
> > > >>> drm_gem_shmem_dumb_create: 8B
> > > >>> drm_gem_vram_fill_create_dumb: 8B
> > > >>>
> > > >>> Thus 256B covers everything we see in the kernel drm drivers.
> > > >>> Signed-off-by: Tejas Upadhyay
> > > >>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > > >>> ---
> > > >>> tests/kms_plane_alpha_blend.c | 1 +
> > > >>> 1 file changed, 1 insertion(+)
> > > >>>
> > > >>> diff --git a/tests/kms_plane_alpha_blend.c
> > > >>> b/tests/kms_plane_alpha_blend.c index d649a09f..864e83f9 100644
> > > >>> --- a/tests/kms_plane_alpha_blend.c
> > > >>> +++ b/tests/kms_plane_alpha_blend.c
> > > >>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
> > > >>> igt_output_t *output, enum pipe pipe)
> > > >>> w = mode->hdisplay;
> > > >>> h = mode->vdisplay;
> > > >>> + w = ALIGN(w, 256);
> > > >
> > > > This doesn't cause anything to align with 256 bytes. This makes fb
> > > > width in pixels divisible by 256. For anything to do with fb
> > > > alignments..this has very little to do. Kernel will do viewport
> > > > clipping hence for actual intended test this does nothing. FB
> > > > alignments are handled otherwise as in this case with with linear
> > > > fb will
> > > have 64 bytes per stride.
> > > >
> > > >>> /* recreate all fbs if incompatible */
> > > >>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
> > > >>> cairo_t *cr;
> > > >>>
> > > >>
> > > >
> > > > If this patch actually fixed anything you'll need to create hw wa
> > > > and this need to be fixed in kernel. Not testing is not fixing.
> > > > Imo there should be no problem for Intel hw to show varying fb
> > > > sizes, including
> > > > 1366 wide.
> > > >
> > > > /Juha-Pekka
> > >
> > > --
> > > ~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-03 16:16 ` Srinivas, Vidya
@ 2021-08-03 17:49 ` Juha-Pekka Heikkilä
2021-08-04 3:11 ` Srinivas, Vidya
0 siblings, 1 reply; 20+ messages in thread
From: Juha-Pekka Heikkilä @ 2021-08-03 17:49 UTC (permalink / raw)
To: Srinivas, Vidya
Cc: Surendrakumar Upadhyay, TejaskumarX, Sharma, Swati2, igt-dev
On Tue, Aug 3, 2021 at 7:16 PM Srinivas, Vidya <vidya.srinivas@intel.com> wrote:
>
>
>
> > -----Original Message-----
> > From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of Juha-
> > Pekka Heikkilä
> > Sent: Tuesday, August 3, 2021 12:49 AM
> > To: Surendrakumar Upadhyay, TejaskumarX
> > <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > Cc: Sharma, Swati2 <swati2.sharma@intel.com>; igt-
> > dev@lists.freedesktop.org
> > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to
> > 256B
> >
> > On Mon, Aug 2, 2021 at 5:16 PM Surendrakumar Upadhyay, TejaskumarX
> > <tejaskumarx.surendrakumar.upadhyay@intel.com> wrote:
> > >
> > > Hi JP,
> > >
> > > You are right i915 driver is giving 64B aligned buffer but test uses raw width
> > and thus it requires width to be aligned.
> >
> > Can you try this on the device which is failing:
> > https://patchwork.freedesktop.org/series/93317/
> >
> > It will put on pixel blend and alpha and try different width linear fbs and
> > compare results with crc. This should tell if alignments somehow can affect
> > the crc on your test machine. On my ICL everything work as expected.
> >
>
> Hi Juha-Pekka
>
> With your https://patchwork.freedesktop.org/series/93317/ the test PASSES.
> But we need to use both planes and exact same sequence as kms_plane_alpha_blend coverage-premultiplied-constant case
> to reproduce the issue.
>
> But with this modification (same as kms_plane_alpha_blend) done here https://patchwork.freedesktop.org/patch/448369/?series=93317&rev=3
> It PASS with ALIGN in draw_squares and draw_squares_coverage but fails without the ALIGNMENT.
>
> Kindly have a check. Thank you. Apologies, I pushed rev3 on top of yours to try-bot to maintain context.
>
Hi Vidya,
thanks for showing this. Your change should segfault because with your
alignment that memory drawing function will draw past reserved memory
but that's not the interesting part. That original bug was included on
the cut'n'pasted lines, it has nothing to do with strides but just
simple rounding issue.
Where there's this function:
+static void draw_squares(struct igt_fb *fb, int w, int h, double a)
+{
+ cairo_t *cr = igt_get_cairo_ctx(fb->fd, fb);
+
+ cairo_set_operator(cr, CAIRO_OPERATOR_SOURCE);
+ igt_paint_color_alpha(cr, 0, 0, w / 2, h / 2, 1., 0., 0., a);
+ igt_paint_color_alpha(cr, w / 2, 0, w / 2, h / 2, 0., 1., 0., a);
+ igt_paint_color_alpha(cr, 0, h / 2, w / 2, h / 2, 0., 0., 1., a);
+ igt_paint_color_alpha(cr, w / 2, h / 2, w / 4, h / 2, 1., 1., 1., a);
+ igt_paint_color_alpha(cr, 3 * w / 4, h / 2, w / 4, h / 2, 0., 0., 0., a);
+
+ igt_put_cairo_ctx(cr);
+}
That last igt_paint_color_alpha(..) will need to say:
igt_paint_color_alpha(cr, w * 3 / 4, h / 2, w - (w * 3 / 4), h / 2,
0., 0., 0., a);
Otherwise it can draw one pixel too narrow box.
/Juha-Pekka
> >
> > >
> > > Thanks,
> > > Tejas
> > >
> > > > -----Original Message-----
> > > > From: Sharma, Swati2 <swati2.sharma@intel.com>
> > > > Sent: 02 August 2021 18:35
> > > > To: juhapekka.heikkila@gmail.com; Surendrakumar Upadhyay,
> > > > TejaskumarX <tejaskumarx.surendrakumar.upadhyay@intel.com>; igt-
> > > > dev@lists.freedesktop.org
> > > > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align
> > > > width to 256B
> > > >
> > > > Hi JP,
> > > >
> > > > Tejas reapplied the same fix as in
> > > > https://patchwork.freedesktop.org/patch/445010/?series=92751&rev=2
> > > > which was reviewed by Daniel.
> > > >
> > > > On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
> > > > > Hi Tejas, Swati,
> > > > >
> > > > > I was confused when I read this patch, mind you tell what happen here?
> > > > > To me it look like nothing matches with each other with the patch.
> > > > >
> > > > > Even subject is telling other things than what this patch actually does.
> > > > >
> > > > > On 30.7.2021 8.50, Sharma, Swati2 wrote:
> > > > >> Reviewed-by:
> > > > >> Swati Sharma <swati2.sharma@intel.com>
> > > > >>
> > > > >> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
> > > > >>> some display resolutions like 1366x768 6bpc which does not have
> > > > >>> 64B aligned width are creating crc mismatch in
> > > > >>> kms_plane_alpha_blend test on Intel platforms.
> > > > >
> > > > > hm. You are saying none of Intel hw is able to show 1366 wide
> > > > > framebuffers correctly? And it is fixed by hiding it from being tested?
> > > > >
> > > > > Memory given from kernel will have 64B alignment. You can easily
> > > > > see by yourself.
> > > > >
> > > > >>>
> > > > >>> Also having different alignment requirement by different
> > > > >>> drivers, 256B aligned width should work for all drm drivers.
> > > > >
> > > > > You are saying you are fixing some problem with Intel hw, what
> > > > > does all this other stuff have to do with it? None of those other
> > > > > drivers are able to show 1366 pixels wide framebuffers either?
> > > > >
> > > > >>>
> > > > >>> amdgpu and radeon, amdgpu_align_pitch: 256B armada,
> > armada_pitch:
> > > > >>> 128B
> > > > >>> exynos_drm_gem_dumb_create: No alignment required
> > > > >>> drm_gem_shmem_dumb_create: 8B
> > > > >>> drm_gem_vram_fill_create_dumb: 8B
> > > > >>>
> > > > >>> Thus 256B covers everything we see in the kernel drm drivers.
> > > > >>> Signed-off-by: Tejas Upadhyay
> > > > >>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > > > >>> ---
> > > > >>> tests/kms_plane_alpha_blend.c | 1 +
> > > > >>> 1 file changed, 1 insertion(+)
> > > > >>>
> > > > >>> diff --git a/tests/kms_plane_alpha_blend.c
> > > > >>> b/tests/kms_plane_alpha_blend.c index d649a09f..864e83f9 100644
> > > > >>> --- a/tests/kms_plane_alpha_blend.c
> > > > >>> +++ b/tests/kms_plane_alpha_blend.c
> > > > >>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
> > > > >>> igt_output_t *output, enum pipe pipe)
> > > > >>> w = mode->hdisplay;
> > > > >>> h = mode->vdisplay;
> > > > >>> + w = ALIGN(w, 256);
> > > > >
> > > > > This doesn't cause anything to align with 256 bytes. This makes fb
> > > > > width in pixels divisible by 256. For anything to do with fb
> > > > > alignments..this has very little to do. Kernel will do viewport
> > > > > clipping hence for actual intended test this does nothing. FB
> > > > > alignments are handled otherwise as in this case with with linear
> > > > > fb will
> > > > have 64 bytes per stride.
> > > > >
> > > > >>> /* recreate all fbs if incompatible */
> > > > >>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
> > > > >>> cairo_t *cr;
> > > > >>>
> > > > >>
> > > > >
> > > > > If this patch actually fixed anything you'll need to create hw wa
> > > > > and this need to be fixed in kernel. Not testing is not fixing.
> > > > > Imo there should be no problem for Intel hw to show varying fb
> > > > > sizes, including
> > > > > 1366 wide.
> > > > >
> > > > > /Juha-Pekka
> > > >
> > > > --
> > > > ~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-03 17:49 ` Juha-Pekka Heikkilä
@ 2021-08-04 3:11 ` Srinivas, Vidya
2021-08-04 4:20 ` Surendrakumar Upadhyay, TejaskumarX
0 siblings, 1 reply; 20+ messages in thread
From: Srinivas, Vidya @ 2021-08-04 3:11 UTC (permalink / raw)
To: Juha-Pekka Heikkilä, Surendrakumar Upadhyay, TejaskumarX
Cc: Sharma, Swati2, igt-dev
> -----Original Message-----
> From: Juha-Pekka Heikkilä <juhapekka.heikkila@gmail.com>
> Sent: Tuesday, August 3, 2021 11:19 PM
> To: Srinivas, Vidya <vidya.srinivas@intel.com>
> Cc: Surendrakumar Upadhyay, TejaskumarX
> <tejaskumarx.surendrakumar.upadhyay@intel.com>; Sharma, Swati2
> <swati2.sharma@intel.com>; igt-dev@lists.freedesktop.org
> Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to
> 256B
>
> On Tue, Aug 3, 2021 at 7:16 PM Srinivas, Vidya <vidya.srinivas@intel.com>
> wrote:
> >
> >
> >
> > > -----Original Message-----
> > > From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of
> > > Juha- Pekka Heikkilä
> > > Sent: Tuesday, August 3, 2021 12:49 AM
> > > To: Surendrakumar Upadhyay, TejaskumarX
> > > <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > > Cc: Sharma, Swati2 <swati2.sharma@intel.com>; igt-
> > > dev@lists.freedesktop.org
> > > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align
> > > width to 256B
> > >
> > > On Mon, Aug 2, 2021 at 5:16 PM Surendrakumar Upadhyay, TejaskumarX
> > > <tejaskumarx.surendrakumar.upadhyay@intel.com> wrote:
> > > >
> > > > Hi JP,
> > > >
> > > > You are right i915 driver is giving 64B aligned buffer but test
> > > > uses raw width
> > > and thus it requires width to be aligned.
> > >
> > > Can you try this on the device which is failing:
> > > https://patchwork.freedesktop.org/series/93317/
> > >
> > > It will put on pixel blend and alpha and try different width linear
> > > fbs and compare results with crc. This should tell if alignments
> > > somehow can affect the crc on your test machine. On my ICL everything
> work as expected.
> > >
> >
> > Hi Juha-Pekka
> >
> > With your https://patchwork.freedesktop.org/series/93317/ the test
> PASSES.
> > But we need to use both planes and exact same sequence as
> > kms_plane_alpha_blend coverage-premultiplied-constant case to
> reproduce the issue.
> >
> > But with this modification (same as kms_plane_alpha_blend) done here
> > https://patchwork.freedesktop.org/patch/448369/?series=93317&rev=3
> > It PASS with ALIGN in draw_squares and draw_squares_coverage but fails
> without the ALIGNMENT.
> >
> > Kindly have a check. Thank you. Apologies, I pushed rev3 on top of yours to
> try-bot to maintain context.
> >
>
> Hi Vidya,
>
> thanks for showing this. Your change should segfault because with your
> alignment that memory drawing function will draw past reserved memory
> but that's not the interesting part. That original bug was included on the
> cut'n'pasted lines, it has nothing to do with strides but just simple rounding
> issue.
>
> Where there's this function:
>
> +static void draw_squares(struct igt_fb *fb, int w, int h, double a) {
> +cairo_t *cr = igt_get_cairo_ctx(fb->fd, fb);
> +
> + cairo_set_operator(cr, CAIRO_OPERATOR_SOURCE);
> + igt_paint_color_alpha(cr, 0, 0, w / 2, h / 2, 1., 0., 0., a);
> + igt_paint_color_alpha(cr, w / 2, 0, w / 2, h / 2, 0., 1., 0., a);
> + igt_paint_color_alpha(cr, 0, h / 2, w / 2, h / 2, 0., 0., 1., a);
> + igt_paint_color_alpha(cr, w / 2, h / 2, w / 4, h / 2, 1., 1., 1., a);
> + igt_paint_color_alpha(cr, 3 * w / 4, h / 2, w / 4, h / 2, 0., 0., 0.,
> + a);
> +
> + igt_put_cairo_ctx(cr);
> +}
>
>
> That last igt_paint_color_alpha(..) will need to say:
>
> igt_paint_color_alpha(cr, w * 3 / 4, h / 2, w - (w * 3 / 4), h / 2, 0., 0., 0., a);
>
> Otherwise it can draw one pixel too narrow box.
Hello Juha-Pekka,
Thank you so much. With this line change this test kms_stridetest_crc and the kms_plane_alpha_blend works too.
No alignment is needed. Sorry, somehow it did not give the CRASH.
This is the same issue I was seeking your help, where we tried multiple fixes.
Thank you so very much. I have submitted the fix you provided in your name
https://patchwork.freedesktop.org/patch/448556/?series=93370&rev=1
https://patchwork.freedesktop.org/series/93370/
@Surendrakumar Upadhyay, TejaskumarX Apologies, I have submitted the revert in the same series.
Thank you Tejas.
Can you kindly help review and merge the same?
Regards
Vidya
>
> /Juha-Pekka
>
> > >
> > > >
> > > > Thanks,
> > > > Tejas
> > > >
> > > > > -----Original Message-----
> > > > > From: Sharma, Swati2 <swati2.sharma@intel.com>
> > > > > Sent: 02 August 2021 18:35
> > > > > To: juhapekka.heikkila@gmail.com; Surendrakumar Upadhyay,
> > > > > TejaskumarX <tejaskumarx.surendrakumar.upadhyay@intel.com>;
> igt-
> > > > > dev@lists.freedesktop.org
> > > > > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend:
> > > > > Align width to 256B
> > > > >
> > > > > Hi JP,
> > > > >
> > > > > Tejas reapplied the same fix as in
> > > > > https://patchwork.freedesktop.org/patch/445010/?series=92751&rev
> > > > > =2
> > > > > which was reviewed by Daniel.
> > > > >
> > > > > On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
> > > > > > Hi Tejas, Swati,
> > > > > >
> > > > > > I was confused when I read this patch, mind you tell what happen
> here?
> > > > > > To me it look like nothing matches with each other with the patch.
> > > > > >
> > > > > > Even subject is telling other things than what this patch actually
> does.
> > > > > >
> > > > > > On 30.7.2021 8.50, Sharma, Swati2 wrote:
> > > > > >> Reviewed-by:
> > > > > >> Swati Sharma <swati2.sharma@intel.com>
> > > > > >>
> > > > > >> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
> > > > > >>> some display resolutions like 1366x768 6bpc which does not
> > > > > >>> have 64B aligned width are creating crc mismatch in
> > > > > >>> kms_plane_alpha_blend test on Intel platforms.
> > > > > >
> > > > > > hm. You are saying none of Intel hw is able to show 1366 wide
> > > > > > framebuffers correctly? And it is fixed by hiding it from being tested?
> > > > > >
> > > > > > Memory given from kernel will have 64B alignment. You can
> > > > > > easily see by yourself.
> > > > > >
> > > > > >>>
> > > > > >>> Also having different alignment requirement by different
> > > > > >>> drivers, 256B aligned width should work for all drm drivers.
> > > > > >
> > > > > > You are saying you are fixing some problem with Intel hw, what
> > > > > > does all this other stuff have to do with it? None of those
> > > > > > other drivers are able to show 1366 pixels wide framebuffers either?
> > > > > >
> > > > > >>>
> > > > > >>> amdgpu and radeon, amdgpu_align_pitch: 256B armada,
> > > armada_pitch:
> > > > > >>> 128B
> > > > > >>> exynos_drm_gem_dumb_create: No alignment required
> > > > > >>> drm_gem_shmem_dumb_create: 8B
> > > > > >>> drm_gem_vram_fill_create_dumb: 8B
> > > > > >>>
> > > > > >>> Thus 256B covers everything we see in the kernel drm drivers.
> > > > > >>> Signed-off-by: Tejas Upadhyay
> > > > > >>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > > > > >>> ---
> > > > > >>> tests/kms_plane_alpha_blend.c | 1 +
> > > > > >>> 1 file changed, 1 insertion(+)
> > > > > >>>
> > > > > >>> diff --git a/tests/kms_plane_alpha_blend.c
> > > > > >>> b/tests/kms_plane_alpha_blend.c index d649a09f..864e83f9
> > > > > >>> 100644
> > > > > >>> --- a/tests/kms_plane_alpha_blend.c
> > > > > >>> +++ b/tests/kms_plane_alpha_blend.c
> > > > > >>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
> > > > > >>> igt_output_t *output, enum pipe pipe)
> > > > > >>> w = mode->hdisplay;
> > > > > >>> h = mode->vdisplay;
> > > > > >>> + w = ALIGN(w, 256);
> > > > > >
> > > > > > This doesn't cause anything to align with 256 bytes. This
> > > > > > makes fb width in pixels divisible by 256. For anything to do
> > > > > > with fb alignments..this has very little to do. Kernel will do
> > > > > > viewport clipping hence for actual intended test this does
> > > > > > nothing. FB alignments are handled otherwise as in this case
> > > > > > with with linear fb will
> > > > > have 64 bytes per stride.
> > > > > >
> > > > > >>> /* recreate all fbs if incompatible */
> > > > > >>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
> > > > > >>> cairo_t *cr;
> > > > > >>>
> > > > > >>
> > > > > >
> > > > > > If this patch actually fixed anything you'll need to create hw
> > > > > > wa and this need to be fixed in kernel. Not testing is not fixing.
> > > > > > Imo there should be no problem for Intel hw to show varying fb
> > > > > > sizes, including
> > > > > > 1366 wide.
> > > > > >
> > > > > > /Juha-Pekka
> > > > >
> > > > > --
> > > > > ~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B
2021-08-04 3:11 ` Srinivas, Vidya
@ 2021-08-04 4:20 ` Surendrakumar Upadhyay, TejaskumarX
0 siblings, 0 replies; 20+ messages in thread
From: Surendrakumar Upadhyay, TejaskumarX @ 2021-08-04 4:20 UTC (permalink / raw)
To: Srinivas, Vidya, Juha-Pekka Heikkilä; +Cc: Sharma, Swati2, igt-dev
> -----Original Message-----
> From: Srinivas, Vidya <vidya.srinivas@intel.com>
> Sent: 04 August 2021 08:41
> To: Juha-Pekka Heikkilä <juhapekka.heikkila@gmail.com>; Surendrakumar
> Upadhyay, TejaskumarX
> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> Cc: Sharma, Swati2 <swati2.sharma@intel.com>; igt-
> dev@lists.freedesktop.org
> Subject: RE: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to
> 256B
>
>
>
> > -----Original Message-----
> > From: Juha-Pekka Heikkilä <juhapekka.heikkila@gmail.com>
> > Sent: Tuesday, August 3, 2021 11:19 PM
> > To: Srinivas, Vidya <vidya.srinivas@intel.com>
> > Cc: Surendrakumar Upadhyay, TejaskumarX
> > <tejaskumarx.surendrakumar.upadhyay@intel.com>; Sharma, Swati2
> > <swati2.sharma@intel.com>; igt-dev@lists.freedesktop.org
> > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align
> > width to 256B
> >
> > On Tue, Aug 3, 2021 at 7:16 PM Srinivas, Vidya
> > <vidya.srinivas@intel.com>
> > wrote:
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of
> > > > Juha- Pekka Heikkilä
> > > > Sent: Tuesday, August 3, 2021 12:49 AM
> > > > To: Surendrakumar Upadhyay, TejaskumarX
> > > > <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > > > Cc: Sharma, Swati2 <swati2.sharma@intel.com>; igt-
> > > > dev@lists.freedesktop.org
> > > > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align
> > > > width to 256B
> > > >
> > > > On Mon, Aug 2, 2021 at 5:16 PM Surendrakumar Upadhyay,
> TejaskumarX
> > > > <tejaskumarx.surendrakumar.upadhyay@intel.com> wrote:
> > > > >
> > > > > Hi JP,
> > > > >
> > > > > You are right i915 driver is giving 64B aligned buffer but test
> > > > > uses raw width
> > > > and thus it requires width to be aligned.
> > > >
> > > > Can you try this on the device which is failing:
> > > > https://patchwork.freedesktop.org/series/93317/
> > > >
> > > > It will put on pixel blend and alpha and try different width
> > > > linear fbs and compare results with crc. This should tell if
> > > > alignments somehow can affect the crc on your test machine. On my
> > > > ICL everything
> > work as expected.
> > > >
> > >
> > > Hi Juha-Pekka
> > >
> > > With your https://patchwork.freedesktop.org/series/93317/ the test
> > PASSES.
> > > But we need to use both planes and exact same sequence as
> > > kms_plane_alpha_blend coverage-premultiplied-constant case to
> > reproduce the issue.
> > >
> > > But with this modification (same as kms_plane_alpha_blend) done here
> > > https://patchwork.freedesktop.org/patch/448369/?series=93317&rev=3
> > > It PASS with ALIGN in draw_squares and draw_squares_coverage but
> > > fails
> > without the ALIGNMENT.
> > >
> > > Kindly have a check. Thank you. Apologies, I pushed rev3 on top of
> > > yours to
> > try-bot to maintain context.
> > >
> >
> > Hi Vidya,
> >
> > thanks for showing this. Your change should segfault because with your
> > alignment that memory drawing function will draw past reserved memory
> > but that's not the interesting part. That original bug was included on
> > the cut'n'pasted lines, it has nothing to do with strides but just
> > simple rounding issue.
> >
> > Where there's this function:
> >
> > +static void draw_squares(struct igt_fb *fb, int w, int h, double a) {
> > +cairo_t *cr = igt_get_cairo_ctx(fb->fd, fb);
> > +
> > + cairo_set_operator(cr, CAIRO_OPERATOR_SOURCE);
> > + igt_paint_color_alpha(cr, 0, 0, w / 2, h / 2, 1., 0., 0., a);
> > + igt_paint_color_alpha(cr, w / 2, 0, w / 2, h / 2, 0., 1., 0., a);
> > + igt_paint_color_alpha(cr, 0, h / 2, w / 2, h / 2, 0., 0., 1., a);
> > + igt_paint_color_alpha(cr, w / 2, h / 2, w / 4, h / 2, 1., 1., 1.,
> > + a); igt_paint_color_alpha(cr, 3 * w / 4, h / 2, w / 4, h / 2, 0.,
> > + 0., 0., a);
> > +
> > + igt_put_cairo_ctx(cr);
> > +}
> >
> >
> > That last igt_paint_color_alpha(..) will need to say:
> >
> > igt_paint_color_alpha(cr, w * 3 / 4, h / 2, w - (w * 3 / 4), h / 2,
> > 0., 0., 0., a);
> >
> > Otherwise it can draw one pixel too narrow box.
>
> Hello Juha-Pekka,
>
> Thank you so much. With this line change this test kms_stridetest_crc and
> the kms_plane_alpha_blend works too.
> No alignment is needed. Sorry, somehow it did not give the CRASH.
> This is the same issue I was seeking your help, where we tried multiple fixes.
> Thank you so very much. I have submitted the fix you provided in your name
> https://patchwork.freedesktop.org/patch/448556/?series=93370&rev=1
>
> https://patchwork.freedesktop.org/series/93370/
> @Surendrakumar Upadhyay, TejaskumarX Apologies, I have submitted the
> revert in the same series.
> Thank you Tejas.
>
> Can you kindly help review and merge the same?
Thanks JP and Vidya for change. Sure, but we need to test with multiple resolution to confirm the change.
>
> Regards
> Vidya
>
> >
> > /Juha-Pekka
> >
> > > >
> > > > >
> > > > > Thanks,
> > > > > Tejas
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Sharma, Swati2 <swati2.sharma@intel.com>
> > > > > > Sent: 02 August 2021 18:35
> > > > > > To: juhapekka.heikkila@gmail.com; Surendrakumar Upadhyay,
> > > > > > TejaskumarX <tejaskumarx.surendrakumar.upadhyay@intel.com>;
> > igt-
> > > > > > dev@lists.freedesktop.org
> > > > > > Subject: Re: [igt-dev] [i-g-t] tests/kms_plane_alpha_blend:
> > > > > > Align width to 256B
> > > > > >
> > > > > > Hi JP,
> > > > > >
> > > > > > Tejas reapplied the same fix as in
> > > > > > https://patchwork.freedesktop.org/patch/445010/?series=92751&r
> > > > > > ev
> > > > > > =2
> > > > > > which was reviewed by Daniel.
> > > > > >
> > > > > > On 02-Aug-21 5:42 PM, Juha-Pekka Heikkila wrote:
> > > > > > > Hi Tejas, Swati,
> > > > > > >
> > > > > > > I was confused when I read this patch, mind you tell what
> > > > > > > happen
> > here?
> > > > > > > To me it look like nothing matches with each other with the patch.
> > > > > > >
> > > > > > > Even subject is telling other things than what this patch
> > > > > > > actually
> > does.
> > > > > > >
> > > > > > > On 30.7.2021 8.50, Sharma, Swati2 wrote:
> > > > > > >> Reviewed-by:
> > > > > > >> Swati Sharma <swati2.sharma@intel.com>
> > > > > > >>
> > > > > > >> On 28-Jul-21 10:25 AM, Tejas Upadhyay wrote:
> > > > > > >>> some display resolutions like 1366x768 6bpc which does not
> > > > > > >>> have 64B aligned width are creating crc mismatch in
> > > > > > >>> kms_plane_alpha_blend test on Intel platforms.
> > > > > > >
> > > > > > > hm. You are saying none of Intel hw is able to show 1366
> > > > > > > wide framebuffers correctly? And it is fixed by hiding it from being
> tested?
> > > > > > >
> > > > > > > Memory given from kernel will have 64B alignment. You can
> > > > > > > easily see by yourself.
> > > > > > >
> > > > > > >>>
> > > > > > >>> Also having different alignment requirement by different
> > > > > > >>> drivers, 256B aligned width should work for all drm drivers.
> > > > > > >
> > > > > > > You are saying you are fixing some problem with Intel hw,
> > > > > > > what does all this other stuff have to do with it? None of
> > > > > > > those other drivers are able to show 1366 pixels wide
> framebuffers either?
> > > > > > >
> > > > > > >>>
> > > > > > >>> amdgpu and radeon, amdgpu_align_pitch: 256B armada,
> > > > armada_pitch:
> > > > > > >>> 128B
> > > > > > >>> exynos_drm_gem_dumb_create: No alignment required
> > > > > > >>> drm_gem_shmem_dumb_create: 8B
> > > > > > >>> drm_gem_vram_fill_create_dumb: 8B
> > > > > > >>>
> > > > > > >>> Thus 256B covers everything we see in the kernel drm drivers.
> > > > > > >>> Signed-off-by: Tejas Upadhyay
> > > > > > >>> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > > > > > >>> ---
> > > > > > >>> tests/kms_plane_alpha_blend.c | 1 +
> > > > > > >>> 1 file changed, 1 insertion(+)
> > > > > > >>>
> > > > > > >>> diff --git a/tests/kms_plane_alpha_blend.c
> > > > > > >>> b/tests/kms_plane_alpha_blend.c index d649a09f..864e83f9
> > > > > > >>> 100644
> > > > > > >>> --- a/tests/kms_plane_alpha_blend.c
> > > > > > >>> +++ b/tests/kms_plane_alpha_blend.c
> > > > > > >>> @@ -168,6 +168,7 @@ static void prepare_crtc(data_t *data,
> > > > > > >>> igt_output_t *output, enum pipe pipe)
> > > > > > >>> w = mode->hdisplay;
> > > > > > >>> h = mode->vdisplay;
> > > > > > >>> + w = ALIGN(w, 256);
> > > > > > >
> > > > > > > This doesn't cause anything to align with 256 bytes. This
> > > > > > > makes fb width in pixels divisible by 256. For anything to
> > > > > > > do with fb alignments..this has very little to do. Kernel
> > > > > > > will do viewport clipping hence for actual intended test
> > > > > > > this does nothing. FB alignments are handled otherwise as in
> > > > > > > this case with with linear fb will
> > > > > > have 64 bytes per stride.
> > > > > > >
> > > > > > >>> /* recreate all fbs if incompatible */
> > > > > > >>> if (data->xrgb_fb.width != w || data->xrgb_fb.height != h) {
> > > > > > >>> cairo_t *cr;
> > > > > > >>>
> > > > > > >>
> > > > > > >
> > > > > > > If this patch actually fixed anything you'll need to create
> > > > > > > hw wa and this need to be fixed in kernel. Not testing is not fixing.
> > > > > > > Imo there should be no problem for Intel hw to show varying
> > > > > > > fb sizes, including
> > > > > > > 1366 wide.
> > > > > > >
> > > > > > > /Juha-Pekka
> > > > > >
> > > > > > --
> > > > > > ~Swati Sharma
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2021-08-04 4:20 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-28 4:55 [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Tejas Upadhyay
2021-07-28 6:15 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-07-28 8:57 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2021-07-28 14:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-29 8:39 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_alpha_blend: Align width to 256B (rev2) Patchwork
2021-07-29 11:23 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2021-07-29 16:04 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2021-07-30 5:50 ` [igt-dev] [i-g-t] tests/kms_plane_alpha_blend: Align width to 256B Sharma, Swati2
2021-08-02 12:12 ` Juha-Pekka Heikkila
2021-08-02 13:04 ` Sharma, Swati2
2021-08-02 14:16 ` Juha-Pekka Heikkila
2021-08-02 14:16 ` Surendrakumar Upadhyay, TejaskumarX
2021-08-02 14:41 ` Juha-Pekka Heikkila
2021-08-02 19:19 ` Juha-Pekka Heikkilä
2021-08-03 4:55 ` Surendrakumar Upadhyay, TejaskumarX
2021-08-03 9:29 ` Juha-Pekka Heikkilä
2021-08-03 16:16 ` Srinivas, Vidya
2021-08-03 17:49 ` Juha-Pekka Heikkilä
2021-08-04 3:11 ` Srinivas, Vidya
2021-08-04 4:20 ` Surendrakumar Upadhyay, TejaskumarX
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.