* [PATCH 0/1] drm/i915/active: Fix misuse of non-idle barriers as fence trackers
@ 2023-02-13 13:05 ` Janusz Krzysztofik
0 siblings, 0 replies; 8+ messages in thread
From: Janusz Krzysztofik @ 2023-02-13 13:05 UTC (permalink / raw)
To: intel-gfx, Tvrtko Ursulin
Cc: Andrzej Hajda, Gwan-gyeong Mun, dri-devel, Andi Shyti,
Rodrigo Vivi, Janusz Krzysztofik, Chris Wilson, Nirmoy Das
Test-with: <20230213095040.13457-2-janusz.krzysztofik@linux.intel.com>
Users reported oopses on list corruptions when using i915 perf with a
number of concurrently running graphics applications. Root cause analysis
pointed out to an issue in barrier processing code -- a race among perf
open / close replacing active barriers with perf requests on kernel
contexts and concurrent barrier preallocate / acquire operations performed
during user context first pin / last unpin.
Respect results of barrier deletion attempts -- mark the barrier as idle
only after successfully deleted from the list. Then, before proceeding
with setting our fence as the one currently tracked, make sure that the
tracker we've got is not a non-idle barrier. If that check fails, don't
use that tracker but go back and try to acquire a new, usable one.
Note:
I'm submitting this fix with a request to CI for testing it with a new
subtest igt@gem_barrier_race@remote-request, developed for that case,
not yet in upstream IGT. I've selected trybot submission of the test,
with the test added to BAT testlist, to get results from the widest
possible HW range.
Janusz Krzysztofik (1):
drm/i915/active: Fix misuse of non-idle barriers as fence trackers
drivers/gpu/drm/i915/i915_active.c | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
--
2.25.1
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Intel-gfx] [PATCH 0/1] drm/i915/active: Fix misuse of non-idle barriers as fence trackers
@ 2023-02-13 13:05 ` Janusz Krzysztofik
0 siblings, 0 replies; 8+ messages in thread
From: Janusz Krzysztofik @ 2023-02-13 13:05 UTC (permalink / raw)
To: intel-gfx, Tvrtko Ursulin
Cc: Andrzej Hajda, dri-devel, Rodrigo Vivi, Chris Wilson, Nirmoy Das
Test-with: <20230213095040.13457-2-janusz.krzysztofik@linux.intel.com>
Users reported oopses on list corruptions when using i915 perf with a
number of concurrently running graphics applications. Root cause analysis
pointed out to an issue in barrier processing code -- a race among perf
open / close replacing active barriers with perf requests on kernel
contexts and concurrent barrier preallocate / acquire operations performed
during user context first pin / last unpin.
Respect results of barrier deletion attempts -- mark the barrier as idle
only after successfully deleted from the list. Then, before proceeding
with setting our fence as the one currently tracked, make sure that the
tracker we've got is not a non-idle barrier. If that check fails, don't
use that tracker but go back and try to acquire a new, usable one.
Note:
I'm submitting this fix with a request to CI for testing it with a new
subtest igt@gem_barrier_race@remote-request, developed for that case,
not yet in upstream IGT. I've selected trybot submission of the test,
with the test added to BAT testlist, to get results from the widest
possible HW range.
Janusz Krzysztofik (1):
drm/i915/active: Fix misuse of non-idle barriers as fence trackers
drivers/gpu/drm/i915/i915_active.c | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
--
2.25.1
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH 1/1] drm/i915/active: Fix misuse of non-idle barriers as fence trackers
2023-02-13 13:05 ` [Intel-gfx] " Janusz Krzysztofik
@ 2023-02-13 13:05 ` Janusz Krzysztofik
-1 siblings, 0 replies; 8+ messages in thread
From: Janusz Krzysztofik @ 2023-02-13 13:05 UTC (permalink / raw)
To: intel-gfx, Tvrtko Ursulin
Cc: Andrzej Hajda, Gwan-gyeong Mun, dri-devel, Andi Shyti,
Rodrigo Vivi, Janusz Krzysztofik, Chris Wilson, Nirmoy Das
Users reported oopses on list corruptions when using i915 perf with a
number of concurrently running graphics applications. Root cause analysis
pointed out to an issue in barrier processing code -- a race among perf
open / close replacing active barriers with perf requests on kernel
contexts and concurrent barrier preallocate / acquire operations performed
during user context first pin / last unpin.
When adding a request to a composite tracker, we try to use an existing
fence tracker already registered with that composite tracker. The tracker
we obtain can already track another fence, can be an idle barrier, or an
active barrier. The first two cases seem easy to handle and we seem to
do that correctly. In the last case, we attempt to replace the active
barrier with our request. However, when the tracker occurs a barrier
and we try to delete that barrier from a list of barrier tasks it belongs
to, we ignore return value from that operation, which informs us whether
the deletion succeeded or not, and we reuse the barrier as if it was
idle.
On the other side, barriers are now deleted from a barrier tasks list by
temporarily removing the list content, traversing that content with skip
over the node to be deleted, then adding the modified content back to the
list. Since that complex operation is not serialized with other
concurrent uses of the list, including similar barrier deletions,
functions that depend on the list being either empty or not empty can take
wrong decisions.
A failed barrier deletion can be a side effect of the way we have it
implemented -- another thread can have temporarily emptied the list before
we manage to do that. If we ignore such failure, that other thread can
then add our fence tracker back to the barrier tasks list. Since the same
structure field of the tracker is used as a list node with both barrier
tasks lists and fence callback lists, list corruption occurs. However,
list corruptions were still observed when running the user workload on top
of an experimental patch that serialized all operations on barrier tasks
lists with a spinlock. Then, other race scenarios leading to list
corruptions likely exist.
Based on those observations, respecting the return code from barrier
deletion seems required for effectively fixing the issue. However, we
need to handle those few above mentioned cases carefully.
Respect results of barrier deletion attempts -- mark the barrier as idle
only after successfully deleted from the list. Then, before proceeding
with setting our fence as the one currently tracked, make sure that the
tracker we've got is not a non-idle barrier. If that check fails, don't
use that tracker but go back and try to acquire a new, usable one.
Extensive testing shows that this patch effectively fixes barrier related
list corruptions. However, other potentially related issues have been
observed, reported by a new subtest we have developed for this case,
with this fix applied. Then, we may still want to get back to this soon
and refactor our intentionally racy but potentially fragile way of barrier
tasks lists handling.
Fixes: d8af05ff38ae ("drm/i915: Allow sharing the idle-barrier from other kernel requests")
References: https://gitlab.freedesktop.org/drm/intel/-/issues/6333
Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: stable@vger.kernel.org # v5.4
---
drivers/gpu/drm/i915/i915_active.c | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c
index 7412abf166a8c..f9282b8c87c1c 100644
--- a/drivers/gpu/drm/i915/i915_active.c
+++ b/drivers/gpu/drm/i915/i915_active.c
@@ -422,12 +422,12 @@ replace_barrier(struct i915_active *ref, struct i915_active_fence *active)
* we can use it to substitute for the pending idle-barrer
* request that we want to emit on the kernel_context.
*/
- __active_del_barrier(ref, node_from_active(active));
- return true;
+ return __active_del_barrier(ref, node_from_active(active));
}
int i915_active_add_request(struct i915_active *ref, struct i915_request *rq)
{
+ u64 idx = i915_request_timeline(rq)->fence_context;
struct dma_fence *fence = &rq->fence;
struct i915_active_fence *active;
int err;
@@ -437,16 +437,19 @@ int i915_active_add_request(struct i915_active *ref, struct i915_request *rq)
if (err)
return err;
- active = active_instance(ref, i915_request_timeline(rq)->fence_context);
- if (!active) {
- err = -ENOMEM;
- goto out;
- }
+ do {
+ active = active_instance(ref, idx);
+ if (!active) {
+ err = -ENOMEM;
+ goto out;
+ }
+
+ if (replace_barrier(ref, active)) {
+ RCU_INIT_POINTER(active->fence, NULL);
+ atomic_dec(&ref->count);
+ }
+ } while (is_barrier(active));
- if (replace_barrier(ref, active)) {
- RCU_INIT_POINTER(active->fence, NULL);
- atomic_dec(&ref->count);
- }
if (!__i915_active_fence_set(active, fence))
__i915_active_acquire(ref);
--
2.25.1
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [Intel-gfx] [PATCH 1/1] drm/i915/active: Fix misuse of non-idle barriers as fence trackers
@ 2023-02-13 13:05 ` Janusz Krzysztofik
0 siblings, 0 replies; 8+ messages in thread
From: Janusz Krzysztofik @ 2023-02-13 13:05 UTC (permalink / raw)
To: intel-gfx, Tvrtko Ursulin
Cc: Andrzej Hajda, dri-devel, Rodrigo Vivi, Chris Wilson, Nirmoy Das
Users reported oopses on list corruptions when using i915 perf with a
number of concurrently running graphics applications. Root cause analysis
pointed out to an issue in barrier processing code -- a race among perf
open / close replacing active barriers with perf requests on kernel
contexts and concurrent barrier preallocate / acquire operations performed
during user context first pin / last unpin.
When adding a request to a composite tracker, we try to use an existing
fence tracker already registered with that composite tracker. The tracker
we obtain can already track another fence, can be an idle barrier, or an
active barrier. The first two cases seem easy to handle and we seem to
do that correctly. In the last case, we attempt to replace the active
barrier with our request. However, when the tracker occurs a barrier
and we try to delete that barrier from a list of barrier tasks it belongs
to, we ignore return value from that operation, which informs us whether
the deletion succeeded or not, and we reuse the barrier as if it was
idle.
On the other side, barriers are now deleted from a barrier tasks list by
temporarily removing the list content, traversing that content with skip
over the node to be deleted, then adding the modified content back to the
list. Since that complex operation is not serialized with other
concurrent uses of the list, including similar barrier deletions,
functions that depend on the list being either empty or not empty can take
wrong decisions.
A failed barrier deletion can be a side effect of the way we have it
implemented -- another thread can have temporarily emptied the list before
we manage to do that. If we ignore such failure, that other thread can
then add our fence tracker back to the barrier tasks list. Since the same
structure field of the tracker is used as a list node with both barrier
tasks lists and fence callback lists, list corruption occurs. However,
list corruptions were still observed when running the user workload on top
of an experimental patch that serialized all operations on barrier tasks
lists with a spinlock. Then, other race scenarios leading to list
corruptions likely exist.
Based on those observations, respecting the return code from barrier
deletion seems required for effectively fixing the issue. However, we
need to handle those few above mentioned cases carefully.
Respect results of barrier deletion attempts -- mark the barrier as idle
only after successfully deleted from the list. Then, before proceeding
with setting our fence as the one currently tracked, make sure that the
tracker we've got is not a non-idle barrier. If that check fails, don't
use that tracker but go back and try to acquire a new, usable one.
Extensive testing shows that this patch effectively fixes barrier related
list corruptions. However, other potentially related issues have been
observed, reported by a new subtest we have developed for this case,
with this fix applied. Then, we may still want to get back to this soon
and refactor our intentionally racy but potentially fragile way of barrier
tasks lists handling.
Fixes: d8af05ff38ae ("drm/i915: Allow sharing the idle-barrier from other kernel requests")
References: https://gitlab.freedesktop.org/drm/intel/-/issues/6333
Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: stable@vger.kernel.org # v5.4
---
drivers/gpu/drm/i915/i915_active.c | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c
index 7412abf166a8c..f9282b8c87c1c 100644
--- a/drivers/gpu/drm/i915/i915_active.c
+++ b/drivers/gpu/drm/i915/i915_active.c
@@ -422,12 +422,12 @@ replace_barrier(struct i915_active *ref, struct i915_active_fence *active)
* we can use it to substitute for the pending idle-barrer
* request that we want to emit on the kernel_context.
*/
- __active_del_barrier(ref, node_from_active(active));
- return true;
+ return __active_del_barrier(ref, node_from_active(active));
}
int i915_active_add_request(struct i915_active *ref, struct i915_request *rq)
{
+ u64 idx = i915_request_timeline(rq)->fence_context;
struct dma_fence *fence = &rq->fence;
struct i915_active_fence *active;
int err;
@@ -437,16 +437,19 @@ int i915_active_add_request(struct i915_active *ref, struct i915_request *rq)
if (err)
return err;
- active = active_instance(ref, i915_request_timeline(rq)->fence_context);
- if (!active) {
- err = -ENOMEM;
- goto out;
- }
+ do {
+ active = active_instance(ref, idx);
+ if (!active) {
+ err = -ENOMEM;
+ goto out;
+ }
+
+ if (replace_barrier(ref, active)) {
+ RCU_INIT_POINTER(active->fence, NULL);
+ atomic_dec(&ref->count);
+ }
+ } while (is_barrier(active));
- if (replace_barrier(ref, active)) {
- RCU_INIT_POINTER(active->fence, NULL);
- atomic_dec(&ref->count);
- }
if (!__i915_active_fence_set(active, fence))
__i915_active_acquire(ref);
--
2.25.1
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/active: Fix misuse of non-idle barriers as fence trackers
2023-02-13 13:05 ` [Intel-gfx] " Janusz Krzysztofik
(?)
(?)
@ 2023-02-13 13:47 ` Patchwork
2023-02-13 15:12 ` [Intel-gfx] " Janusz Krzysztofik
-1 siblings, 1 reply; 8+ messages in thread
From: Patchwork @ 2023-02-13 13:47 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 5423 bytes --]
== Series Details ==
Series: drm/i915/active: Fix misuse of non-idle barriers as fence trackers
URL : https://patchwork.freedesktop.org/series/113950/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12730 -> Patchwork_113950v1
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/index.html
Participating hosts (40 -> 37)
------------------------------
Missing (3): fi-tgl-1115g4 bat-atsm-1 fi-snb-2520m
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_113950v1:
### IGT changes ###
#### Possible regressions ####
* {igt@gem_barrier_race@remote-request@rcs0} (NEW):
- fi-rkl-11600: NOTRUN -> [ABORT][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-rkl-11600/igt@gem_barrier_race@remote-request@rcs0.html
- bat-dg1-5: NOTRUN -> [ABORT][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/bat-dg1-5/igt@gem_barrier_race@remote-request@rcs0.html
- {bat-adlm-1}: NOTRUN -> [DMESG-WARN][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/bat-adlm-1/igt@gem_barrier_race@remote-request@rcs0.html
New tests
---------
New tests have been introduced between CI_DRM_12730 and Patchwork_113950v1:
### New IGT tests (2) ###
* igt@gem_barrier_race@remote-request:
- Statuses :
- Exec time: [None] s
* igt@gem_barrier_race@remote-request@rcs0:
- Statuses : 2 abort(s) 1 dmesg-warn(s) 27 pass(s) 5 skip(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_113950v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* {igt@gem_barrier_race@remote-request@rcs0} (NEW):
- fi-pnv-d510: NOTRUN -> [SKIP][4] ([fdo#109271])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-pnv-d510/igt@gem_barrier_race@remote-request@rcs0.html
- fi-blb-e6850: NOTRUN -> [SKIP][5] ([fdo#109271])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-blb-e6850/igt@gem_barrier_race@remote-request@rcs0.html
- fi-ivb-3770: NOTRUN -> [SKIP][6] ([fdo#109271])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-ivb-3770/igt@gem_barrier_race@remote-request@rcs0.html
- fi-elk-e7500: NOTRUN -> [SKIP][7] ([fdo#109271])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-elk-e7500/igt@gem_barrier_race@remote-request@rcs0.html
- fi-ilk-650: NOTRUN -> [SKIP][8] ([fdo#109271])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-ilk-650/igt@gem_barrier_race@remote-request@rcs0.html
#### Possible fixes ####
* igt@i915_selftest@live@gt_heartbeat:
- fi-apl-guc: [DMESG-FAIL][9] ([i915#5334]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
* igt@i915_selftest@live@requests:
- {bat-rpls-2}: [ABORT][11] ([i915#7982]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/bat-rpls-2/igt@i915_selftest@live@requests.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/bat-rpls-2/igt@i915_selftest@live@requests.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions:
- fi-bsw-n3050: [FAIL][13] ([i915#6298]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions.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
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#6298]: https://gitlab.freedesktop.org/drm/intel/issues/6298
[i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
[i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699
[i915#7982]: https://gitlab.freedesktop.org/drm/intel/issues/7982
[i915#7996]: https://gitlab.freedesktop.org/drm/intel/issues/7996
Build changes
-------------
* IGT: IGT_7157 -> TrybotIGT_706
* Linux: CI_DRM_12730 -> Patchwork_113950v1
CI-20190529: 20190529
CI_DRM_12730: c54b5fcf3e686a0abfdd7d6af53e9014c137023a @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7157: 96d12fdc942cee9526a951b377b195ca9c8276b1 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_113950v1: c54b5fcf3e686a0abfdd7d6af53e9014c137023a @ git://anongit.freedesktop.org/gfx-ci/linux
TrybotIGT_706: https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_706/index.html
### Linux commits
44de67f6c674 drm/i915/active: Fix misuse of non-idle barriers as fence trackers
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/index.html
[-- Attachment #2: Type: text/html, Size: 6328 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/active: Fix misuse of non-idle barriers as fence trackers
2023-02-13 13:05 ` [Intel-gfx] " Janusz Krzysztofik
` (2 preceding siblings ...)
(?)
@ 2023-02-13 14:57 ` Patchwork
-1 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2023-02-13 14:57 UTC (permalink / raw)
To: Janusz Krzysztofik; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 32949 bytes --]
== Series Details ==
Series: drm/i915/active: Fix misuse of non-idle barriers as fence trackers
URL : https://patchwork.freedesktop.org/series/113950/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12730_full -> Patchwork_113950v1_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/index.html
Participating hosts (9 -> 10)
------------------------------
Additional (1): shard-tglu-9
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_113950v1_full:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* {igt@kms_draw_crc@draw-method-mmap-gtt}:
- {shard-dg1}: NOTRUN -> [SKIP][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-dg1-17/igt@kms_draw_crc@draw-method-mmap-gtt.html
* {igt@kms_plane_scaling@invalid-parameters}:
- {shard-rkl}: [SKIP][2] ([i915#8152]) -> [SKIP][3]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-3/igt@kms_plane_scaling@invalid-parameters.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-5/igt@kms_plane_scaling@invalid-parameters.html
New tests
---------
New tests have been introduced between CI_DRM_12730_full and Patchwork_113950v1_full:
### New IGT tests (11) ###
* igt@gem_barrier_race@remote-request:
- Statuses :
- Exec time: [None] s
* igt@gem_barrier_race@remote-request@rcs0:
- Statuses : 4 pass(s) 1 skip(s)
- Exec time: [0.0] s
* igt@kms_cursor_edge_walk@128x128-right-edge@pipe-a-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s
* igt@kms_cursor_edge_walk@128x128-right-edge@pipe-d-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s
* igt@kms_cursor_edge_walk@128x128-top-bottom@pipe-d-hdmi-a-1:
- Statuses : 1 pass(s)
- Exec time: [0.0] s
* igt@kms_cursor_edge_walk@64x64-left-edge@pipe-b-edp-1:
- Statuses : 1 pass(s)
- Exec time: [0.0] s
* igt@kms_cursor_edge_walk@64x64-left-edge@pipe-d-hdmi-a-1:
- Statuses : 1 pass(s)
- Exec time: [0.0] s
* igt@kms_cursor_edge_walk@64x64-right-edge@pipe-a-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s
* igt@kms_cursor_edge_walk@64x64-right-edge@pipe-d-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s
* igt@kms_cursor_edge_walk@64x64-top-bottom@pipe-a-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s
* igt@kms_cursor_edge_walk@64x64-top-bottom@pipe-d-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_113950v1_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_eio@in-flight-contexts-10ms:
- shard-apl: NOTRUN -> [TIMEOUT][4] ([i915#3063])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl2/igt@gem_eio@in-flight-contexts-10ms.html
* igt@gem_exec_capture@capture-invisible@smem0:
- shard-apl: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#6334])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl7/igt@gem_exec_capture@capture-invisible@smem0.html
* igt@gem_exec_fair@basic-deadline:
- shard-apl: NOTRUN -> [FAIL][6] ([i915#2846])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl4/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-apl: NOTRUN -> [FAIL][7] ([i915#2842])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl2/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-glk: [PASS][8] -> [FAIL][9] ([i915#2842])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-glk6/igt@gem_exec_fair@basic-pace@rcs0.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk6/igt@gem_exec_fair@basic-pace@rcs0.html
* igt@gem_huc_copy@huc-copy:
- shard-apl: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#2190])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl1/igt@gem_huc_copy@huc-copy.html
* igt@gem_lmem_swapping@smem-oom:
- shard-apl: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613]) +20 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl1/igt@gem_lmem_swapping@smem-oom.html
* igt@gem_pread@exhaustion:
- shard-apl: NOTRUN -> [WARN][12] ([i915#2658]) +1 similar issue
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl1/igt@gem_pread@exhaustion.html
* igt@gem_render_copy@x-tiled-to-vebox-yf-tiled:
- shard-apl: NOTRUN -> [SKIP][13] ([fdo#109271]) +1261 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl4/igt@gem_render_copy@x-tiled-to-vebox-yf-tiled.html
* igt@gem_userptr_blits@dmabuf-sync:
- shard-apl: NOTRUN -> [SKIP][14] ([fdo#109271] / [i915#3323])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl1/igt@gem_userptr_blits@dmabuf-sync.html
* igt@gem_userptr_blits@vma-merge:
- shard-apl: NOTRUN -> [FAIL][15] ([i915#3318])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl4/igt@gem_userptr_blits@vma-merge.html
* igt@i915_pipe_stress@stress-xrgb8888-ytiled:
- shard-apl: NOTRUN -> [FAIL][16] ([i915#7036]) +1 similar issue
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl6/igt@i915_pipe_stress@stress-xrgb8888-ytiled.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-apl: NOTRUN -> [SKIP][17] ([fdo#109271] / [i915#1937])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl4/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp.html
* igt@kms_atomic@plane-primary-overlay-mutable-zpos:
- shard-glk: NOTRUN -> [SKIP][18] ([fdo#109271]) +24 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk6/igt@kms_atomic@plane-primary-overlay-mutable-zpos.html
* igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][19] ([fdo#109271] / [i915#3886]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk3/igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][20] ([fdo#109271] / [i915#3886]) +53 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl2/igt@kms_ccs@pipe-b-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_content_protection@lic@pipe-a-dp-1:
- shard-apl: NOTRUN -> [TIMEOUT][21] ([i915#7173]) +4 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl6/igt@kms_content_protection@lic@pipe-a-dp-1.html
* igt@kms_content_protection@uevent@pipe-a-dp-1:
- shard-apl: NOTRUN -> [FAIL][22] ([i915#1339])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl1/igt@kms_content_protection@uevent@pipe-a-dp-1.html
* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size:
- shard-apl: NOTRUN -> [FAIL][23] ([i915#2346]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl7/igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size.html
* igt@kms_plane_alpha_blend@alpha-basic@pipe-a-dp-1:
- shard-apl: NOTRUN -> [FAIL][24] ([i915#7862]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl4/igt@kms_plane_alpha_blend@alpha-basic@pipe-a-dp-1.html
* igt@kms_plane_alpha_blend@alpha-opaque-fb@pipe-a-dp-1:
- shard-apl: NOTRUN -> [FAIL][25] ([i915#4573]) +5 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl2/igt@kms_plane_alpha_blend@alpha-opaque-fb@pipe-a-dp-1.html
* igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-a-vga-1:
- shard-snb: NOTRUN -> [SKIP][26] ([fdo#109271]) +27 similar issues
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-snb4/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-a-vga-1.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-big-fb:
- shard-apl: NOTRUN -> [SKIP][27] ([fdo#109271] / [i915#658]) +17 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl7/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-big-fb.html
* igt@kms_psr2_su@frontbuffer-xrgb8888:
- shard-glk: NOTRUN -> [SKIP][28] ([fdo#109271] / [i915#658])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk7/igt@kms_psr2_su@frontbuffer-xrgb8888.html
* igt@kms_vblank@pipe-d-wait-idle:
- shard-apl: NOTRUN -> [SKIP][29] ([fdo#109271] / [i915#533])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl4/igt@kms_vblank@pipe-d-wait-idle.html
* igt@kms_writeback@writeback-pixel-formats:
- shard-apl: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#2437]) +3 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-apl7/igt@kms_writeback@writeback-pixel-formats.html
#### Possible fixes ####
* igt@drm_fdinfo@most-busy-check-all@rcs0:
- {shard-rkl}: [FAIL][31] ([i915#7742]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-1/igt@drm_fdinfo@most-busy-check-all@rcs0.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-4/igt@drm_fdinfo@most-busy-check-all@rcs0.html
* igt@drm_read@short-buffer-block:
- {shard-rkl}: [SKIP][33] ([i915#4098]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-1/igt@drm_read@short-buffer-block.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-6/igt@drm_read@short-buffer-block.html
* igt@fbdev@unaligned-read:
- {shard-rkl}: [SKIP][35] ([i915#2582]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-1/igt@fbdev@unaligned-read.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-6/igt@fbdev@unaligned-read.html
* igt@gem_ctx_exec@basic-nohangcheck:
- {shard-tglu}: [FAIL][37] ([i915#6268]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-tglu-5/igt@gem_ctx_exec@basic-nohangcheck.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-tglu-8/igt@gem_ctx_exec@basic-nohangcheck.html
* igt@gem_ctx_persistence@hang:
- {shard-rkl}: [SKIP][39] ([i915#6252]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-5/igt@gem_ctx_persistence@hang.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-3/igt@gem_ctx_persistence@hang.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [FAIL][41] ([i915#2842]) -> [PASS][42] +2 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-glk2/igt@gem_exec_fair@basic-throttle@rcs0.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk9/igt@gem_exec_fair@basic-throttle@rcs0.html
- {shard-rkl}: [FAIL][43] ([i915#2842]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-5/igt@gem_exec_fair@basic-throttle@rcs0.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-5/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@gem_exec_reloc@basic-wc-read-noreloc:
- {shard-rkl}: [SKIP][45] ([i915#3281]) -> [PASS][46] +9 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-4/igt@gem_exec_reloc@basic-wc-read-noreloc.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-5/igt@gem_exec_reloc@basic-wc-read-noreloc.html
* igt@gem_exec_reloc@basic-write-read:
- shard-glk: [TIMEOUT][47] ([i915#8167]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-glk6/igt@gem_exec_reloc@basic-write-read.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk1/igt@gem_exec_reloc@basic-write-read.html
* igt@gem_partial_pwrite_pread@write:
- {shard-rkl}: [SKIP][49] ([i915#3282]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-4/igt@gem_partial_pwrite_pread@write.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-5/igt@gem_partial_pwrite_pread@write.html
* igt@gen9_exec_parse@bb-start-out:
- {shard-rkl}: [SKIP][51] ([i915#2527]) -> [PASS][52] +3 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-4/igt@gen9_exec_parse@bb-start-out.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-5/igt@gen9_exec_parse@bb-start-out.html
* igt@i915_pm_rpm@dpms-mode-unset-lpsp:
- {shard-tglu}: [SKIP][53] ([i915#1397]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-tglu-6/igt@i915_pm_rpm@dpms-mode-unset-lpsp.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-tglu-3/igt@i915_pm_rpm@dpms-mode-unset-lpsp.html
* igt@kms_big_fb@y-tiled-addfb-size-offset-overflow:
- {shard-rkl}: [SKIP][55] ([i915#1845] / [i915#4098]) -> [PASS][56] +9 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-3/igt@kms_big_fb@y-tiled-addfb-size-offset-overflow.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-6/igt@kms_big_fb@y-tiled-addfb-size-offset-overflow.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip:
- {shard-tglu}: [SKIP][57] ([i915#1845] / [i915#7651]) -> [PASS][58] +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-tglu-6/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-tglu-8/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
* igt@kms_ccs@pipe-d-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc:
- {shard-tglu}: [SKIP][59] ([i915#7651]) -> [PASS][60] +2 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-tglu-6/igt@kms_ccs@pipe-d-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-tglu-1/igt@kms_ccs@pipe-d-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size:
- shard-glk: [FAIL][61] ([i915#2346]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-glk4/igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk7/igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size.html
* igt@kms_draw_crc@fill-fb:
- {shard-tglu}: [SKIP][63] ([i915#1845]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-tglu-6/igt@kms_draw_crc@fill-fb.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-tglu-4/igt@kms_draw_crc@fill-fb.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc:
- {shard-rkl}: [SKIP][65] ([i915#1849] / [i915#4098]) -> [PASS][66] +7 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbc-badstride:
- {shard-tglu}: [SKIP][67] ([i915#1849]) -> [PASS][68] +3 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-tglu-6/igt@kms_frontbuffer_tracking@fbc-badstride.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-tglu-4/igt@kms_frontbuffer_tracking@fbc-badstride.html
* igt@kms_psr@suspend:
- {shard-rkl}: [SKIP][69] ([i915#1072]) -> [PASS][70] +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-5/igt@kms_psr@suspend.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-6/igt@kms_psr@suspend.html
* igt@kms_universal_plane@universal-plane-pipe-a-sanity:
- {shard-rkl}: [SKIP][71] ([i915#1845] / [i915#4070] / [i915#4098]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-1/igt@kms_universal_plane@universal-plane-pipe-a-sanity.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-6/igt@kms_universal_plane@universal-plane-pipe-a-sanity.html
* igt@perf@enable-disable:
- shard-glk: [TIMEOUT][73] ([i915#6943]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-glk6/igt@perf@enable-disable.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk7/igt@perf@enable-disable.html
* igt@perf@polling-small-buf:
- {shard-rkl}: [FAIL][75] ([i915#1722]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-3/igt@perf@polling-small-buf.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-5/igt@perf@polling-small-buf.html
* igt@prime_vgem@basic-write:
- {shard-rkl}: [SKIP][77] ([fdo#109295] / [i915#3291] / [i915#3708]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-rkl-4/igt@prime_vgem@basic-write.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-rkl-5/igt@prime_vgem@basic-write.html
* igt@syncobj_wait@invalid-signal-bad-pad:
- shard-glk: [TIMEOUT][79] ([i915#7900]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-glk6/igt@syncobj_wait@invalid-signal-bad-pad.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk3/igt@syncobj_wait@invalid-signal-bad-pad.html
#### Warnings ####
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-spr-indfb-draw-render:
- shard-glk: [TIMEOUT][81] ([i915#8056]) -> [SKIP][82] ([fdo#109271])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-glk6/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-spr-indfb-draw-render.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk9/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-spr-indfb-draw-render.html
* igt@kms_psr@psr2_primary_render:
- shard-glk: [TIMEOUT][83] ([i915#8162]) -> [SKIP][84] ([fdo#109271])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/shard-glk6/igt@kms_psr@psr2_primary_render.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/shard-glk8/igt@kms_psr@psr2_primary_render.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#109302]: https://bugs.freedesktop.org/show_bug.cgi?id=109302
[fdo#109307]: https://bugs.freedesktop.org/show_bug.cgi?id=109307
[fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309
[fdo#109312]: https://bugs.freedesktop.org/show_bug.cgi?id=109312
[fdo#109313]: https://bugs.freedesktop.org/show_bug.cgi?id=109313
[fdo#109314]: https://bugs.freedesktop.org/show_bug.cgi?id=109314
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#109506]: https://bugs.freedesktop.org/show_bug.cgi?id=109506
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#110542]: https://bugs.freedesktop.org/show_bug.cgi?id=110542
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111644]: https://bugs.freedesktop.org/show_bug.cgi?id=111644
[fdo#111656]: https://bugs.freedesktop.org/show_bug.cgi?id=111656
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112054]: https://bugs.freedesktop.org/show_bug.cgi?id=112054
[fdo#112283]: https://bugs.freedesktop.org/show_bug.cgi?id=112283
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1257]: https://gitlab.freedesktop.org/drm/intel/issues/1257
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1339]: https://gitlab.freedesktop.org/drm/intel/issues/1339
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1722]: https://gitlab.freedesktop.org/drm/intel/issues/1722
[i915#1755]: https://gitlab.freedesktop.org/drm/intel/issues/1755
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1850]: https://gitlab.freedesktop.org/drm/intel/issues/1850
[i915#1902]: https://gitlab.freedesktop.org/drm/intel/issues/1902
[i915#1937]: https://gitlab.freedesktop.org/drm/intel/issues/1937
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2433]: https://gitlab.freedesktop.org/drm/intel/issues/2433
[i915#2434]: https://gitlab.freedesktop.org/drm/intel/issues/2434
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2705]: https://gitlab.freedesktop.org/drm/intel/issues/2705
[i915#280]: https://gitlab.freedesktop.org/drm/intel/issues/280
[i915#284]: https://gitlab.freedesktop.org/drm/intel/issues/284
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#3063]: https://gitlab.freedesktop.org/drm/intel/issues/3063
[i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116
[i915#315]: https://gitlab.freedesktop.org/drm/intel/issues/315
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3299]: https://gitlab.freedesktop.org/drm/intel/issues/3299
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3318]: https://gitlab.freedesktop.org/drm/intel/issues/3318
[i915#3323]: https://gitlab.freedesktop.org/drm/intel/issues/3323
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3361]: https://gitlab.freedesktop.org/drm/intel/issues/3361
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3469]: https://gitlab.freedesktop.org/drm/intel/issues/3469
[i915#3528]: https://gitlab.freedesktop.org/drm/intel/issues/3528
[i915#3539]: https://gitlab.freedesktop.org/drm/intel/issues/3539
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3547]: https://gitlab.freedesktop.org/drm/intel/issues/3547
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3639]: https://gitlab.freedesktop.org/drm/intel/issues/3639
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3742]: https://gitlab.freedesktop.org/drm/intel/issues/3742
[i915#3743]: https://gitlab.freedesktop.org/drm/intel/issues/3743
[i915#3840]: https://gitlab.freedesktop.org/drm/intel/issues/3840
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#404]: https://gitlab.freedesktop.org/drm/intel/issues/404
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[i915#426]: https://gitlab.freedesktop.org/drm/intel/issues/426
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4281]: https://gitlab.freedesktop.org/drm/intel/issues/4281
[i915#4349]: https://gitlab.freedesktop.org/drm/intel/issues/4349
[i915#4391]: https://gitlab.freedesktop.org/drm/intel/issues/4391
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#4565]: https://gitlab.freedesktop.org/drm/intel/issues/4565
[i915#4573]: https://gitlab.freedesktop.org/drm/intel/issues/4573
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4771]: https://gitlab.freedesktop.org/drm/intel/issues/4771
[i915#4812]: https://gitlab.freedesktop.org/drm/intel/issues/4812
[i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833
[i915#4852]: https://gitlab.freedesktop.org/drm/intel/issues/4852
[i915#4854]: https://gitlab.freedesktop.org/drm/intel/issues/4854
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#4885]: https://gitlab.freedesktop.org/drm/intel/issues/4885
[i915#4958]: https://gitlab.freedesktop.org/drm/intel/issues/4958
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#5115]: https://gitlab.freedesktop.org/drm/intel/issues/5115
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5288]: https://gitlab.freedesktop.org/drm/intel/issues/5288
[i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289
[i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439
[i915#5563]: https://gitlab.freedesktop.org/drm/intel/issues/5563
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5723]: https://gitlab.freedesktop.org/drm/intel/issues/5723
[i915#5784]: https://gitlab.freedesktop.org/drm/intel/issues/5784
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6117]: https://gitlab.freedesktop.org/drm/intel/issues/6117
[i915#6227]: https://gitlab.freedesktop.org/drm/intel/issues/6227
[i915#6230]: https://gitlab.freedesktop.org/drm/intel/issues/6230
[i915#6245]: https://gitlab.freedesktop.org/drm/intel/issues/6245
[i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248
[i915#6252]: https://gitlab.freedesktop.org/drm/intel/issues/6252
[i915#6258]: https://gitlab.freedesktop.org/drm/intel/issues/6258
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6301]: https://gitlab.freedesktop.org/drm/intel/issues/6301
[i915#6334]: https://gitlab.freedesktop.org/drm/intel/issues/6334
[i915#6335]: https://gitlab.freedesktop.org/drm/intel/issues/6335
[i915#6344]: https://gitlab.freedesktop.org/drm/intel/issues/6344
[i915#6412]: https://gitlab.freedesktop.org/drm/intel/issues/6412
[i915#6433]: https://gitlab.freedesktop.org/drm/intel/issues/6433
[i915#6497]: https://gitlab.freedesktop.org/drm/intel/issues/6497
[i915#6524]: https://gitlab.freedesktop.org/drm/intel/issues/6524
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6590]: https://gitlab.freedesktop.org/drm/intel/issues/6590
[i915#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#6943]: https://gitlab.freedesktop.org/drm/intel/issues/6943
[i915#6944]: https://gitlab.freedesktop.org/drm/intel/issues/6944
[i915#6946]: https://gitlab.freedesktop.org/drm/intel/issues/6946
[i915#6953]: https://gitlab.freedesktop.org/drm/intel/issues/6953
[i915#7036]: https://gitlab.freedesktop.org/drm/intel/issues/7036
[i915#7037]: https://gitlab.freedesktop.org/drm/intel/issues/7037
[i915#7052]: https://gitlab.freedesktop.org/drm/intel/issues/7052
[i915#7116]: https://gitlab.freedesktop.org/drm/intel/issues/7116
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#7128]: https://gitlab.freedesktop.org/drm/intel/issues/7128
[i915#7173]: https://gitlab.freedesktop.org/drm/intel/issues/7173
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
[i915#7651]: https://gitlab.freedesktop.org/drm/intel/issues/7651
[i915#7697]: https://gitlab.freedesktop.org/drm/intel/issues/7697
[i915#7701]: https://gitlab.freedesktop.org/drm/intel/issues/7701
[i915#7707]: https://gitlab.freedesktop.org/drm/intel/issues/7707
[i915#7711]: https://gitlab.freedesktop.org/drm/intel/issues/7711
[i915#7742]: https://gitlab.freedesktop.org/drm/intel/issues/7742
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#7862]: https://gitlab.freedesktop.org/drm/intel/issues/7862
[i915#7900]: https://gitlab.freedesktop.org/drm/intel/issues/7900
[i915#7957]: https://gitlab.freedesktop.org/drm/intel/issues/7957
[i915#7981]: https://gitlab.freedesktop.org/drm/intel/issues/7981
[i915#8056]: https://gitlab.freedesktop.org/drm/intel/issues/8056
[i915#8151]: https://gitlab.freedesktop.org/drm/intel/issues/8151
[i915#8152]: https://gitlab.freedesktop.org/drm/intel/issues/8152
[i915#8162]: https://gitlab.freedesktop.org/drm/intel/issues/8162
[i915#8167]: https://gitlab.freedesktop.org/drm/intel/issues/8167
Build changes
-------------
* IGT: IGT_7157 -> TrybotIGT_706
* Linux: CI_DRM_12730 -> Patchwork_113950v1
CI-20190529: 20190529
CI_DRM_12730: c54b5fcf3e686a0abfdd7d6af53e9014c137023a @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7157: 96d12fdc942cee9526a951b377b195ca9c8276b1 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_113950v1: c54b5fcf3e686a0abfdd7d6af53e9014c137023a @ git://anongit.freedesktop.org/gfx-ci/linux
TrybotIGT_706: https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_706/index.html
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/index.html
[-- Attachment #2: Type: text/html, Size: 27838 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ✓ Fi.CI.BAT: success for drm/i915/active: Fix misuse of non-idle barriers as fence trackers
2023-02-13 13:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
@ 2023-02-13 15:12 ` Janusz Krzysztofik
0 siblings, 0 replies; 8+ messages in thread
From: Janusz Krzysztofik @ 2023-02-13 15:12 UTC (permalink / raw)
To: intel-gfx, Tvrtko Ursulin
Cc: Andrzej Hajda, Gwan-gyeong Mun, dri-devel, Andi Shyti,
Rodrigo Vivi, Janusz Krzysztofik, Chris Wilson, Nirmoy Das
On Monday, 13 February 2023 14:47:42 CET Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/active: Fix misuse of non-idle barriers as fence trackers
> URL : https://patchwork.freedesktop.org/series/113950/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_12730 -> Patchwork_113950v1
> ====================================================
>
> Summary
> -------
>
> **SUCCESS**
>
> No regressions found.
>
> External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/index.html
>
> Participating hosts (40 -> 37)
> ------------------------------
>
> Missing (3): fi-tgl-1115g4 bat-atsm-1 fi-snb-2520m
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_113950v1:
>
> ### IGT changes ###
>
> #### Possible regressions ####
No mor list corruptions, only issues already reported by the new
igt@gem_barrier_race@remote-request test before (without this patch in place).
> * {igt@gem_barrier_race@remote-request@rcs0} (NEW):
> - fi-rkl-11600: NOTRUN -> [ABORT][1]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-rkl-11600/igt@gem_barrier_race@remote-request@rcs0.html
> - bat-dg1-5: NOTRUN -> [ABORT][2]
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/bat-dg1-5/igt@gem_barrier_race@remote-request@rcs0.html
Infinite __i915_active_wait(), similar to
https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_706/fi-cfl-8109u/igt@gem_barrier_race@remote-request@rcs0.html
> - {bat-adlm-1}: NOTRUN -> [DMESG-WARN][3]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/bat-adlm-1/igt@gem_barrier_race@remote-request@rcs0.html
Suspicious RCU usage, equivalent to
https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_706/bat-dg1-7/igt@gem_barrier_race@remote-request@rcs0.html,
also seen before, e.g.,
https://gitlab.freedesktop.org/drm/intel/-/issues/7390,
https://gitlab.freedesktop.org/drm/intel/-/issues/6616
Thanks,
Janusz
>
>
> New tests
> ---------
>
> New tests have been introduced between CI_DRM_12730 and Patchwork_113950v1:
>
> ### New IGT tests (2) ###
>
> * igt@gem_barrier_race@remote-request:
> - Statuses :
> - Exec time: [None] s
>
> * igt@gem_barrier_race@remote-request@rcs0:
> - Statuses : 2 abort(s) 1 dmesg-warn(s) 27 pass(s) 5 skip(s)
> - Exec time: [0.0] s
>
>
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_113950v1 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * {igt@gem_barrier_race@remote-request@rcs0} (NEW):
> - fi-pnv-d510: NOTRUN -> [SKIP][4] ([fdo#109271])
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-pnv-d510/igt@gem_barrier_race@remote-request@rcs0.html
> - fi-blb-e6850: NOTRUN -> [SKIP][5] ([fdo#109271])
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-blb-e6850/igt@gem_barrier_race@remote-request@rcs0.html
> - fi-ivb-3770: NOTRUN -> [SKIP][6] ([fdo#109271])
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-ivb-3770/igt@gem_barrier_race@remote-request@rcs0.html
> - fi-elk-e7500: NOTRUN -> [SKIP][7] ([fdo#109271])
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-elk-e7500/igt@gem_barrier_race@remote-request@rcs0.html
> - fi-ilk-650: NOTRUN -> [SKIP][8] ([fdo#109271])
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-ilk-650/igt@gem_barrier_race@remote-request@rcs0.html
>
>
> #### Possible fixes ####
>
> * igt@i915_selftest@live@gt_heartbeat:
> - fi-apl-guc: [DMESG-FAIL][9] ([i915#5334]) -> [PASS][10]
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
>
> * igt@i915_selftest@live@requests:
> - {bat-rpls-2}: [ABORT][11] ([i915#7982]) -> [PASS][12]
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/bat-rpls-2/igt@i915_selftest@live@requests.html
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/bat-rpls-2/igt@i915_selftest@live@requests.html
>
> * igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions:
> - fi-bsw-n3050: [FAIL][13] ([i915#6298]) -> [PASS][14]
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions.html
> [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions.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
> [i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
> [i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
> [i915#6298]: https://gitlab.freedesktop.org/drm/intel/issues/6298
> [i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
> [i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699
> [i915#7982]: https://gitlab.freedesktop.org/drm/intel/issues/7982
> [i915#7996]: https://gitlab.freedesktop.org/drm/intel/issues/7996
>
>
> Build changes
> -------------
>
> * IGT: IGT_7157 -> TrybotIGT_706
> * Linux: CI_DRM_12730 -> Patchwork_113950v1
>
> CI-20190529: 20190529
> CI_DRM_12730: c54b5fcf3e686a0abfdd7d6af53e9014c137023a @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_7157: 96d12fdc942cee9526a951b377b195ca9c8276b1 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> Patchwork_113950v1: c54b5fcf3e686a0abfdd7d6af53e9014c137023a @ git://anongit.freedesktop.org/gfx-ci/linux
> TrybotIGT_706: https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_706/index.html
>
>
> ### Linux commits
>
> 44de67f6c674 drm/i915/active: Fix misuse of non-idle barriers as fence trackers
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/index.html
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/active: Fix misuse of non-idle barriers as fence trackers
@ 2023-02-13 15:12 ` Janusz Krzysztofik
0 siblings, 0 replies; 8+ messages in thread
From: Janusz Krzysztofik @ 2023-02-13 15:12 UTC (permalink / raw)
To: intel-gfx, Tvrtko Ursulin
Cc: Andrzej Hajda, dri-devel, Rodrigo Vivi, Chris Wilson, Nirmoy Das
On Monday, 13 February 2023 14:47:42 CET Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/active: Fix misuse of non-idle barriers as fence trackers
> URL : https://patchwork.freedesktop.org/series/113950/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_12730 -> Patchwork_113950v1
> ====================================================
>
> Summary
> -------
>
> **SUCCESS**
>
> No regressions found.
>
> External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/index.html
>
> Participating hosts (40 -> 37)
> ------------------------------
>
> Missing (3): fi-tgl-1115g4 bat-atsm-1 fi-snb-2520m
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_113950v1:
>
> ### IGT changes ###
>
> #### Possible regressions ####
No mor list corruptions, only issues already reported by the new
igt@gem_barrier_race@remote-request test before (without this patch in place).
> * {igt@gem_barrier_race@remote-request@rcs0} (NEW):
> - fi-rkl-11600: NOTRUN -> [ABORT][1]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-rkl-11600/igt@gem_barrier_race@remote-request@rcs0.html
> - bat-dg1-5: NOTRUN -> [ABORT][2]
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/bat-dg1-5/igt@gem_barrier_race@remote-request@rcs0.html
Infinite __i915_active_wait(), similar to
https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_706/fi-cfl-8109u/igt@gem_barrier_race@remote-request@rcs0.html
> - {bat-adlm-1}: NOTRUN -> [DMESG-WARN][3]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/bat-adlm-1/igt@gem_barrier_race@remote-request@rcs0.html
Suspicious RCU usage, equivalent to
https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_706/bat-dg1-7/igt@gem_barrier_race@remote-request@rcs0.html,
also seen before, e.g.,
https://gitlab.freedesktop.org/drm/intel/-/issues/7390,
https://gitlab.freedesktop.org/drm/intel/-/issues/6616
Thanks,
Janusz
>
>
> New tests
> ---------
>
> New tests have been introduced between CI_DRM_12730 and Patchwork_113950v1:
>
> ### New IGT tests (2) ###
>
> * igt@gem_barrier_race@remote-request:
> - Statuses :
> - Exec time: [None] s
>
> * igt@gem_barrier_race@remote-request@rcs0:
> - Statuses : 2 abort(s) 1 dmesg-warn(s) 27 pass(s) 5 skip(s)
> - Exec time: [0.0] s
>
>
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_113950v1 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * {igt@gem_barrier_race@remote-request@rcs0} (NEW):
> - fi-pnv-d510: NOTRUN -> [SKIP][4] ([fdo#109271])
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-pnv-d510/igt@gem_barrier_race@remote-request@rcs0.html
> - fi-blb-e6850: NOTRUN -> [SKIP][5] ([fdo#109271])
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-blb-e6850/igt@gem_barrier_race@remote-request@rcs0.html
> - fi-ivb-3770: NOTRUN -> [SKIP][6] ([fdo#109271])
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-ivb-3770/igt@gem_barrier_race@remote-request@rcs0.html
> - fi-elk-e7500: NOTRUN -> [SKIP][7] ([fdo#109271])
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-elk-e7500/igt@gem_barrier_race@remote-request@rcs0.html
> - fi-ilk-650: NOTRUN -> [SKIP][8] ([fdo#109271])
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-ilk-650/igt@gem_barrier_race@remote-request@rcs0.html
>
>
> #### Possible fixes ####
>
> * igt@i915_selftest@live@gt_heartbeat:
> - fi-apl-guc: [DMESG-FAIL][9] ([i915#5334]) -> [PASS][10]
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
>
> * igt@i915_selftest@live@requests:
> - {bat-rpls-2}: [ABORT][11] ([i915#7982]) -> [PASS][12]
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/bat-rpls-2/igt@i915_selftest@live@requests.html
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/bat-rpls-2/igt@i915_selftest@live@requests.html
>
> * igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions:
> - fi-bsw-n3050: [FAIL][13] ([i915#6298]) -> [PASS][14]
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12730/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions.html
> [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions.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
> [i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
> [i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
> [i915#6298]: https://gitlab.freedesktop.org/drm/intel/issues/6298
> [i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
> [i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699
> [i915#7982]: https://gitlab.freedesktop.org/drm/intel/issues/7982
> [i915#7996]: https://gitlab.freedesktop.org/drm/intel/issues/7996
>
>
> Build changes
> -------------
>
> * IGT: IGT_7157 -> TrybotIGT_706
> * Linux: CI_DRM_12730 -> Patchwork_113950v1
>
> CI-20190529: 20190529
> CI_DRM_12730: c54b5fcf3e686a0abfdd7d6af53e9014c137023a @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_7157: 96d12fdc942cee9526a951b377b195ca9c8276b1 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> Patchwork_113950v1: c54b5fcf3e686a0abfdd7d6af53e9014c137023a @ git://anongit.freedesktop.org/gfx-ci/linux
> TrybotIGT_706: https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_706/index.html
>
>
> ### Linux commits
>
> 44de67f6c674 drm/i915/active: Fix misuse of non-idle barriers as fence trackers
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_113950v1/index.html
>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2023-02-13 15:13 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-13 13:05 [PATCH 0/1] drm/i915/active: Fix misuse of non-idle barriers as fence trackers Janusz Krzysztofik
2023-02-13 13:05 ` [Intel-gfx] " Janusz Krzysztofik
2023-02-13 13:05 ` [PATCH 1/1] " Janusz Krzysztofik
2023-02-13 13:05 ` [Intel-gfx] " Janusz Krzysztofik
2023-02-13 13:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-02-13 15:12 ` Janusz Krzysztofik
2023-02-13 15:12 ` [Intel-gfx] " Janusz Krzysztofik
2023-02-13 14:57 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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.