* [Intel-gfx] [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
@ 2021-10-05 6:51 ` Sebastian Andrzej Siewior
0 siblings, 0 replies; 23+ messages in thread
From: Sebastian Andrzej Siewior @ 2021-10-05 6:51 UTC (permalink / raw)
To: dri-devel, Maarten Lankhorst, intel-gfx
Cc: Maxime Ripard, Thomas Zimmermann, David Airlie, Daniel Vetter,
Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, Thomas Gleixner,
Sebastian Andrzej Siewior
The warning poped up, it says it increase it by the number of occurrence.
I saw it 18 times so here it is.
It started to up since commit
2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
Increase DRM_OBJECT_MAX_PROPERTY by 18.
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
I have no idea whether this is correct or just a symptom of another
problem. This has been observed with i915 and full debug.
include/drm/drm_mode_object.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/drm/drm_mode_object.h b/include/drm/drm_mode_object.h
index c34a3e8030e12..1e5399e47c3a5 100644
--- a/include/drm/drm_mode_object.h
+++ b/include/drm/drm_mode_object.h
@@ -60,7 +60,7 @@ struct drm_mode_object {
void (*free_cb)(struct kref *kref);
};
-#define DRM_OBJECT_MAX_PROPERTY 24
+#define DRM_OBJECT_MAX_PROPERTY 42
/**
* struct drm_object_properties - property tracking for &drm_mode_object
*/
--
2.33.0
^ permalink raw reply related [flat|nested] 23+ messages in thread* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-05 6:51 ` [Intel-gfx] " Sebastian Andrzej Siewior
(?)
@ 2021-10-05 7:46 ` Patchwork
-1 siblings, 0 replies; 23+ messages in thread
From: Patchwork @ 2021-10-05 7:46 UTC (permalink / raw)
To: Sebastian Andrzej Siewior; +Cc: intel-gfx
== Series Details ==
Series: drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
URL : https://patchwork.freedesktop.org/series/95440/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
275051930b84 drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
-:9: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#9:
2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
total: 0 errors, 1 warnings, 0 checks, 8 lines checked
^ permalink raw reply [flat|nested] 23+ messages in thread* [Intel-gfx] ✓ Fi.CI.BAT: success for drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-05 6:51 ` [Intel-gfx] " Sebastian Andrzej Siewior
(?)
(?)
@ 2021-10-05 8:18 ` Patchwork
-1 siblings, 0 replies; 23+ messages in thread
From: Patchwork @ 2021-10-05 8:18 UTC (permalink / raw)
To: Sebastian Andrzej Siewior; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 7095 bytes --]
== Series Details ==
Series: drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
URL : https://patchwork.freedesktop.org/series/95440/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10681 -> Patchwork_21243
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/index.html
Known issues
------------
Here are the changes found in Patchwork_21243 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@query-info:
- fi-tgl-1115g4: NOTRUN -> [SKIP][1] ([fdo#109315])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-tgl-1115g4/igt@amdgpu/amd_basic@query-info.html
* igt@amdgpu/amd_basic@semaphore:
- fi-bdw-5557u: NOTRUN -> [SKIP][2] ([fdo#109271]) +27 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-bdw-5557u/igt@amdgpu/amd_basic@semaphore.html
* igt@amdgpu/amd_cs_nop@nop-gfx0:
- fi-tgl-1115g4: NOTRUN -> [SKIP][3] ([fdo#109315] / [i915#2575]) +16 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-tgl-1115g4/igt@amdgpu/amd_cs_nop@nop-gfx0.html
* igt@core_hotunplug@unbind-rebind:
- fi-bdw-5557u: NOTRUN -> [WARN][4] ([i915#3718])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-bdw-5557u/igt@core_hotunplug@unbind-rebind.html
* igt@gem_exec_fence@basic-busy@bcs0:
- fi-apl-guc: NOTRUN -> [SKIP][5] ([fdo#109271]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-apl-guc/igt@gem_exec_fence@basic-busy@bcs0.html
* igt@gem_huc_copy@huc-copy:
- fi-tgl-1115g4: NOTRUN -> [SKIP][6] ([i915#2190])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-tgl-1115g4/igt@gem_huc_copy@huc-copy.html
* igt@i915_hangman@error-state-basic:
- fi-apl-guc: NOTRUN -> [DMESG-WARN][7] ([i915#1610])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-apl-guc/igt@i915_hangman@error-state-basic.html
* igt@i915_pm_backlight@basic-brightness:
- fi-tgl-1115g4: NOTRUN -> [SKIP][8] ([i915#1155])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-tgl-1115g4/igt@i915_pm_backlight@basic-brightness.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-tgl-1115g4: NOTRUN -> [SKIP][9] ([fdo#111827]) +8 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-tgl-1115g4/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@dp-crc-fast:
- fi-kbl-7500u: [PASS][10] -> [FAIL][11] ([i915#1372])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/fi-kbl-7500u/igt@kms_chamelium@dp-crc-fast.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-kbl-7500u/igt@kms_chamelium@dp-crc-fast.html
- fi-bdw-5557u: NOTRUN -> [SKIP][12] ([fdo#109271] / [fdo#111827]) +8 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-bdw-5557u/igt@kms_chamelium@dp-crc-fast.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-tgl-1115g4: NOTRUN -> [SKIP][13] ([i915#4103]) +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-tgl-1115g4/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-1115g4: NOTRUN -> [SKIP][14] ([fdo#109285])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-tgl-1115g4/igt@kms_force_connector_basic@force-load-detect.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-bsw-kefka: [PASS][15] -> [INCOMPLETE][16] ([i915#3159])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/fi-bsw-kefka/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-bsw-kefka/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
* igt@kms_psr@primary_mmap_gtt:
- fi-tgl-1115g4: NOTRUN -> [SKIP][17] ([i915#1072]) +3 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-tgl-1115g4/igt@kms_psr@primary_mmap_gtt.html
* igt@prime_vgem@basic-userptr:
- fi-tgl-1115g4: NOTRUN -> [SKIP][18] ([i915#3301])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-tgl-1115g4/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-apl-guc: NOTRUN -> [FAIL][19] ([i915#2426] / [i915#3363])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-apl-guc/igt@runner@aborted.html
#### Possible fixes ####
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b:
- fi-cfl-8109u: [DMESG-WARN][20] ([i915#295]) -> [PASS][21] +12 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/fi-cfl-8109u/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/fi-cfl-8109u/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#1372]: https://gitlab.freedesktop.org/drm/intel/issues/1372
[i915#1610]: https://gitlab.freedesktop.org/drm/intel/issues/1610
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#295]: https://gitlab.freedesktop.org/drm/intel/issues/295
[i915#3159]: https://gitlab.freedesktop.org/drm/intel/issues/3159
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363
[i915#3718]: https://gitlab.freedesktop.org/drm/intel/issues/3718
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
Participating hosts (36 -> 33)
------------------------------
Additional (2): fi-tgl-1115g4 fi-apl-guc
Missing (5): bat-dg1-6 fi-bsw-cyan bat-adlp-4 bat-jsl-2 bat-jsl-1
Build changes
-------------
* Linux: CI_DRM_10681 -> Patchwork_21243
CI-20190529: 20190529
CI_DRM_10681: fe9b639a95a08713c8ee4ef110ce6a6388c9f9f2 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6228: 22643ce4014a0b2dc52ce7916b2f657e2a7757c3 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21243: 275051930b8443502040198bcfd9a40bcf5c1e36 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
275051930b84 drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/index.html
[-- Attachment #2: Type: text/html, Size: 8403 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread* [Intel-gfx] ✓ Fi.CI.IGT: success for drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-05 6:51 ` [Intel-gfx] " Sebastian Andrzej Siewior
` (2 preceding siblings ...)
(?)
@ 2021-10-05 10:09 ` Patchwork
-1 siblings, 0 replies; 23+ messages in thread
From: Patchwork @ 2021-10-05 10:09 UTC (permalink / raw)
To: Sebastian Andrzej Siewior; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 30267 bytes --]
== Series Details ==
Series: drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
URL : https://patchwork.freedesktop.org/series/95440/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10681_full -> Patchwork_21243_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
New tests
---------
New tests have been introduced between CI_DRM_10681_full and Patchwork_21243_full:
### New IGT tests (11) ###
* igt@gem_ctx_persistence@heartbeat-close:
- Statuses : 7 pass(s)
- Exec time: [0.11, 0.33] s
* igt@gem_ctx_persistence@heartbeat-hang:
- Statuses : 7 pass(s) 1 skip(s)
- Exec time: [0.0, 1.48] s
* igt@gem_ctx_persistence@heartbeat-hostile:
- Statuses : 6 pass(s)
- Exec time: [1.17, 1.52] s
* igt@gem_ctx_persistence@heartbeat-many:
- Statuses :
- Exec time: [None] s
* igt@gem_ctx_persistence@heartbeat-stop:
- Statuses : 5 pass(s) 1 skip(s)
- Exec time: [0.0, 0.37] s
* igt@gem_exec_parallel@engines@userptr:
- Statuses : 6 pass(s)
- Exec time: [1.33, 3.39] s
* igt@kms_async_flips@alternate-sync-async-flip:
- Statuses : 7 pass(s) 1 skip(s)
- Exec time: [0.0, 2.04] s
* igt@kms_async_flips@async-flip-with-page-flip-events:
- Statuses : 5 pass(s)
- Exec time: [2.0, 2.00] s
* igt@kms_async_flips@invalid-async-flip:
- Statuses : 5 pass(s) 2 skip(s)
- Exec time: [0.0, 0.04] s
* igt@kms_async_flips@test-cursor:
- Statuses : 8 pass(s)
- Exec time: [0.00, 0.04] s
* igt@kms_async_flips@test-time-stamp:
- Statuses :
- Exec time: [None] s
Known issues
------------
Here are the changes found in Patchwork_21243_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@chamelium:
- shard-tglb: NOTRUN -> [SKIP][1] ([fdo#111827])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb3/igt@feature_discovery@chamelium.html
* igt@gem_ctx_persistence@idempotent:
- shard-snb: NOTRUN -> [SKIP][2] ([fdo#109271] / [i915#1099]) +2 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-snb2/igt@gem_ctx_persistence@idempotent.html
* igt@gem_eio@unwedge-stress:
- shard-tglb: NOTRUN -> [TIMEOUT][3] ([i915#2369] / [i915#3063] / [i915#3648])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][4] -> [FAIL][5] ([i915#2842])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-tglb6/igt@gem_exec_fair@basic-pace-share@rcs0.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb5/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-glk: [PASS][6] -> [FAIL][7] ([i915#2842])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-glk7/igt@gem_exec_fair@basic-pace-solo@rcs0.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-glk2/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gem_exec_flush@basic-uc-ro-default:
- shard-skl: [PASS][8] -> [DMESG-WARN][9] ([i915#1982])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-skl2/igt@gem_exec_flush@basic-uc-ro-default.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-skl10/igt@gem_exec_flush@basic-uc-ro-default.html
* igt@gem_exec_params@no-bsd:
- shard-tglb: NOTRUN -> [SKIP][10] ([fdo#109283])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@gem_exec_params@no-bsd.html
* igt@gem_exec_params@secure-non-master:
- shard-tglb: NOTRUN -> [SKIP][11] ([fdo#112283])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@gem_exec_params@secure-non-master.html
* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [PASS][12] -> [DMESG-WARN][13] ([i915#118] / [i915#95]) +2 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-glk1/igt@gem_exec_whisper@basic-queues-forked-all.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-glk3/igt@gem_exec_whisper@basic-queues-forked-all.html
* igt@gem_render_copy@yf-tiled-to-vebox-y-tiled:
- shard-iclb: NOTRUN -> [SKIP][14] ([i915#768])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@gem_render_copy@yf-tiled-to-vebox-y-tiled.html
* igt@gen7_exec_parse@load-register-reg:
- shard-iclb: NOTRUN -> [SKIP][15] ([fdo#109289]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb6/igt@gen7_exec_parse@load-register-reg.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-kbl: NOTRUN -> [SKIP][16] ([fdo#109271] / [i915#1937])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl4/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp.html
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: NOTRUN -> [WARN][17] ([i915#1804] / [i915#2684])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb6/igt@i915_pm_rc6_residency@rc6-fence.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: NOTRUN -> [WARN][18] ([i915#2684])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@i915_query@query-topology-unsupported:
- shard-tglb: NOTRUN -> [SKIP][19] ([fdo#109302])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb3/igt@i915_query@query-topology-unsupported.html
* igt@i915_suspend@forcewake:
- shard-tglb: [PASS][20] -> [INCOMPLETE][21] ([i915#2411] / [i915#456]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-tglb2/igt@i915_suspend@forcewake.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb7/igt@i915_suspend@forcewake.html
* igt@i915_suspend@sysfs-reader:
- shard-skl: [PASS][22] -> [INCOMPLETE][23] ([i915#146] / [i915#198])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-skl1/igt@i915_suspend@sysfs-reader.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-skl3/igt@i915_suspend@sysfs-reader.html
* igt@kms_async_flips@invalid-async-flip (NEW):
- {shard-rkl}: [PASS][24] -> [SKIP][25] ([i915#1845])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-6/igt@kms_async_flips@invalid-async-flip.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-2/igt@kms_async_flips@invalid-async-flip.html
* igt@kms_big_fb@x-tiled-32bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][26] ([fdo#110725] / [fdo#111614])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb6/igt@kms_big_fb@x-tiled-32bpp-rotate-270.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-apl: NOTRUN -> [SKIP][27] ([fdo#109271] / [i915#3777])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl1/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip.html
- shard-tglb: NOTRUN -> [SKIP][28] ([fdo#111615])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-180-async-flip:
- shard-iclb: NOTRUN -> [SKIP][29] ([fdo#110723])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html
* igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][30] ([i915#3689]) +2 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_ccs.html
* igt@kms_ccs@pipe-b-bad-aux-stride-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][31] ([fdo#109271] / [i915#3886]) +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl3/igt@kms_ccs@pipe-b-bad-aux-stride-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][32] ([fdo#109271] / [i915#3886]) +3 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl2/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs.html
* igt@kms_chamelium@hdmi-mode-timings:
- shard-snb: NOTRUN -> [SKIP][33] ([fdo#109271] / [fdo#111827]) +21 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-snb2/igt@kms_chamelium@hdmi-mode-timings.html
* igt@kms_chamelium@vga-hpd-with-enabled-mode:
- shard-tglb: NOTRUN -> [SKIP][34] ([fdo#109284] / [fdo#111827]) +5 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb3/igt@kms_chamelium@vga-hpd-with-enabled-mode.html
* igt@kms_color_chamelium@pipe-a-ctm-0-25:
- shard-iclb: NOTRUN -> [SKIP][35] ([fdo#109284] / [fdo#111827]) +2 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb6/igt@kms_color_chamelium@pipe-a-ctm-0-25.html
* igt@kms_color_chamelium@pipe-a-ctm-0-5:
- shard-apl: NOTRUN -> [SKIP][36] ([fdo#109271] / [fdo#111827]) +13 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl7/igt@kms_color_chamelium@pipe-a-ctm-0-5.html
* igt@kms_color_chamelium@pipe-b-degamma:
- shard-kbl: NOTRUN -> [SKIP][37] ([fdo#109271] / [fdo#111827]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl4/igt@kms_color_chamelium@pipe-b-degamma.html
* igt@kms_color_chamelium@pipe-d-ctm-negative:
- shard-iclb: NOTRUN -> [SKIP][38] ([fdo#109278] / [fdo#109284] / [fdo#111827])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@kms_color_chamelium@pipe-d-ctm-negative.html
* igt@kms_content_protection@dp-mst-type-0:
- shard-tglb: NOTRUN -> [SKIP][39] ([i915#3116])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb2/igt@kms_content_protection@dp-mst-type-0.html
* igt@kms_cursor_crc@pipe-a-cursor-alpha-opaque:
- shard-kbl: NOTRUN -> [FAIL][40] ([i915#3444])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl3/igt@kms_cursor_crc@pipe-a-cursor-alpha-opaque.html
- shard-snb: NOTRUN -> [FAIL][41] ([i915#4024])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-snb2/igt@kms_cursor_crc@pipe-a-cursor-alpha-opaque.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [PASS][42] -> [DMESG-WARN][43] ([i915#180]) +6 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl6/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
- shard-tglb: [PASS][44] -> [INCOMPLETE][45] ([i915#2411] / [i915#2828] / [i915#456])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-tglb5/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb7/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
- shard-skl: [PASS][46] -> [INCOMPLETE][47] ([i915#2828] / [i915#300])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-skl3/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-skl2/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
* igt@kms_cursor_crc@pipe-b-cursor-32x10-sliding:
- shard-tglb: NOTRUN -> [SKIP][48] ([i915#3359]) +1 similar issue
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb2/igt@kms_cursor_crc@pipe-b-cursor-32x10-sliding.html
* igt@kms_cursor_crc@pipe-c-cursor-512x512-random:
- shard-tglb: NOTRUN -> [SKIP][49] ([fdo#109279] / [i915#3359]) +2 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@kms_cursor_crc@pipe-c-cursor-512x512-random.html
* igt@kms_cursor_crc@pipe-d-cursor-32x32-random:
- shard-tglb: NOTRUN -> [SKIP][50] ([i915#3319])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@kms_cursor_crc@pipe-d-cursor-32x32-random.html
* igt@kms_cursor_crc@pipe-d-cursor-64x21-rapid-movement:
- shard-apl: NOTRUN -> [SKIP][51] ([fdo#109271]) +135 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl2/igt@kms_cursor_crc@pipe-d-cursor-64x21-rapid-movement.html
* igt@kms_cursor_crc@pipe-d-cursor-dpms:
- shard-iclb: NOTRUN -> [SKIP][52] ([fdo#109278]) +6 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb6/igt@kms_cursor_crc@pipe-d-cursor-dpms.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-kbl: [PASS][53] -> [INCOMPLETE][54] ([i915#155] / [i915#636])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-kbl1/igt@kms_fbcon_fbt@fbc-suspend.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl4/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs:
- shard-iclb: [PASS][55] -> [SKIP][56] ([i915#3701])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-iclb4/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile:
- shard-snb: NOTRUN -> [SKIP][57] ([fdo#109271]) +433 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-snb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html
- shard-iclb: NOTRUN -> [SKIP][58] ([i915#3701])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html
* igt@kms_frontbuffer_tracking@fbc-rgb565-draw-mmap-wc:
- shard-skl: NOTRUN -> [SKIP][59] ([fdo#109271])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-skl6/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-indfb-draw-blt:
- shard-tglb: NOTRUN -> [SKIP][60] ([fdo#111825]) +12 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-move:
- shard-iclb: NOTRUN -> [SKIP][61] ([fdo#109280]) +7 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-move.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render:
- shard-kbl: NOTRUN -> [SKIP][62] ([fdo#109271]) +40 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][63] -> [FAIL][64] ([i915#1188]) +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-skl3/igt@kms_hdr@bpc-switch-dpms.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-skl6/igt@kms_hdr@bpc-switch-dpms.html
* igt@kms_hdr@static-swap:
- shard-iclb: NOTRUN -> [SKIP][65] ([i915#1187])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@kms_hdr@static-swap.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
- shard-apl: [PASS][66] -> [DMESG-WARN][67] ([i915#180]) +2 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-apl3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html
- shard-kbl: NOTRUN -> [DMESG-WARN][68] ([i915#180])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-kbl: NOTRUN -> [FAIL][69] ([i915#265])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl4/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html
* igt@kms_plane_alpha_blend@pipe-b-alpha-basic:
- shard-apl: NOTRUN -> [FAIL][70] ([fdo#108145] / [i915#265]) +2 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl2/igt@kms_plane_alpha_blend@pipe-b-alpha-basic.html
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [PASS][71] -> [FAIL][72] ([fdo#108145] / [i915#265]) +1 similar issue
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-skl8/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-skl7/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
* igt@kms_plane_lowres@pipe-b-tiling-y:
- shard-tglb: NOTRUN -> [SKIP][73] ([i915#3536])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb3/igt@kms_plane_lowres@pipe-b-tiling-y.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1:
- shard-kbl: NOTRUN -> [SKIP][74] ([fdo#109271] / [i915#658]) +1 similar issue
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl4/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2:
- shard-tglb: NOTRUN -> [SKIP][75] ([i915#2920])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4:
- shard-apl: NOTRUN -> [SKIP][76] ([fdo#109271] / [i915#658]) +1 similar issue
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl7/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-iclb: NOTRUN -> [SKIP][77] ([i915#2920])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1.html
* igt@kms_psr@psr2_dpms:
- shard-tglb: NOTRUN -> [FAIL][78] ([i915#132] / [i915#3467])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@kms_psr@psr2_dpms.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [PASS][79] -> [SKIP][80] ([fdo#109441]) +3 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb4/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_sysfs_edid_timing:
- shard-kbl: NOTRUN -> [FAIL][81] ([IGT#2])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl4/igt@kms_sysfs_edid_timing.html
* igt@kms_writeback@writeback-fb-id:
- shard-apl: NOTRUN -> [SKIP][82] ([fdo#109271] / [i915#2437])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl2/igt@kms_writeback@writeback-fb-id.html
* igt@nouveau_crc@pipe-a-ctx-flip-detection:
- shard-tglb: NOTRUN -> [SKIP][83] ([i915#2530]) +1 similar issue
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@nouveau_crc@pipe-a-ctx-flip-detection.html
* igt@prime_nv_api@i915_nv_import_vs_close:
- shard-iclb: NOTRUN -> [SKIP][84] ([fdo#109291])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb6/igt@prime_nv_api@i915_nv_import_vs_close.html
* igt@prime_nv_test@i915_blt_fill_nv_read:
- shard-tglb: NOTRUN -> [SKIP][85] ([fdo#109291])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@prime_nv_test@i915_blt_fill_nv_read.html
* igt@prime_vgem@basic-userptr:
- shard-iclb: NOTRUN -> [SKIP][86] ([i915#3301])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@prime_vgem@basic-userptr.html
* igt@prime_vgem@fence-write-hang:
- shard-iclb: NOTRUN -> [SKIP][87] ([fdo#109295])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@prime_vgem@fence-write-hang.html
* igt@sysfs_clients@fair-1:
- shard-apl: NOTRUN -> [SKIP][88] ([fdo#109271] / [i915#2994]) +1 similar issue
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl7/igt@sysfs_clients@fair-1.html
* igt@sysfs_heartbeat_interval@precise@vecs0:
- shard-tglb: [PASS][89] -> [FAIL][90] ([i915#1755])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-tglb8/igt@sysfs_heartbeat_interval@precise@vecs0.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb5/igt@sysfs_heartbeat_interval@precise@vecs0.html
- shard-apl: [PASS][91] -> [FAIL][92] ([i915#1755])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-apl8/igt@sysfs_heartbeat_interval@precise@vecs0.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl6/igt@sysfs_heartbeat_interval@precise@vecs0.html
#### Possible fixes ####
* igt@fbdev@read:
- {shard-rkl}: [SKIP][93] ([i915#2582]) -> [PASS][94] +2 similar issues
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@fbdev@read.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-6/igt@fbdev@read.html
* igt@feature_discovery@psr2:
- {shard-rkl}: [SKIP][95] ([i915#658]) -> [PASS][96] +1 similar issue
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@feature_discovery@psr2.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-6/igt@feature_discovery@psr2.html
* igt@gem_eio@in-flight-contexts-immediate:
- shard-iclb: [TIMEOUT][97] ([i915#3070]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-iclb3/igt@gem_eio@in-flight-contexts-immediate.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb6/igt@gem_eio@in-flight-contexts-immediate.html
* igt@gem_eio@unwedge-stress:
- shard-iclb: [TIMEOUT][99] ([i915#2369] / [i915#2481] / [i915#3070]) -> [PASS][100]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-iclb3/igt@gem_eio@unwedge-stress.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb6/igt@gem_eio@unwedge-stress.html
- {shard-rkl}: [FAIL][101] ([i915#3115]) -> [PASS][102]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-1/igt@gem_eio@unwedge-stress.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-1/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- {shard-rkl}: [FAIL][103] ([i915#2842]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-1/igt@gem_exec_fair@basic-pace-solo@rcs0.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-2/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gem_exec_fair@basic-pace@bcs0:
- shard-iclb: [FAIL][105] ([i915#2842]) -> [PASS][106]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-iclb4/igt@gem_exec_fair@basic-pace@bcs0.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb7/igt@gem_exec_fair@basic-pace@bcs0.html
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: [FAIL][107] ([i915#2842]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-kbl3/igt@gem_exec_fair@basic-pace@vecs0.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl2/igt@gem_exec_fair@basic-pace@vecs0.html
* igt@gem_exec_fair@basic-sync@rcs0:
- shard-kbl: [SKIP][109] ([fdo#109271]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-kbl1/igt@gem_exec_fair@basic-sync@rcs0.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl4/igt@gem_exec_fair@basic-sync@rcs0.html
* igt@gem_exec_reloc@basic-scanout@vecs0:
- {shard-rkl}: [SKIP][111] ([i915#3639]) -> [PASS][112] +3 similar issues
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@gem_exec_reloc@basic-scanout@vecs0.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-6/igt@gem_exec_reloc@basic-scanout@vecs0.html
* igt@gem_exec_whisper@basic-queues-priority-all:
- shard-iclb: [INCOMPLETE][113] ([i915#1895]) -> [PASS][114]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-iclb6/igt@gem_exec_whisper@basic-queues-priority-all.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-iclb2/igt@gem_exec_whisper@basic-queues-priority-all.html
* igt@gem_workarounds@suspend-resume:
- shard-tglb: [INCOMPLETE][115] ([i915#456]) -> [PASS][116] +1 similar issue
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-tglb7/igt@gem_workarounds@suspend-resume.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-tglb6/igt@gem_workarounds@suspend-resume.html
* igt@i915_pm_rpm@drm-resources-equal:
- {shard-rkl}: [SKIP][117] ([fdo#109308]) -> [PASS][118] +2 similar issues
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@i915_pm_rpm@drm-resources-equal.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-6/igt@i915_pm_rpm@drm-resources-equal.html
* igt@i915_selftest@live@gt_pm:
- {shard-rkl}: [DMESG-FAIL][119] ([i915#1021]) -> [PASS][120]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-6/igt@i915_selftest@live@gt_pm.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-1/igt@i915_selftest@live@gt_pm.html
* igt@i915_suspend@debugfs-reader:
- shard-apl: [DMESG-WARN][121] ([i915#180]) -> [PASS][122]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-apl7/igt@i915_suspend@debugfs-reader.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-apl1/igt@i915_suspend@debugfs-reader.html
* igt@i915_suspend@fence-restore-untiled:
- shard-kbl: [DMESG-WARN][123] ([i915#180]) -> [PASS][124]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-kbl4/igt@i915_suspend@fence-restore-untiled.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-kbl3/igt@i915_suspend@fence-restore-untiled.html
* igt@kms_async_flips@crc:
- {shard-rkl}: [SKIP][125] -> [PASS][126]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@kms_async_flips@crc.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-6/igt@kms_async_flips@crc.html
* igt@kms_big_fb@linear-max-hw-stride-32bpp-rotate-0:
- {shard-rkl}: [SKIP][127] ([i915#3721]) -> [PASS][128] +8 similar issues
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@kms_big_fb@linear-max-hw-stride-32bpp-rotate-0.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-6/igt@kms_big_fb@linear-max-hw-stride-32bpp-rotate-0.html
* igt@kms_big_fb@x-tiled-32bpp-rotate-0:
- shard-glk: [DMESG-WARN][129] ([i915#118] / [i915#95]) -> [PASS][130] +2 similar issues
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-glk1/igt@kms_big_fb@x-tiled-32bpp-rotate-0.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-glk3/igt@kms_big_fb@x-tiled-32bpp-rotate-0.html
* igt@kms_big_fb@x-tiled-64bpp-rotate-180:
- {shard-rkl}: [SKIP][131] ([i915#3638]) -> [PASS][132] +3 similar issues
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@kms_big_fb@x-tiled-64bpp-rotate-180.html
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-6/igt@kms_big_fb@x-tiled-64bpp-rotate-180.html
* igt@kms_big_fb@y-tiled-16bpp-rotate-90:
- {shard-rkl}: [SKIP][133] ([fdo#111614]) -> [PASS][134] +2 similar issues
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@kms_big_fb@y-tiled-16bpp-rotate-90.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-6/igt@kms_big_fb@y-tiled-16bpp-rotate-90.html
* igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc:
- {shard-rkl}: [SKIP][135] ([i915#1845]) -> [PASS][136] +35 similar issues
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/shard-rkl-6/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_color@pipe-a-ctm-0-5:
- {shard-rkl}: [SKIP][137] ([i915#1149] / [i915#1849] / [i915#4070]) -> [PASS][138] +4 similar issues
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10681/shard-rkl-2/igt@
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21243/index.html
[-- Attachment #2: Type: text/html, Size: 33811 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-05 6:51 ` [Intel-gfx] " Sebastian Andrzej Siewior
@ 2021-10-13 12:02 ` Daniel Vetter
-1 siblings, 0 replies; 23+ messages in thread
From: Daniel Vetter @ 2021-10-13 12:02 UTC (permalink / raw)
To: Sebastian Andrzej Siewior
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Daniel Vetter, Jani Nikula,
Joonas Lahtinen, Rodrigo Vivi, Thomas Gleixner
On Tue, Oct 05, 2021 at 08:51:51AM +0200, Sebastian Andrzej Siewior wrote:
> The warning poped up, it says it increase it by the number of occurrence.
> I saw it 18 times so here it is.
> It started to up since commit
> 2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
>
> Increase DRM_OBJECT_MAX_PROPERTY by 18.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Which driver where? Whomever added that into upstream should also have
realized this (things will just not work) and include it in there. So if
things are tested correctly this should be part of a larger series to add
these 18 props somewhere.
Also maybe we should just dynamically allocate this array if people have
this many properties on their objects.
-Daniel
> ---
>
> I have no idea whether this is correct or just a symptom of another
> problem. This has been observed with i915 and full debug.
>
> include/drm/drm_mode_object.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/drm/drm_mode_object.h b/include/drm/drm_mode_object.h
> index c34a3e8030e12..1e5399e47c3a5 100644
> --- a/include/drm/drm_mode_object.h
> +++ b/include/drm/drm_mode_object.h
> @@ -60,7 +60,7 @@ struct drm_mode_object {
> void (*free_cb)(struct kref *kref);
> };
>
> -#define DRM_OBJECT_MAX_PROPERTY 24
> +#define DRM_OBJECT_MAX_PROPERTY 42
> /**
> * struct drm_object_properties - property tracking for &drm_mode_object
> */
> --
> 2.33.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [Intel-gfx] [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
@ 2021-10-13 12:02 ` Daniel Vetter
0 siblings, 0 replies; 23+ messages in thread
From: Daniel Vetter @ 2021-10-13 12:02 UTC (permalink / raw)
To: Sebastian Andrzej Siewior
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Daniel Vetter, Jani Nikula,
Joonas Lahtinen, Rodrigo Vivi, Thomas Gleixner
On Tue, Oct 05, 2021 at 08:51:51AM +0200, Sebastian Andrzej Siewior wrote:
> The warning poped up, it says it increase it by the number of occurrence.
> I saw it 18 times so here it is.
> It started to up since commit
> 2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
>
> Increase DRM_OBJECT_MAX_PROPERTY by 18.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Which driver where? Whomever added that into upstream should also have
realized this (things will just not work) and include it in there. So if
things are tested correctly this should be part of a larger series to add
these 18 props somewhere.
Also maybe we should just dynamically allocate this array if people have
this many properties on their objects.
-Daniel
> ---
>
> I have no idea whether this is correct or just a symptom of another
> problem. This has been observed with i915 and full debug.
>
> include/drm/drm_mode_object.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/drm/drm_mode_object.h b/include/drm/drm_mode_object.h
> index c34a3e8030e12..1e5399e47c3a5 100644
> --- a/include/drm/drm_mode_object.h
> +++ b/include/drm/drm_mode_object.h
> @@ -60,7 +60,7 @@ struct drm_mode_object {
> void (*free_cb)(struct kref *kref);
> };
>
> -#define DRM_OBJECT_MAX_PROPERTY 24
> +#define DRM_OBJECT_MAX_PROPERTY 42
> /**
> * struct drm_object_properties - property tracking for &drm_mode_object
> */
> --
> 2.33.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-13 12:02 ` [Intel-gfx] " Daniel Vetter
@ 2021-10-13 12:35 ` Sebastian Andrzej Siewior
-1 siblings, 0 replies; 23+ messages in thread
From: Sebastian Andrzej Siewior @ 2021-10-13 12:35 UTC (permalink / raw)
To: Daniel Vetter
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Jani Nikula, Joonas Lahtinen,
Rodrigo Vivi, Thomas Gleixner
On 2021-10-13 14:02:59 [+0200], Daniel Vetter wrote:
> On Tue, Oct 05, 2021 at 08:51:51AM +0200, Sebastian Andrzej Siewior wrote:
> > The warning poped up, it says it increase it by the number of occurrence.
> > I saw it 18 times so here it is.
> > It started to up since commit
> > 2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
> >
> > Increase DRM_OBJECT_MAX_PROPERTY by 18.
> >
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>
> Which driver where? Whomever added that into upstream should also have
> realized this (things will just not work) and include it in there. So if
> things are tested correctly this should be part of a larger series to add
> these 18 props somewhere.
This is on i915 with full debug. If I remember correctly, it wasn't
there before commit
c7fcbf2513973 ("drm/plane: check that fb_damage is set up when used")
With that commit the box crashed until commit
2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
where I then observed this.
> Also maybe we should just dynamically allocate this array if people have
> this many properties on their objects.
> -Daniel
Sebastian
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [Intel-gfx] [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
@ 2021-10-13 12:35 ` Sebastian Andrzej Siewior
0 siblings, 0 replies; 23+ messages in thread
From: Sebastian Andrzej Siewior @ 2021-10-13 12:35 UTC (permalink / raw)
To: Daniel Vetter
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Jani Nikula, Joonas Lahtinen,
Rodrigo Vivi, Thomas Gleixner
On 2021-10-13 14:02:59 [+0200], Daniel Vetter wrote:
> On Tue, Oct 05, 2021 at 08:51:51AM +0200, Sebastian Andrzej Siewior wrote:
> > The warning poped up, it says it increase it by the number of occurrence.
> > I saw it 18 times so here it is.
> > It started to up since commit
> > 2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
> >
> > Increase DRM_OBJECT_MAX_PROPERTY by 18.
> >
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>
> Which driver where? Whomever added that into upstream should also have
> realized this (things will just not work) and include it in there. So if
> things are tested correctly this should be part of a larger series to add
> these 18 props somewhere.
This is on i915 with full debug. If I remember correctly, it wasn't
there before commit
c7fcbf2513973 ("drm/plane: check that fb_damage is set up when used")
With that commit the box crashed until commit
2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
where I then observed this.
> Also maybe we should just dynamically allocate this array if people have
> this many properties on their objects.
> -Daniel
Sebastian
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-13 12:35 ` [Intel-gfx] " Sebastian Andrzej Siewior
@ 2021-10-13 12:57 ` Daniel Vetter
-1 siblings, 0 replies; 23+ messages in thread
From: Daniel Vetter @ 2021-10-13 12:57 UTC (permalink / raw)
To: Sebastian Andrzej Siewior
Cc: Daniel Vetter, dri-devel, Maarten Lankhorst, intel-gfx,
Maxime Ripard, Thomas Zimmermann, David Airlie, Jani Nikula,
Joonas Lahtinen, Rodrigo Vivi, Thomas Gleixner
On Wed, Oct 13, 2021 at 02:35:25PM +0200, Sebastian Andrzej Siewior wrote:
> On 2021-10-13 14:02:59 [+0200], Daniel Vetter wrote:
> > On Tue, Oct 05, 2021 at 08:51:51AM +0200, Sebastian Andrzej Siewior wrote:
> > > The warning poped up, it says it increase it by the number of occurrence.
> > > I saw it 18 times so here it is.
> > > It started to up since commit
> > > 2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
> > >
> > > Increase DRM_OBJECT_MAX_PROPERTY by 18.
> > >
> > > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> >
> > Which driver where? Whomever added that into upstream should also have
> > realized this (things will just not work) and include it in there. So if
> > things are tested correctly this should be part of a larger series to add
> > these 18 props somewhere.
>
> This is on i915 with full debug. If I remember correctly, it wasn't
> there before commit
> c7fcbf2513973 ("drm/plane: check that fb_damage is set up when used")
>
> With that commit the box crashed until commit
> 2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
>
> where I then observed this.
Hm there's a pile of commits there, and nothing immediately jumps to
light. The thing is, 18 is likely way too much, since if e.g. we have a
single new property on a plane and that pushes over the limit on all of
them, you get iirc 3x4 already simply because we have that many planes.
So would be good to know the actual culprit.
Can you pls try to bisect the above range, applying the patch as a fixup
locally (without commit, that will confuse git bisect a bit I think), so
we know what/where went wrong?
I'm still confused why this isn't showing up anywhere in our intel ci ...
Thanks, Daniel
>
> > Also maybe we should just dynamically allocate this array if people have
> > this many properties on their objects.
> > -Daniel
>
> Sebastian
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [Intel-gfx] [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
@ 2021-10-13 12:57 ` Daniel Vetter
0 siblings, 0 replies; 23+ messages in thread
From: Daniel Vetter @ 2021-10-13 12:57 UTC (permalink / raw)
To: Sebastian Andrzej Siewior
Cc: Daniel Vetter, dri-devel, Maarten Lankhorst, intel-gfx,
Maxime Ripard, Thomas Zimmermann, David Airlie, Jani Nikula,
Joonas Lahtinen, Rodrigo Vivi, Thomas Gleixner
On Wed, Oct 13, 2021 at 02:35:25PM +0200, Sebastian Andrzej Siewior wrote:
> On 2021-10-13 14:02:59 [+0200], Daniel Vetter wrote:
> > On Tue, Oct 05, 2021 at 08:51:51AM +0200, Sebastian Andrzej Siewior wrote:
> > > The warning poped up, it says it increase it by the number of occurrence.
> > > I saw it 18 times so here it is.
> > > It started to up since commit
> > > 2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
> > >
> > > Increase DRM_OBJECT_MAX_PROPERTY by 18.
> > >
> > > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> >
> > Which driver where? Whomever added that into upstream should also have
> > realized this (things will just not work) and include it in there. So if
> > things are tested correctly this should be part of a larger series to add
> > these 18 props somewhere.
>
> This is on i915 with full debug. If I remember correctly, it wasn't
> there before commit
> c7fcbf2513973 ("drm/plane: check that fb_damage is set up when used")
>
> With that commit the box crashed until commit
> 2f425cf5242a0 ("drm: Fix oops in damage self-tests by mocking damage property")
>
> where I then observed this.
Hm there's a pile of commits there, and nothing immediately jumps to
light. The thing is, 18 is likely way too much, since if e.g. we have a
single new property on a plane and that pushes over the limit on all of
them, you get iirc 3x4 already simply because we have that many planes.
So would be good to know the actual culprit.
Can you pls try to bisect the above range, applying the patch as a fixup
locally (without commit, that will confuse git bisect a bit I think), so
we know what/where went wrong?
I'm still confused why this isn't showing up anywhere in our intel ci ...
Thanks, Daniel
>
> > Also maybe we should just dynamically allocate this array if people have
> > this many properties on their objects.
> > -Daniel
>
> Sebastian
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-13 12:57 ` [Intel-gfx] " Daniel Vetter
@ 2021-10-13 17:35 ` Sebastian Andrzej Siewior
-1 siblings, 0 replies; 23+ messages in thread
From: Sebastian Andrzej Siewior @ 2021-10-13 17:35 UTC (permalink / raw)
To: Daniel Vetter
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Jani Nikula, Joonas Lahtinen,
Rodrigo Vivi, Thomas Gleixner
On 2021-10-13 14:57:34 [+0200], Daniel Vetter wrote:
> Hm there's a pile of commits there, and nothing immediately jumps to
> light. The thing is, 18 is likely way too much, since if e.g. we have a
> single new property on a plane and that pushes over the limit on all of
> them, you get iirc 3x4 already simply because we have that many planes.
>
> So would be good to know the actual culprit.
>
> Can you pls try to bisect the above range, applying the patch as a fixup
> locally (without commit, that will confuse git bisect a bit I think), so
> we know what/where went wrong?
c7fcbf2513973 -> does not boot
c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY
6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> I'm still confused why this isn't showing up anywhere in our intel ci ...
>
> Thanks, Daniel
Sebastian
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Intel-gfx] [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
@ 2021-10-13 17:35 ` Sebastian Andrzej Siewior
0 siblings, 0 replies; 23+ messages in thread
From: Sebastian Andrzej Siewior @ 2021-10-13 17:35 UTC (permalink / raw)
To: Daniel Vetter
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Jani Nikula, Joonas Lahtinen,
Rodrigo Vivi, Thomas Gleixner
On 2021-10-13 14:57:34 [+0200], Daniel Vetter wrote:
> Hm there's a pile of commits there, and nothing immediately jumps to
> light. The thing is, 18 is likely way too much, since if e.g. we have a
> single new property on a plane and that pushes over the limit on all of
> them, you get iirc 3x4 already simply because we have that many planes.
>
> So would be good to know the actual culprit.
>
> Can you pls try to bisect the above range, applying the patch as a fixup
> locally (without commit, that will confuse git bisect a bit I think), so
> we know what/where went wrong?
c7fcbf2513973 -> does not boot
c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY
6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> I'm still confused why this isn't showing up anywhere in our intel ci ...
>
> Thanks, Daniel
Sebastian
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-13 17:35 ` [Intel-gfx] " Sebastian Andrzej Siewior
@ 2021-10-14 13:21 ` Daniel Vetter
-1 siblings, 0 replies; 23+ messages in thread
From: Daniel Vetter @ 2021-10-14 13:21 UTC (permalink / raw)
To: Sebastian Andrzej Siewior
Cc: Daniel Vetter, dri-devel, Maarten Lankhorst, intel-gfx,
Maxime Ripard, Thomas Zimmermann, David Airlie, Jani Nikula,
Joonas Lahtinen, Rodrigo Vivi, Thomas Gleixner
On Wed, Oct 13, 2021 at 07:35:48PM +0200, Sebastian Andrzej Siewior wrote:
> On 2021-10-13 14:57:34 [+0200], Daniel Vetter wrote:
> > Hm there's a pile of commits there, and nothing immediately jumps to
> > light. The thing is, 18 is likely way too much, since if e.g. we have a
> > single new property on a plane and that pushes over the limit on all of
> > them, you get iirc 3x4 already simply because we have that many planes.
> >
> > So would be good to know the actual culprit.
> >
> > Can you pls try to bisect the above range, applying the patch as a fixup
> > locally (without commit, that will confuse git bisect a bit I think), so
> > we know what/where went wrong?
>
> c7fcbf2513973 -> does not boot
> c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> 6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY
> 6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
Just to check, you've built 6f11f37459d8f, and then you cherry-picked
2f425cf5242a0 on top (not merged), and that already got you the warning
flood?
I'm probably blind, but I'm really not seeing where this pile of
properties is coming from. Can you pls also boot with drm.debug=0xe and
attach full dmesg? Plus your .config please.
Thanks, Daniel
>
> > I'm still confused why this isn't showing up anywhere in our intel ci ...
> >
> > Thanks, Daniel
>
> Sebastian
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Intel-gfx] [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
@ 2021-10-14 13:21 ` Daniel Vetter
0 siblings, 0 replies; 23+ messages in thread
From: Daniel Vetter @ 2021-10-14 13:21 UTC (permalink / raw)
To: Sebastian Andrzej Siewior
Cc: Daniel Vetter, dri-devel, Maarten Lankhorst, intel-gfx,
Maxime Ripard, Thomas Zimmermann, David Airlie, Jani Nikula,
Joonas Lahtinen, Rodrigo Vivi, Thomas Gleixner
On Wed, Oct 13, 2021 at 07:35:48PM +0200, Sebastian Andrzej Siewior wrote:
> On 2021-10-13 14:57:34 [+0200], Daniel Vetter wrote:
> > Hm there's a pile of commits there, and nothing immediately jumps to
> > light. The thing is, 18 is likely way too much, since if e.g. we have a
> > single new property on a plane and that pushes over the limit on all of
> > them, you get iirc 3x4 already simply because we have that many planes.
> >
> > So would be good to know the actual culprit.
> >
> > Can you pls try to bisect the above range, applying the patch as a fixup
> > locally (without commit, that will confuse git bisect a bit I think), so
> > we know what/where went wrong?
>
> c7fcbf2513973 -> does not boot
> c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> 6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY
> 6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
Just to check, you've built 6f11f37459d8f, and then you cherry-picked
2f425cf5242a0 on top (not merged), and that already got you the warning
flood?
I'm probably blind, but I'm really not seeing where this pile of
properties is coming from. Can you pls also boot with drm.debug=0xe and
attach full dmesg? Plus your .config please.
Thanks, Daniel
>
> > I'm still confused why this isn't showing up anywhere in our intel ci ...
> >
> > Thanks, Daniel
>
> Sebastian
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-14 13:21 ` [Intel-gfx] " Daniel Vetter
@ 2021-10-14 13:47 ` Sebastian Andrzej Siewior
-1 siblings, 0 replies; 23+ messages in thread
From: Sebastian Andrzej Siewior @ 2021-10-14 13:47 UTC (permalink / raw)
To: Daniel Vetter
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Jani Nikula, Joonas Lahtinen,
Rodrigo Vivi, Thomas Gleixner
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On 2021-10-14 15:21:22 [+0200], Daniel Vetter wrote:
> On Wed, Oct 13, 2021 at 07:35:48PM +0200, Sebastian Andrzej Siewior wrote:
> > c7fcbf2513973 -> does not boot
> > c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> > 6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY
> > 6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
>
> Just to check, you've built 6f11f37459d8f, and then you cherry-picked
> 2f425cf5242a0 on top (not merged), and that already got you the warning
> flood?
Correct.
> I'm probably blind, but I'm really not seeing where this pile of
> properties is coming from. Can you pls also boot with drm.debug=0xe and
> attach full dmesg? Plus your .config please.
attached. dmesg.txt is 6f11f37459d8f and the other is 6f11f37459d8f +
2f425cf5242a0.
> Thanks, Daniel
Sebastian
[-- Attachment #2: config.xz --]
[-- Type: application/x-xz, Size: 30168 bytes --]
[-- Attachment #3: dmesg.txt.xz --]
[-- Type: application/x-xz, Size: 25228 bytes --]
[-- Attachment #4: dmesg-with-2f425cf5242a0.txt.xz --]
[-- Type: application/x-xz, Size: 28104 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Intel-gfx] [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
@ 2021-10-14 13:47 ` Sebastian Andrzej Siewior
0 siblings, 0 replies; 23+ messages in thread
From: Sebastian Andrzej Siewior @ 2021-10-14 13:47 UTC (permalink / raw)
To: Daniel Vetter
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Jani Nikula, Joonas Lahtinen,
Rodrigo Vivi, Thomas Gleixner
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On 2021-10-14 15:21:22 [+0200], Daniel Vetter wrote:
> On Wed, Oct 13, 2021 at 07:35:48PM +0200, Sebastian Andrzej Siewior wrote:
> > c7fcbf2513973 -> does not boot
> > c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> > 6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY
> > 6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
>
> Just to check, you've built 6f11f37459d8f, and then you cherry-picked
> 2f425cf5242a0 on top (not merged), and that already got you the warning
> flood?
Correct.
> I'm probably blind, but I'm really not seeing where this pile of
> properties is coming from. Can you pls also boot with drm.debug=0xe and
> attach full dmesg? Plus your .config please.
attached. dmesg.txt is 6f11f37459d8f and the other is 6f11f37459d8f +
2f425cf5242a0.
> Thanks, Daniel
Sebastian
[-- Attachment #2: config.xz --]
[-- Type: application/x-xz, Size: 30168 bytes --]
[-- Attachment #3: dmesg.txt.xz --]
[-- Type: application/x-xz, Size: 25228 bytes --]
[-- Attachment #4: dmesg-with-2f425cf5242a0.txt.xz --]
[-- Type: application/x-xz, Size: 28104 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-14 13:47 ` [Intel-gfx] " Sebastian Andrzej Siewior
@ 2021-10-19 12:24 ` Daniel Vetter
-1 siblings, 0 replies; 23+ messages in thread
From: Daniel Vetter @ 2021-10-19 12:24 UTC (permalink / raw)
To: Sebastian Andrzej Siewior
Cc: Daniel Vetter, dri-devel, Maarten Lankhorst, intel-gfx,
Maxime Ripard, Thomas Zimmermann, David Airlie, Jani Nikula,
Joonas Lahtinen, Rodrigo Vivi, Thomas Gleixner
On Thu, Oct 14, 2021 at 03:47:31PM +0200, Sebastian Andrzej Siewior wrote:
> On 2021-10-14 15:21:22 [+0200], Daniel Vetter wrote:
> > On Wed, Oct 13, 2021 at 07:35:48PM +0200, Sebastian Andrzej Siewior wrote:
> > > c7fcbf2513973 -> does not boot
> > > c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> > > 6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY
> > > 6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> >
> > Just to check, you've built 6f11f37459d8f, and then you cherry-picked
> > 2f425cf5242a0 on top (not merged), and that already got you the warning
> > flood?
>
> Correct.
>
> > I'm probably blind, but I'm really not seeing where this pile of
> > properties is coming from. Can you pls also boot with drm.debug=0xe and
> > attach full dmesg? Plus your .config please.
>
> attached. dmesg.txt is 6f11f37459d8f and the other is 6f11f37459d8f +
> 2f425cf5242a0.
Ah dmesg help me understand what's going on. Does the below patch help? If
it's this one that would also explain why intel CI hasn't hit it - it's a
leak between tests and we run them all individually instead of once at
boot-up.
Cheers, Daniel
diff --git a/drivers/gpu/drm/selftests/test-drm_damage_helper.c b/drivers/gpu/drm/selftests/test-drm_damage_helper.c
index 1c19a5d3eefb..8d8d8e214c28 100644
--- a/drivers/gpu/drm/selftests/test-drm_damage_helper.c
+++ b/drivers/gpu/drm/selftests/test-drm_damage_helper.c
@@ -30,6 +30,7 @@ static void mock_setup(struct drm_plane_state *state)
mock_device.driver = &mock_driver;
mock_device.mode_config.prop_fb_damage_clips = &mock_prop;
mock_plane.dev = &mock_device;
+ mock_obj_props.count = 0;
mock_plane.base.properties = &mock_obj_props;
mock_prop.base.id = 1; /* 0 is an invalid id */
mock_prop.dev = &mock_device;
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply related [flat|nested] 23+ messages in thread
* Re: [Intel-gfx] [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
@ 2021-10-19 12:24 ` Daniel Vetter
0 siblings, 0 replies; 23+ messages in thread
From: Daniel Vetter @ 2021-10-19 12:24 UTC (permalink / raw)
To: Sebastian Andrzej Siewior
Cc: Daniel Vetter, dri-devel, Maarten Lankhorst, intel-gfx,
Maxime Ripard, Thomas Zimmermann, David Airlie, Jani Nikula,
Joonas Lahtinen, Rodrigo Vivi, Thomas Gleixner
On Thu, Oct 14, 2021 at 03:47:31PM +0200, Sebastian Andrzej Siewior wrote:
> On 2021-10-14 15:21:22 [+0200], Daniel Vetter wrote:
> > On Wed, Oct 13, 2021 at 07:35:48PM +0200, Sebastian Andrzej Siewior wrote:
> > > c7fcbf2513973 -> does not boot
> > > c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> > > 6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY
> > > 6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
> >
> > Just to check, you've built 6f11f37459d8f, and then you cherry-picked
> > 2f425cf5242a0 on top (not merged), and that already got you the warning
> > flood?
>
> Correct.
>
> > I'm probably blind, but I'm really not seeing where this pile of
> > properties is coming from. Can you pls also boot with drm.debug=0xe and
> > attach full dmesg? Plus your .config please.
>
> attached. dmesg.txt is 6f11f37459d8f and the other is 6f11f37459d8f +
> 2f425cf5242a0.
Ah dmesg help me understand what's going on. Does the below patch help? If
it's this one that would also explain why intel CI hasn't hit it - it's a
leak between tests and we run them all individually instead of once at
boot-up.
Cheers, Daniel
diff --git a/drivers/gpu/drm/selftests/test-drm_damage_helper.c b/drivers/gpu/drm/selftests/test-drm_damage_helper.c
index 1c19a5d3eefb..8d8d8e214c28 100644
--- a/drivers/gpu/drm/selftests/test-drm_damage_helper.c
+++ b/drivers/gpu/drm/selftests/test-drm_damage_helper.c
@@ -30,6 +30,7 @@ static void mock_setup(struct drm_plane_state *state)
mock_device.driver = &mock_driver;
mock_device.mode_config.prop_fb_damage_clips = &mock_prop;
mock_plane.dev = &mock_device;
+ mock_obj_props.count = 0;
mock_plane.base.properties = &mock_obj_props;
mock_prop.base.id = 1; /* 0 is an invalid id */
mock_prop.dev = &mock_device;
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply related [flat|nested] 23+ messages in thread
* Re: [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
2021-10-19 12:24 ` [Intel-gfx] " Daniel Vetter
@ 2021-10-19 13:14 ` Sebastian Andrzej Siewior
-1 siblings, 0 replies; 23+ messages in thread
From: Sebastian Andrzej Siewior @ 2021-10-19 13:14 UTC (permalink / raw)
To: Daniel Vetter
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Jani Nikula, Joonas Lahtinen,
Rodrigo Vivi, Thomas Gleixner
On 2021-10-19 14:24:29 [+0200], Daniel Vetter wrote:
>
> Ah dmesg help me understand what's going on. Does the below patch help? If
> it's this one that would also explain why intel CI hasn't hit it - it's a
> leak between tests and we run them all individually instead of once at
> boot-up.
Yes, it does. Thank you.
Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Cheers, Daniel
Sebastian
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [Intel-gfx] [RFC PATCH] drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
@ 2021-10-19 13:14 ` Sebastian Andrzej Siewior
0 siblings, 0 replies; 23+ messages in thread
From: Sebastian Andrzej Siewior @ 2021-10-19 13:14 UTC (permalink / raw)
To: Daniel Vetter
Cc: dri-devel, Maarten Lankhorst, intel-gfx, Maxime Ripard,
Thomas Zimmermann, David Airlie, Jani Nikula, Joonas Lahtinen,
Rodrigo Vivi, Thomas Gleixner
On 2021-10-19 14:24:29 [+0200], Daniel Vetter wrote:
>
> Ah dmesg help me understand what's going on. Does the below patch help? If
> it's this one that would also explain why intel CI hasn't hit it - it's a
> leak between tests and we run them all individually instead of once at
> boot-up.
Yes, it does. Thank you.
Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Cheers, Daniel
Sebastian
^ permalink raw reply [flat|nested] 23+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: Increase DRM_OBJECT_MAX_PROPERTY by 18. (rev2)
2021-10-05 6:51 ` [Intel-gfx] " Sebastian Andrzej Siewior
` (4 preceding siblings ...)
(?)
@ 2021-10-19 17:25 ` Patchwork
-1 siblings, 0 replies; 23+ messages in thread
From: Patchwork @ 2021-10-19 17:25 UTC (permalink / raw)
To: Daniel Vetter; +Cc: intel-gfx
== Series Details ==
Series: drm: Increase DRM_OBJECT_MAX_PROPERTY by 18. (rev2)
URL : https://patchwork.freedesktop.org/series/95440/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
4252f133017b drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
-:8: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#8:
> > On Wed, Oct 13, 2021 at 07:35:48PM +0200, Sebastian Andrzej Siewior wrote:
-:9: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit c7fcbf251397 ("drm/plane: check that fb_damage is set up when used")'
#9:
> > > c7fcbf2513973 -> does not boot
-:10: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit c7fcbf251397 ("drm/plane: check that fb_damage is set up when used")'
#10:
> > > c7fcbf2513973 + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
-:11: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 6f11f37459d8 ("drm/plane: remove drm_helper_get_plane_damage_clips")'
#11:
> > > 6f11f37459d8f -> boots, 0 x DRM_OBJECT_MAX_PROPERTY
-:12: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 6f11f37459d8 ("drm/plane: remove drm_helper_get_plane_damage_clips")'
#12:
> > > 6f11f37459d8f + 2f425cf5242a0 -> boots, 18 x DRM_OBJECT_MAX_PROPERTY
-:15: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 2f425cf5242a ("drm: Fix oops in damage self-tests by mocking damage property")'
#15:
> > 2f425cf5242a0 on top (not merged), and that already got you the warning
-:24: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 6f11f37459d8 ("drm/plane: remove drm_helper_get_plane_damage_clips")'
#24:
> attached. dmesg.txt is 6f11f37459d8f and the other is 6f11f37459d8f +
-:46: ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 7 errors, 1 warnings, 0 checks, 7 lines checked
^ permalink raw reply [flat|nested] 23+ messages in thread* [Intel-gfx] ✗ Fi.CI.BAT: failure for drm: Increase DRM_OBJECT_MAX_PROPERTY by 18. (rev2)
2021-10-05 6:51 ` [Intel-gfx] " Sebastian Andrzej Siewior
` (5 preceding siblings ...)
(?)
@ 2021-10-19 17:59 ` Patchwork
-1 siblings, 0 replies; 23+ messages in thread
From: Patchwork @ 2021-10-19 17:59 UTC (permalink / raw)
To: Daniel Vetter; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 6699 bytes --]
== Series Details ==
Series: drm: Increase DRM_OBJECT_MAX_PROPERTY by 18. (rev2)
URL : https://patchwork.freedesktop.org/series/95440/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10762 -> Patchwork_21380
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_21380 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_21380, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_21380:
### IGT changes ###
#### Possible regressions ####
* igt@kms_force_connector_basic@force-edid:
- fi-skl-6700k2: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10762/fi-skl-6700k2/igt@kms_force_connector_basic@force-edid.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-skl-6700k2/igt@kms_force_connector_basic@force-edid.html
Known issues
------------
Here are the changes found in Patchwork_21380 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@query-info:
- fi-ilk-650: NOTRUN -> [SKIP][3] ([fdo#109271]) +35 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-ilk-650/igt@amdgpu/amd_basic@query-info.html
- fi-tgl-1115g4: NOTRUN -> [SKIP][4] ([fdo#109315])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-tgl-1115g4/igt@amdgpu/amd_basic@query-info.html
* igt@amdgpu/amd_cs_nop@nop-gfx0:
- fi-tgl-1115g4: NOTRUN -> [SKIP][5] ([fdo#109315] / [i915#2575]) +16 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-tgl-1115g4/igt@amdgpu/amd_cs_nop@nop-gfx0.html
* igt@gem_huc_copy@huc-copy:
- fi-tgl-1115g4: NOTRUN -> [SKIP][6] ([i915#2190])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-tgl-1115g4/igt@gem_huc_copy@huc-copy.html
* igt@i915_pm_backlight@basic-brightness:
- fi-tgl-1115g4: NOTRUN -> [SKIP][7] ([i915#1155])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-tgl-1115g4/igt@i915_pm_backlight@basic-brightness.html
* igt@i915_selftest@live@hangcheck:
- fi-snb-2600: [PASS][8] -> [INCOMPLETE][9] ([i915#3921])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10762/fi-snb-2600/igt@i915_selftest@live@hangcheck.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-snb-2600/igt@i915_selftest@live@hangcheck.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-tgl-1115g4: NOTRUN -> [SKIP][10] ([fdo#111827]) +8 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-tgl-1115g4/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@dp-hpd-fast:
- fi-ilk-650: NOTRUN -> [SKIP][11] ([fdo#109271] / [fdo#111827]) +8 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-ilk-650/igt@kms_chamelium@dp-hpd-fast.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-tgl-1115g4: NOTRUN -> [SKIP][12] ([i915#4103]) +1 similar issue
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-tgl-1115g4/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-1115g4: NOTRUN -> [SKIP][13] ([fdo#109285])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-tgl-1115g4/igt@kms_force_connector_basic@force-load-detect.html
* igt@kms_psr@primary_mmap_gtt:
- fi-tgl-1115g4: NOTRUN -> [SKIP][14] ([i915#1072]) +3 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-tgl-1115g4/igt@kms_psr@primary_mmap_gtt.html
* igt@prime_vgem@basic-userptr:
- fi-tgl-1115g4: NOTRUN -> [SKIP][15] ([i915#3301])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-tgl-1115g4/igt@prime_vgem@basic-userptr.html
#### Possible fixes ####
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [DMESG-WARN][16] ([i915#4269]) -> [PASS][17]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10762/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
#### Warnings ####
* igt@runner@aborted:
- fi-icl-u2: [FAIL][18] ([i915#3363]) -> [FAIL][19] ([i915#3363] / [i915#4312])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10762/fi-icl-u2/igt@runner@aborted.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/fi-icl-u2/igt@runner@aborted.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
Participating hosts (36 -> 36)
------------------------------
Additional (2): fi-tgl-1115g4 fi-ilk-650
Missing (2): fi-bsw-cyan bat-dg1-6
Build changes
-------------
* Linux: CI_DRM_10762 -> Patchwork_21380
CI-20190529: 20190529
CI_DRM_10762: 448b23374caeafa59d2a057fdc1a7c069b934960 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6255: 9b0881254557edeaf273b2196309fc4e22ea0312 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21380: 4252f133017b64c8bf39ca0674b15f35361ec997 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
4252f133017b drm: Increase DRM_OBJECT_MAX_PROPERTY by 18.
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21380/index.html
[-- Attachment #2: Type: text/html, Size: 7934 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread