* [PATCH v2] drm/i915/ttm: never purge busy objects
@ 2022-11-15 10:46 ` Matthew Auld
0 siblings, 0 replies; 9+ messages in thread
From: Matthew Auld @ 2022-11-15 10:46 UTC (permalink / raw)
To: intel-gfx; +Cc: Niranjana Vishwanathapura, Andrzej Hajda, Nirmoy Das, stable
In i915_gem_madvise_ioctl() we immediately purge the object is not
currently used, like when the mm.pages are NULL. With shmem the pages
might still be hanging around or are perhaps swapped out. Similarly with
ttm we might still have the pages hanging around on the ttm resource,
like with lmem or shmem, but here we need to be extra careful since
async unbinds are possible as well as in-progress kernel moves. In
i915_ttm_purge() we expect the pipeline-gutting to nuke the ttm resource
for us, however if it's busy the memory is only moved to a ghost object,
which then leads to broken behaviour when for example clearing the
i915_tt->filp, since the actual ttm_tt is still alive and populated,
even though it's been moved to the ghost object. When we later destroy
the ghost object we hit the following, since the filp is now NULL:
[ +0.006982] #PF: supervisor read access in kernel mode
[ +0.005149] #PF: error_code(0x0000) - not-present page
[ +0.005147] PGD 11631d067 P4D 11631d067 PUD 115972067 PMD 0
[ +0.005676] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ +0.012962] Workqueue: events ttm_device_delayed_workqueue [ttm]
[ +0.006022] RIP: 0010:i915_ttm_tt_unpopulate+0x3a/0x70 [i915]
[ +0.005879] Code: 89 fb 48 85 f6 74 11 8b 55 4c 48 8b 7d 30 45 31 c0 31 c9 e8 18 6a e5 e0 80 7d 60 00 74 20 48 8b 45 68
8b 55 08 4c 89 e7 5b 5d <48> 8b 40 20 83 e2 01 41 5c 89 d1 48 8b 70
30 e9 42 b2 ff ff 4c 89
[ +0.018782] RSP: 0000:ffffc9000bf6fd70 EFLAGS: 00010202
[ +0.005244] RAX: 0000000000000000 RBX: ffff8883e12ae380 RCX: 0000000000000000
[ +0.007150] RDX: 000000008000000e RSI: ffffffff823559b4 RDI: ffff8883e12ae3c0
[ +0.007142] RBP: ffff888103b65d48 R08: 0000000000000001 R09: 0000000000000001
[ +0.007144] R10: 0000000000000001 R11: ffff88829c2c8040 R12: ffff8883e12ae3c0
[ +0.007148] R13: 0000000000000001 R14: ffff888115184140 R15: ffff888115184248
[ +0.007154] FS: 0000000000000000(0000) GS:ffff88844db00000(0000) knlGS:0000000000000000
[ +0.008108] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ +0.005763] CR2: 0000000000000020 CR3: 000000013fdb4004 CR4: 00000000003706e0
[ +0.007152] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ +0.007145] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ +0.007154] Call Trace:
[ +0.002459] <TASK>
[ +0.002126] ttm_tt_unpopulate.part.0+0x17/0x70 [ttm]
[ +0.005068] ttm_bo_tt_destroy+0x1c/0x50 [ttm]
[ +0.004464] ttm_bo_cleanup_memtype_use+0x25/0x40 [ttm]
[ +0.005244] ttm_bo_cleanup_refs+0x90/0x2c0 [ttm]
[ +0.004721] ttm_bo_delayed_delete+0x235/0x250 [ttm]
[ +0.004981] ttm_device_delayed_workqueue+0x13/0x40 [ttm]
[ +0.005422] process_one_work+0x248/0x560
[ +0.004028] worker_thread+0x4b/0x390
[ +0.003682] ? process_one_work+0x560/0x560
[ +0.004199] kthread+0xeb/0x120
[ +0.003163] ? kthread_complete_and_exit+0x20/0x20
[ +0.004815] ret_from_fork+0x1f/0x30
v2:
- Just use ttm_bo_wait() directly (Niranjana)
- Add testcase reference
Testcase: igt@gem_madvise@dontneed-evict-race
Fixes: 213d50927763 ("drm/i915/ttm: Introduce a TTM i915 gem object backend")
Reported-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: Nirmoy Das <nirmoy.das@intel.com>
Cc: <stable@vger.kernel.org> # v5.15+
Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
---
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
index e4e55e3f4e41..34793863ea45 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
@@ -603,6 +603,10 @@ static int i915_ttm_truncate(struct drm_i915_gem_object *obj)
WARN_ON_ONCE(obj->mm.madv == I915_MADV_WILLNEED);
+ err = ttm_bo_wait(bo, true, false);
+ if (err)
+ return err;
+
err = i915_ttm_move_notify(bo);
if (err)
return err;
--
2.38.1
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [Intel-gfx] [PATCH v2] drm/i915/ttm: never purge busy objects
@ 2022-11-15 10:46 ` Matthew Auld
0 siblings, 0 replies; 9+ messages in thread
From: Matthew Auld @ 2022-11-15 10:46 UTC (permalink / raw)
To: intel-gfx; +Cc: stable, Andrzej Hajda, Nirmoy Das
In i915_gem_madvise_ioctl() we immediately purge the object is not
currently used, like when the mm.pages are NULL. With shmem the pages
might still be hanging around or are perhaps swapped out. Similarly with
ttm we might still have the pages hanging around on the ttm resource,
like with lmem or shmem, but here we need to be extra careful since
async unbinds are possible as well as in-progress kernel moves. In
i915_ttm_purge() we expect the pipeline-gutting to nuke the ttm resource
for us, however if it's busy the memory is only moved to a ghost object,
which then leads to broken behaviour when for example clearing the
i915_tt->filp, since the actual ttm_tt is still alive and populated,
even though it's been moved to the ghost object. When we later destroy
the ghost object we hit the following, since the filp is now NULL:
[ +0.006982] #PF: supervisor read access in kernel mode
[ +0.005149] #PF: error_code(0x0000) - not-present page
[ +0.005147] PGD 11631d067 P4D 11631d067 PUD 115972067 PMD 0
[ +0.005676] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ +0.012962] Workqueue: events ttm_device_delayed_workqueue [ttm]
[ +0.006022] RIP: 0010:i915_ttm_tt_unpopulate+0x3a/0x70 [i915]
[ +0.005879] Code: 89 fb 48 85 f6 74 11 8b 55 4c 48 8b 7d 30 45 31 c0 31 c9 e8 18 6a e5 e0 80 7d 60 00 74 20 48 8b 45 68
8b 55 08 4c 89 e7 5b 5d <48> 8b 40 20 83 e2 01 41 5c 89 d1 48 8b 70
30 e9 42 b2 ff ff 4c 89
[ +0.018782] RSP: 0000:ffffc9000bf6fd70 EFLAGS: 00010202
[ +0.005244] RAX: 0000000000000000 RBX: ffff8883e12ae380 RCX: 0000000000000000
[ +0.007150] RDX: 000000008000000e RSI: ffffffff823559b4 RDI: ffff8883e12ae3c0
[ +0.007142] RBP: ffff888103b65d48 R08: 0000000000000001 R09: 0000000000000001
[ +0.007144] R10: 0000000000000001 R11: ffff88829c2c8040 R12: ffff8883e12ae3c0
[ +0.007148] R13: 0000000000000001 R14: ffff888115184140 R15: ffff888115184248
[ +0.007154] FS: 0000000000000000(0000) GS:ffff88844db00000(0000) knlGS:0000000000000000
[ +0.008108] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ +0.005763] CR2: 0000000000000020 CR3: 000000013fdb4004 CR4: 00000000003706e0
[ +0.007152] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ +0.007145] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ +0.007154] Call Trace:
[ +0.002459] <TASK>
[ +0.002126] ttm_tt_unpopulate.part.0+0x17/0x70 [ttm]
[ +0.005068] ttm_bo_tt_destroy+0x1c/0x50 [ttm]
[ +0.004464] ttm_bo_cleanup_memtype_use+0x25/0x40 [ttm]
[ +0.005244] ttm_bo_cleanup_refs+0x90/0x2c0 [ttm]
[ +0.004721] ttm_bo_delayed_delete+0x235/0x250 [ttm]
[ +0.004981] ttm_device_delayed_workqueue+0x13/0x40 [ttm]
[ +0.005422] process_one_work+0x248/0x560
[ +0.004028] worker_thread+0x4b/0x390
[ +0.003682] ? process_one_work+0x560/0x560
[ +0.004199] kthread+0xeb/0x120
[ +0.003163] ? kthread_complete_and_exit+0x20/0x20
[ +0.004815] ret_from_fork+0x1f/0x30
v2:
- Just use ttm_bo_wait() directly (Niranjana)
- Add testcase reference
Testcase: igt@gem_madvise@dontneed-evict-race
Fixes: 213d50927763 ("drm/i915/ttm: Introduce a TTM i915 gem object backend")
Reported-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: Nirmoy Das <nirmoy.das@intel.com>
Cc: <stable@vger.kernel.org> # v5.15+
Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
---
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
index e4e55e3f4e41..34793863ea45 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
@@ -603,6 +603,10 @@ static int i915_ttm_truncate(struct drm_i915_gem_object *obj)
WARN_ON_ONCE(obj->mm.madv == I915_MADV_WILLNEED);
+ err = ttm_bo_wait(bo, true, false);
+ if (err)
+ return err;
+
err = i915_ttm_move_notify(bo);
if (err)
return err;
--
2.38.1
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/ttm: never purge busy objects
2022-11-15 10:46 ` [Intel-gfx] " Matthew Auld
@ 2022-11-15 13:45 ` Das, Nirmoy
-1 siblings, 0 replies; 9+ messages in thread
From: Das, Nirmoy @ 2022-11-15 13:45 UTC (permalink / raw)
To: Matthew Auld, intel-gfx; +Cc: stable, Andrzej Hajda, Nirmoy Das
On 11/15/2022 11:46 AM, Matthew Auld wrote:
> In i915_gem_madvise_ioctl() we immediately purge the object is not
> currently used, like when the mm.pages are NULL. With shmem the pages
> might still be hanging around or are perhaps swapped out. Similarly with
> ttm we might still have the pages hanging around on the ttm resource,
> like with lmem or shmem, but here we need to be extra careful since
> async unbinds are possible as well as in-progress kernel moves. In
> i915_ttm_purge() we expect the pipeline-gutting to nuke the ttm resource
> for us, however if it's busy the memory is only moved to a ghost object,
> which then leads to broken behaviour when for example clearing the
> i915_tt->filp, since the actual ttm_tt is still alive and populated,
> even though it's been moved to the ghost object. When we later destroy
> the ghost object we hit the following, since the filp is now NULL:
>
> [ +0.006982] #PF: supervisor read access in kernel mode
> [ +0.005149] #PF: error_code(0x0000) - not-present page
> [ +0.005147] PGD 11631d067 P4D 11631d067 PUD 115972067 PMD 0
> [ +0.005676] Oops: 0000 [#1] PREEMPT SMP NOPTI
> [ +0.012962] Workqueue: events ttm_device_delayed_workqueue [ttm]
> [ +0.006022] RIP: 0010:i915_ttm_tt_unpopulate+0x3a/0x70 [i915]
> [ +0.005879] Code: 89 fb 48 85 f6 74 11 8b 55 4c 48 8b 7d 30 45 31 c0 31 c9 e8 18 6a e5 e0 80 7d 60 00 74 20 48 8b 45 68
> 8b 55 08 4c 89 e7 5b 5d <48> 8b 40 20 83 e2 01 41 5c 89 d1 48 8b 70
> 30 e9 42 b2 ff ff 4c 89
> [ +0.018782] RSP: 0000:ffffc9000bf6fd70 EFLAGS: 00010202
> [ +0.005244] RAX: 0000000000000000 RBX: ffff8883e12ae380 RCX: 0000000000000000
> [ +0.007150] RDX: 000000008000000e RSI: ffffffff823559b4 RDI: ffff8883e12ae3c0
> [ +0.007142] RBP: ffff888103b65d48 R08: 0000000000000001 R09: 0000000000000001
> [ +0.007144] R10: 0000000000000001 R11: ffff88829c2c8040 R12: ffff8883e12ae3c0
> [ +0.007148] R13: 0000000000000001 R14: ffff888115184140 R15: ffff888115184248
> [ +0.007154] FS: 0000000000000000(0000) GS:ffff88844db00000(0000) knlGS:0000000000000000
> [ +0.008108] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ +0.005763] CR2: 0000000000000020 CR3: 000000013fdb4004 CR4: 00000000003706e0
> [ +0.007152] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ +0.007145] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [ +0.007154] Call Trace:
> [ +0.002459] <TASK>
> [ +0.002126] ttm_tt_unpopulate.part.0+0x17/0x70 [ttm]
> [ +0.005068] ttm_bo_tt_destroy+0x1c/0x50 [ttm]
> [ +0.004464] ttm_bo_cleanup_memtype_use+0x25/0x40 [ttm]
> [ +0.005244] ttm_bo_cleanup_refs+0x90/0x2c0 [ttm]
> [ +0.004721] ttm_bo_delayed_delete+0x235/0x250 [ttm]
> [ +0.004981] ttm_device_delayed_workqueue+0x13/0x40 [ttm]
> [ +0.005422] process_one_work+0x248/0x560
> [ +0.004028] worker_thread+0x4b/0x390
> [ +0.003682] ? process_one_work+0x560/0x560
> [ +0.004199] kthread+0xeb/0x120
> [ +0.003163] ? kthread_complete_and_exit+0x20/0x20
> [ +0.004815] ret_from_fork+0x1f/0x30
>
> v2:
> - Just use ttm_bo_wait() directly (Niranjana)
> - Add testcase reference
>
> Testcase: igt@gem_madvise@dontneed-evict-race
> Fixes: 213d50927763 ("drm/i915/ttm: Introduce a TTM i915 gem object backend")
> Reported-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
Acked-by: Nirmoy Das <Nirmoy.Das@intel.com>
> Cc: <stable@vger.kernel.org> # v5.15+
> Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> index e4e55e3f4e41..34793863ea45 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> @@ -603,6 +603,10 @@ static int i915_ttm_truncate(struct drm_i915_gem_object *obj)
>
> WARN_ON_ONCE(obj->mm.madv == I915_MADV_WILLNEED);
>
> + err = ttm_bo_wait(bo, true, false);
> + if (err)
> + return err;
> +
> err = i915_ttm_move_notify(bo);
> if (err)
> return err;
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/ttm: never purge busy objects
@ 2022-11-15 13:45 ` Das, Nirmoy
0 siblings, 0 replies; 9+ messages in thread
From: Das, Nirmoy @ 2022-11-15 13:45 UTC (permalink / raw)
To: Matthew Auld, intel-gfx; +Cc: Andrzej Hajda, stable, Nirmoy Das
On 11/15/2022 11:46 AM, Matthew Auld wrote:
> In i915_gem_madvise_ioctl() we immediately purge the object is not
> currently used, like when the mm.pages are NULL. With shmem the pages
> might still be hanging around or are perhaps swapped out. Similarly with
> ttm we might still have the pages hanging around on the ttm resource,
> like with lmem or shmem, but here we need to be extra careful since
> async unbinds are possible as well as in-progress kernel moves. In
> i915_ttm_purge() we expect the pipeline-gutting to nuke the ttm resource
> for us, however if it's busy the memory is only moved to a ghost object,
> which then leads to broken behaviour when for example clearing the
> i915_tt->filp, since the actual ttm_tt is still alive and populated,
> even though it's been moved to the ghost object. When we later destroy
> the ghost object we hit the following, since the filp is now NULL:
>
> [ +0.006982] #PF: supervisor read access in kernel mode
> [ +0.005149] #PF: error_code(0x0000) - not-present page
> [ +0.005147] PGD 11631d067 P4D 11631d067 PUD 115972067 PMD 0
> [ +0.005676] Oops: 0000 [#1] PREEMPT SMP NOPTI
> [ +0.012962] Workqueue: events ttm_device_delayed_workqueue [ttm]
> [ +0.006022] RIP: 0010:i915_ttm_tt_unpopulate+0x3a/0x70 [i915]
> [ +0.005879] Code: 89 fb 48 85 f6 74 11 8b 55 4c 48 8b 7d 30 45 31 c0 31 c9 e8 18 6a e5 e0 80 7d 60 00 74 20 48 8b 45 68
> 8b 55 08 4c 89 e7 5b 5d <48> 8b 40 20 83 e2 01 41 5c 89 d1 48 8b 70
> 30 e9 42 b2 ff ff 4c 89
> [ +0.018782] RSP: 0000:ffffc9000bf6fd70 EFLAGS: 00010202
> [ +0.005244] RAX: 0000000000000000 RBX: ffff8883e12ae380 RCX: 0000000000000000
> [ +0.007150] RDX: 000000008000000e RSI: ffffffff823559b4 RDI: ffff8883e12ae3c0
> [ +0.007142] RBP: ffff888103b65d48 R08: 0000000000000001 R09: 0000000000000001
> [ +0.007144] R10: 0000000000000001 R11: ffff88829c2c8040 R12: ffff8883e12ae3c0
> [ +0.007148] R13: 0000000000000001 R14: ffff888115184140 R15: ffff888115184248
> [ +0.007154] FS: 0000000000000000(0000) GS:ffff88844db00000(0000) knlGS:0000000000000000
> [ +0.008108] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ +0.005763] CR2: 0000000000000020 CR3: 000000013fdb4004 CR4: 00000000003706e0
> [ +0.007152] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ +0.007145] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [ +0.007154] Call Trace:
> [ +0.002459] <TASK>
> [ +0.002126] ttm_tt_unpopulate.part.0+0x17/0x70 [ttm]
> [ +0.005068] ttm_bo_tt_destroy+0x1c/0x50 [ttm]
> [ +0.004464] ttm_bo_cleanup_memtype_use+0x25/0x40 [ttm]
> [ +0.005244] ttm_bo_cleanup_refs+0x90/0x2c0 [ttm]
> [ +0.004721] ttm_bo_delayed_delete+0x235/0x250 [ttm]
> [ +0.004981] ttm_device_delayed_workqueue+0x13/0x40 [ttm]
> [ +0.005422] process_one_work+0x248/0x560
> [ +0.004028] worker_thread+0x4b/0x390
> [ +0.003682] ? process_one_work+0x560/0x560
> [ +0.004199] kthread+0xeb/0x120
> [ +0.003163] ? kthread_complete_and_exit+0x20/0x20
> [ +0.004815] ret_from_fork+0x1f/0x30
>
> v2:
> - Just use ttm_bo_wait() directly (Niranjana)
> - Add testcase reference
>
> Testcase: igt@gem_madvise@dontneed-evict-race
> Fixes: 213d50927763 ("drm/i915/ttm: Introduce a TTM i915 gem object backend")
> Reported-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
Acked-by: Nirmoy Das <Nirmoy.Das@intel.com>
> Cc: <stable@vger.kernel.org> # v5.15+
> Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> index e4e55e3f4e41..34793863ea45 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> @@ -603,6 +603,10 @@ static int i915_ttm_truncate(struct drm_i915_gem_object *obj)
>
> WARN_ON_ONCE(obj->mm.madv == I915_MADV_WILLNEED);
>
> + err = ttm_bo_wait(bo, true, false);
> + if (err)
> + return err;
> +
> err = i915_ttm_move_notify(bo);
> if (err)
> return err;
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/ttm: never purge busy objects
2022-11-15 10:46 ` [Intel-gfx] " Matthew Auld
@ 2022-11-15 16:20 ` Andrzej Hajda
-1 siblings, 0 replies; 9+ messages in thread
From: Andrzej Hajda @ 2022-11-15 16:20 UTC (permalink / raw)
To: Matthew Auld, intel-gfx; +Cc: stable, Nirmoy Das
On 15.11.2022 11:46, Matthew Auld wrote:
> In i915_gem_madvise_ioctl() we immediately purge the object is not
> currently used, like when the mm.pages are NULL. With shmem the pages
> might still be hanging around or are perhaps swapped out. Similarly with
> ttm we might still have the pages hanging around on the ttm resource,
> like with lmem or shmem, but here we need to be extra careful since
> async unbinds are possible as well as in-progress kernel moves. In
> i915_ttm_purge() we expect the pipeline-gutting to nuke the ttm resource
> for us, however if it's busy the memory is only moved to a ghost object,
> which then leads to broken behaviour when for example clearing the
> i915_tt->filp, since the actual ttm_tt is still alive and populated,
> even though it's been moved to the ghost object. When we later destroy
> the ghost object we hit the following, since the filp is now NULL:
>
> [ +0.006982] #PF: supervisor read access in kernel mode
> [ +0.005149] #PF: error_code(0x0000) - not-present page
> [ +0.005147] PGD 11631d067 P4D 11631d067 PUD 115972067 PMD 0
> [ +0.005676] Oops: 0000 [#1] PREEMPT SMP NOPTI
> [ +0.012962] Workqueue: events ttm_device_delayed_workqueue [ttm]
> [ +0.006022] RIP: 0010:i915_ttm_tt_unpopulate+0x3a/0x70 [i915]
> [ +0.005879] Code: 89 fb 48 85 f6 74 11 8b 55 4c 48 8b 7d 30 45 31 c0 31 c9 e8 18 6a e5 e0 80 7d 60 00 74 20 48 8b 45 68
> 8b 55 08 4c 89 e7 5b 5d <48> 8b 40 20 83 e2 01 41 5c 89 d1 48 8b 70
> 30 e9 42 b2 ff ff 4c 89
> [ +0.018782] RSP: 0000:ffffc9000bf6fd70 EFLAGS: 00010202
> [ +0.005244] RAX: 0000000000000000 RBX: ffff8883e12ae380 RCX: 0000000000000000
> [ +0.007150] RDX: 000000008000000e RSI: ffffffff823559b4 RDI: ffff8883e12ae3c0
> [ +0.007142] RBP: ffff888103b65d48 R08: 0000000000000001 R09: 0000000000000001
> [ +0.007144] R10: 0000000000000001 R11: ffff88829c2c8040 R12: ffff8883e12ae3c0
> [ +0.007148] R13: 0000000000000001 R14: ffff888115184140 R15: ffff888115184248
> [ +0.007154] FS: 0000000000000000(0000) GS:ffff88844db00000(0000) knlGS:0000000000000000
> [ +0.008108] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ +0.005763] CR2: 0000000000000020 CR3: 000000013fdb4004 CR4: 00000000003706e0
> [ +0.007152] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ +0.007145] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [ +0.007154] Call Trace:
> [ +0.002459] <TASK>
> [ +0.002126] ttm_tt_unpopulate.part.0+0x17/0x70 [ttm]
> [ +0.005068] ttm_bo_tt_destroy+0x1c/0x50 [ttm]
> [ +0.004464] ttm_bo_cleanup_memtype_use+0x25/0x40 [ttm]
> [ +0.005244] ttm_bo_cleanup_refs+0x90/0x2c0 [ttm]
> [ +0.004721] ttm_bo_delayed_delete+0x235/0x250 [ttm]
> [ +0.004981] ttm_device_delayed_workqueue+0x13/0x40 [ttm]
> [ +0.005422] process_one_work+0x248/0x560
> [ +0.004028] worker_thread+0x4b/0x390
> [ +0.003682] ? process_one_work+0x560/0x560
> [ +0.004199] kthread+0xeb/0x120
> [ +0.003163] ? kthread_complete_and_exit+0x20/0x20
> [ +0.004815] ret_from_fork+0x1f/0x30
>
> v2:
> - Just use ttm_bo_wait() directly (Niranjana)
> - Add testcase reference
>
> Testcase: igt@gem_madvise@dontneed-evict-race
> Fixes: 213d50927763 ("drm/i915/ttm: Introduce a TTM i915 gem object backend")
> Reported-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
> Cc: <stable@vger.kernel.org> # v5.15+
> Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
Regards
Andrzej
> ---
> drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> index e4e55e3f4e41..34793863ea45 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> @@ -603,6 +603,10 @@ static int i915_ttm_truncate(struct drm_i915_gem_object *obj)
>
> WARN_ON_ONCE(obj->mm.madv == I915_MADV_WILLNEED);
>
> + err = ttm_bo_wait(bo, true, false);
> + if (err)
> + return err;
> +
> err = i915_ttm_move_notify(bo);
> if (err)
> return err;
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH v2] drm/i915/ttm: never purge busy objects
@ 2022-11-15 16:20 ` Andrzej Hajda
0 siblings, 0 replies; 9+ messages in thread
From: Andrzej Hajda @ 2022-11-15 16:20 UTC (permalink / raw)
To: Matthew Auld, intel-gfx; +Cc: Niranjana Vishwanathapura, Nirmoy Das, stable
On 15.11.2022 11:46, Matthew Auld wrote:
> In i915_gem_madvise_ioctl() we immediately purge the object is not
> currently used, like when the mm.pages are NULL. With shmem the pages
> might still be hanging around or are perhaps swapped out. Similarly with
> ttm we might still have the pages hanging around on the ttm resource,
> like with lmem or shmem, but here we need to be extra careful since
> async unbinds are possible as well as in-progress kernel moves. In
> i915_ttm_purge() we expect the pipeline-gutting to nuke the ttm resource
> for us, however if it's busy the memory is only moved to a ghost object,
> which then leads to broken behaviour when for example clearing the
> i915_tt->filp, since the actual ttm_tt is still alive and populated,
> even though it's been moved to the ghost object. When we later destroy
> the ghost object we hit the following, since the filp is now NULL:
>
> [ +0.006982] #PF: supervisor read access in kernel mode
> [ +0.005149] #PF: error_code(0x0000) - not-present page
> [ +0.005147] PGD 11631d067 P4D 11631d067 PUD 115972067 PMD 0
> [ +0.005676] Oops: 0000 [#1] PREEMPT SMP NOPTI
> [ +0.012962] Workqueue: events ttm_device_delayed_workqueue [ttm]
> [ +0.006022] RIP: 0010:i915_ttm_tt_unpopulate+0x3a/0x70 [i915]
> [ +0.005879] Code: 89 fb 48 85 f6 74 11 8b 55 4c 48 8b 7d 30 45 31 c0 31 c9 e8 18 6a e5 e0 80 7d 60 00 74 20 48 8b 45 68
> 8b 55 08 4c 89 e7 5b 5d <48> 8b 40 20 83 e2 01 41 5c 89 d1 48 8b 70
> 30 e9 42 b2 ff ff 4c 89
> [ +0.018782] RSP: 0000:ffffc9000bf6fd70 EFLAGS: 00010202
> [ +0.005244] RAX: 0000000000000000 RBX: ffff8883e12ae380 RCX: 0000000000000000
> [ +0.007150] RDX: 000000008000000e RSI: ffffffff823559b4 RDI: ffff8883e12ae3c0
> [ +0.007142] RBP: ffff888103b65d48 R08: 0000000000000001 R09: 0000000000000001
> [ +0.007144] R10: 0000000000000001 R11: ffff88829c2c8040 R12: ffff8883e12ae3c0
> [ +0.007148] R13: 0000000000000001 R14: ffff888115184140 R15: ffff888115184248
> [ +0.007154] FS: 0000000000000000(0000) GS:ffff88844db00000(0000) knlGS:0000000000000000
> [ +0.008108] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ +0.005763] CR2: 0000000000000020 CR3: 000000013fdb4004 CR4: 00000000003706e0
> [ +0.007152] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ +0.007145] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [ +0.007154] Call Trace:
> [ +0.002459] <TASK>
> [ +0.002126] ttm_tt_unpopulate.part.0+0x17/0x70 [ttm]
> [ +0.005068] ttm_bo_tt_destroy+0x1c/0x50 [ttm]
> [ +0.004464] ttm_bo_cleanup_memtype_use+0x25/0x40 [ttm]
> [ +0.005244] ttm_bo_cleanup_refs+0x90/0x2c0 [ttm]
> [ +0.004721] ttm_bo_delayed_delete+0x235/0x250 [ttm]
> [ +0.004981] ttm_device_delayed_workqueue+0x13/0x40 [ttm]
> [ +0.005422] process_one_work+0x248/0x560
> [ +0.004028] worker_thread+0x4b/0x390
> [ +0.003682] ? process_one_work+0x560/0x560
> [ +0.004199] kthread+0xeb/0x120
> [ +0.003163] ? kthread_complete_and_exit+0x20/0x20
> [ +0.004815] ret_from_fork+0x1f/0x30
>
> v2:
> - Just use ttm_bo_wait() directly (Niranjana)
> - Add testcase reference
>
> Testcase: igt@gem_madvise@dontneed-evict-race
> Fixes: 213d50927763 ("drm/i915/ttm: Introduce a TTM i915 gem object backend")
> Reported-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
> Cc: <stable@vger.kernel.org> # v5.15+
> Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
Regards
Andrzej
> ---
> drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> index e4e55e3f4e41..34793863ea45 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> @@ -603,6 +603,10 @@ static int i915_ttm_truncate(struct drm_i915_gem_object *obj)
>
> WARN_ON_ONCE(obj->mm.madv == I915_MADV_WILLNEED);
>
> + err = ttm_bo_wait(bo, true, false);
> + if (err)
> + return err;
> +
> err = i915_ttm_move_notify(bo);
> if (err)
> return err;
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/ttm: never purge busy objects (rev2)
2022-11-15 10:46 ` [Intel-gfx] " Matthew Auld
` (2 preceding siblings ...)
(?)
@ 2022-11-15 16:30 ` Patchwork
-1 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2022-11-15 16:30 UTC (permalink / raw)
To: Matthew Auld; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/ttm: never purge busy objects (rev2)
URL : https://patchwork.freedesktop.org/series/110601/
State : warning
== Summary ==
Error: dim checkpatch failed
b44746463714 drm/i915/ttm: never purge busy objects
-:25: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#25:
[ +0.005879] Code: 89 fb 48 85 f6 74 11 8b 55 4c 48 8b 7d 30 45 31 c0 31 c9 e8 18 6a e5 e0 80 7d 60 00 74 20 48 8b 45 68
total: 0 errors, 1 warnings, 0 checks, 10 lines checked
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/ttm: never purge busy objects (rev2)
2022-11-15 10:46 ` [Intel-gfx] " Matthew Auld
` (3 preceding siblings ...)
(?)
@ 2022-11-15 16:52 ` Patchwork
-1 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2022-11-15 16:52 UTC (permalink / raw)
To: Matthew Auld; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 2879 bytes --]
== Series Details ==
Series: drm/i915/ttm: never purge busy objects (rev2)
URL : https://patchwork.freedesktop.org/series/110601/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12382 -> Patchwork_110601v2
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/index.html
Participating hosts (40 -> 38)
------------------------------
Missing (2): bat-rpls-1 bat-dg2-11
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_110601v2:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@i915_selftest@live@gt_mocs:
- {bat-adln-1}: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/bat-adln-1/igt@i915_selftest@live@gt_mocs.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/bat-adln-1/igt@i915_selftest@live@gt_mocs.html
Known issues
------------
Here are the changes found in Patchwork_110601v2 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@gem_huc_copy@huc-copy:
- {bat-dg2-8}: [FAIL][3] ([i915#7029]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/bat-dg2-8/igt@gem_huc_copy@huc-copy.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/bat-dg2-8/igt@gem_huc_copy@huc-copy.html
* igt@i915_pm_rpm@module-reload:
- {bat-rpls-2}: [DMESG-WARN][5] ([i915#6434]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/bat-rpls-2/igt@i915_pm_rpm@module-reload.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/bat-rpls-2/igt@i915_pm_rpm@module-reload.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#5278]: https://gitlab.freedesktop.org/drm/intel/issues/5278
[i915#6434]: https://gitlab.freedesktop.org/drm/intel/issues/6434
[i915#7029]: https://gitlab.freedesktop.org/drm/intel/issues/7029
Build changes
-------------
* Linux: CI_DRM_12382 -> Patchwork_110601v2
CI-20190529: 20190529
CI_DRM_12382: cb74864693414b221b3601572e75449558126e8b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7057: e2138d48c2c506816868c16cf3ba64f81bdead41 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_110601v2: cb74864693414b221b3601572e75449558126e8b @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
8fc1b9729634 drm/i915/ttm: never purge busy objects
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/index.html
[-- Attachment #2: Type: text/html, Size: 3485 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ttm: never purge busy objects (rev2)
2022-11-15 10:46 ` [Intel-gfx] " Matthew Auld
` (4 preceding siblings ...)
(?)
@ 2022-11-15 22:27 ` Patchwork
-1 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2022-11-15 22:27 UTC (permalink / raw)
To: Matthew Auld; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 31098 bytes --]
== Series Details ==
Series: drm/i915/ttm: never purge busy objects (rev2)
URL : https://patchwork.freedesktop.org/series/110601/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12382_full -> Patchwork_110601v2_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_110601v2_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_110601v2_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_110601v2_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_fence@syncobj-repeat:
- shard-skl: NOTRUN -> [INCOMPLETE][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl2/igt@gem_exec_fence@syncobj-repeat.html
* igt@kms_plane_alpha_blend@alpha-7efc@pipe-b-edp-1:
- shard-tglb: [PASS][2] -> [INCOMPLETE][3]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-tglb1/igt@kms_plane_alpha_blend@alpha-7efc@pipe-b-edp-1.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-tglb8/igt@kms_plane_alpha_blend@alpha-7efc@pipe-b-edp-1.html
Known issues
------------
Here are the changes found in Patchwork_110601v2_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@fbdev@unaligned-read:
- shard-skl: [PASS][4] -> [DMESG-WARN][5] ([i915#1982])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-skl9/igt@fbdev@unaligned-read.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl7/igt@fbdev@unaligned-read.html
* igt@gem_ctx_persistence@legacy-engines-hang:
- shard-snb: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#1099])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-snb6/igt@gem_ctx_persistence@legacy-engines-hang.html
* igt@gem_eio@unwedge-stress:
- shard-snb: NOTRUN -> [FAIL][7] ([i915#3354])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-snb6/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_fair@basic-deadline:
- shard-glk: [PASS][8] -> [FAIL][9] ([i915#2846])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-glk2/igt@gem_exec_fair@basic-deadline.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-glk6/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][10] -> [FAIL][11] ([i915#2842]) +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-tglb3/igt@gem_exec_fair@basic-flow@rcs0.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-tglb1/igt@gem_exec_fair@basic-flow@rcs0.html
* igt@gem_exec_fair@basic-none@vecs0:
- shard-glk: [PASS][12] -> [FAIL][13] ([i915#2842])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-glk3/igt@gem_exec_fair@basic-none@vecs0.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-glk3/igt@gem_exec_fair@basic-none@vecs0.html
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][14] -> [SKIP][15] ([i915#2190])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-tglb1/igt@gem_huc_copy@huc-copy.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-tglb7/igt@gem_huc_copy@huc-copy.html
* igt@gem_pread@exhaustion:
- shard-skl: NOTRUN -> [INCOMPLETE][16] ([i915#7248])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl10/igt@gem_pread@exhaustion.html
* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs:
- shard-skl: NOTRUN -> [SKIP][17] ([fdo#109271] / [i915#3886]) +2 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl10/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html
* igt@kms_chamelium@vga-hpd-enable-disable-mode:
- shard-skl: NOTRUN -> [SKIP][18] ([fdo#109271] / [fdo#111827]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl2/igt@kms_chamelium@vga-hpd-enable-disable-mode.html
* igt@kms_chamelium@vga-hpd-with-enabled-mode:
- shard-snb: NOTRUN -> [SKIP][19] ([fdo#109271] / [fdo#111827])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-snb6/igt@kms_chamelium@vga-hpd-with-enabled-mode.html
* igt@kms_cursor_crc@cursor-offscreen-32x10:
- shard-skl: NOTRUN -> [SKIP][20] ([fdo#109271]) +35 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl2/igt@kms_cursor_crc@cursor-offscreen-32x10.html
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][21] -> [FAIL][22] ([i915#79]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-glk1/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-glk8/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html
* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][23] ([i915#2587] / [i915#2672]) +2 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb1/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tile-upscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][24] ([i915#2672]) +8 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb3/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tile-upscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-linear-to-32bpp-linear-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][25] ([i915#3555]) +2 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-linear-to-32bpp-linear-downscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][26] ([i915#2672] / [i915#3555])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb3/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-default-mode.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-mmap-cpu:
- shard-snb: NOTRUN -> [SKIP][27] ([fdo#109271]) +53 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-snb6/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-mmap-cpu.html
* igt@kms_plane_alpha_blend@alpha-transparent-fb@pipe-c-edp-1:
- shard-skl: NOTRUN -> [FAIL][28] ([i915#4573]) +2 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl7/igt@kms_plane_alpha_blend@alpha-transparent-fb@pipe-c-edp-1.html
* igt@kms_plane_lowres@tiling-yf@pipe-b-hdmi-a-1:
- shard-glk: [PASS][29] -> [FAIL][30] ([i915#7307])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-glk1/igt@kms_plane_lowres@tiling-yf@pipe-b-hdmi-a-1.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-glk8/igt@kms_plane_lowres@tiling-yf@pipe-b-hdmi-a-1.html
* igt@kms_plane_scaling@plane-downscale-with-pixel-format-factor-0-5@pipe-b-edp-1:
- shard-iclb: [PASS][31] -> [SKIP][32] ([i915#5176]) +2 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb8/igt@kms_plane_scaling@plane-downscale-with-pixel-format-factor-0-5@pipe-b-edp-1.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb2/igt@kms_plane_scaling@plane-downscale-with-pixel-format-factor-0-5@pipe-b-edp-1.html
* igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b-edp-1:
- shard-iclb: [PASS][33] -> [SKIP][34] ([i915#5235]) +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb6/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b-edp-1.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb2/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b-edp-1.html
* igt@kms_psr2_su@frontbuffer-xrgb8888:
- shard-skl: NOTRUN -> [SKIP][35] ([fdo#109271] / [i915#658]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl10/igt@kms_psr2_su@frontbuffer-xrgb8888.html
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-iclb: NOTRUN -> [SKIP][36] ([fdo#109642] / [fdo#111068] / [i915#658])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb5/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [PASS][37] -> [SKIP][38] ([fdo#109441]) +3 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb6/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_psr_stress_test@flip-primary-invalidate-overlay:
- shard-iclb: [PASS][39] -> [SKIP][40] ([i915#5519])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb5/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb7/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html
* igt@sysfs_clients@fair-1:
- shard-skl: NOTRUN -> [SKIP][41] ([fdo#109271] / [i915#2994])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl2/igt@sysfs_clients@fair-1.html
#### Possible fixes ####
* igt@core_hotunplug@unbind-rebind:
- shard-snb: [DMESG-WARN][42] ([i915#4528]) -> [PASS][43]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-snb6/igt@core_hotunplug@unbind-rebind.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-snb6/igt@core_hotunplug@unbind-rebind.html
* igt@fbdev@write:
- {shard-rkl}: [SKIP][44] ([i915#2582]) -> [PASS][45]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-5/igt@fbdev@write.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@fbdev@write.html
* igt@gem_eio@in-flight-suspend:
- {shard-rkl}: [FAIL][46] ([fdo#103375]) -> [PASS][47]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-4/igt@gem_eio@in-flight-suspend.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@gem_eio@in-flight-suspend.html
* igt@gem_exec_balancer@parallel:
- shard-iclb: [SKIP][48] ([i915#4525]) -> [PASS][49] +1 similar issue
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb3/igt@gem_exec_balancer@parallel.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb2/igt@gem_exec_balancer@parallel.html
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [FAIL][50] ([i915#2842]) -> [PASS][51]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-apl2/igt@gem_exec_fair@basic-none-solo@rcs0.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-apl2/igt@gem_exec_fair@basic-none-solo@rcs0.html
* igt@gem_exec_fair@basic-pace@bcs0:
- shard-iclb: [FAIL][52] ([i915#2842]) -> [PASS][53]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb5/igt@gem_exec_fair@basic-pace@bcs0.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb8/igt@gem_exec_fair@basic-pace@bcs0.html
* igt@gem_exec_reloc@basic-gtt-read:
- {shard-rkl}: [SKIP][54] ([i915#3281]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-2/igt@gem_exec_reloc@basic-gtt-read.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-5/igt@gem_exec_reloc@basic-gtt-read.html
* igt@gem_pread@uncached:
- {shard-rkl}: [SKIP][56] ([i915#3282]) -> [PASS][57] +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-2/igt@gem_pread@uncached.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-5/igt@gem_pread@uncached.html
* igt@i915_pipe_stress@stress-xrgb8888-untiled:
- {shard-rkl}: [SKIP][58] ([i915#4098]) -> [PASS][59]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-4/igt@i915_pipe_stress@stress-xrgb8888-untiled.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@i915_pipe_stress@stress-xrgb8888-untiled.html
* igt@i915_pm_sseu@full-enable:
- shard-skl: [FAIL][60] ([i915#6991]) -> [PASS][61]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-skl10/igt@i915_pm_sseu@full-enable.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl1/igt@i915_pm_sseu@full-enable.html
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-iclb: [SKIP][62] -> [PASS][63]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb5/igt@i915_suspend@fence-restore-tiled2untiled.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb3/igt@i915_suspend@fence-restore-tiled2untiled.html
* igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc:
- {shard-rkl}: [SKIP][64] ([i915#1845] / [i915#4098]) -> [PASS][65] +12 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-4/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_cursor_legacy@single-move@all-pipes:
- {shard-rkl}: [INCOMPLETE][66] -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-4/igt@kms_cursor_legacy@single-move@all-pipes.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@kms_cursor_legacy@single-move@all-pipes.html
* igt@kms_fbcon_fbt@psr:
- {shard-rkl}: [SKIP][68] ([fdo#110189] / [i915#3955]) -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-5/igt@kms_fbcon_fbt@psr.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@kms_fbcon_fbt@psr.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-skl: [FAIL][70] ([i915#79]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-skl7/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl4/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html
* igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1:
- shard-skl: [FAIL][72] ([i915#2122]) -> [PASS][73]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-skl2/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl2/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-pwrite:
- {shard-rkl}: [SKIP][74] ([i915#1849] / [i915#4098]) -> [PASS][75] +9 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-pwrite.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-pwrite.html
* igt@kms_plane@plane-panning-bottom-right@pipe-a-planes:
- {shard-rkl}: [SKIP][76] ([i915#1849] / [i915#3558]) -> [PASS][77] +1 similar issue
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-5/igt@kms_plane@plane-panning-bottom-right@pipe-a-planes.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@kms_plane@plane-panning-bottom-right@pipe-a-planes.html
* igt@kms_plane_lowres@tiling-yf@pipe-c-hdmi-a-1:
- shard-glk: [FAIL][78] ([i915#7307]) -> [PASS][79]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-glk1/igt@kms_plane_lowres@tiling-yf@pipe-c-hdmi-a-1.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-glk8/igt@kms_plane_lowres@tiling-yf@pipe-c-hdmi-a-1.html
* igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [SKIP][80] ([i915#5235]) -> [PASS][81] +2 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb2/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-a-edp-1.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb6/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-a-edp-1.html
* igt@kms_properties@crtc-properties-legacy:
- {shard-rkl}: [SKIP][82] ([i915#1849]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-5/igt@kms_properties@crtc-properties-legacy.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@kms_properties@crtc-properties-legacy.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][84] ([fdo#109441]) -> [PASS][85] +2 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb6/igt@kms_psr@psr2_primary_mmap_cpu.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_psr@sprite_plane_move:
- {shard-rkl}: [SKIP][86] ([i915#1072]) -> [PASS][87] +1 similar issue
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-4/igt@kms_psr@sprite_plane_move.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-6/igt@kms_psr@sprite_plane_move.html
* igt@kms_psr_stress_test@flip-primary-invalidate-overlay:
- shard-tglb: [SKIP][88] ([i915#5519]) -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-tglb2/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-tglb7/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html
* igt@perf_pmu@module-unload:
- shard-skl: [DMESG-WARN][90] ([i915#1982]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-skl7/igt@perf_pmu@module-unload.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-skl4/igt@perf_pmu@module-unload.html
* igt@prime_vgem@basic-write:
- {shard-rkl}: [SKIP][92] ([fdo#109295] / [i915#3291] / [i915#3708]) -> [PASS][93]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-rkl-2/igt@prime_vgem@basic-write.html
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-rkl-5/igt@prime_vgem@basic-write.html
#### Warnings ####
* igt@gem_exec_balancer@parallel-ordering:
- shard-iclb: [FAIL][94] ([i915#6117]) -> [SKIP][95] ([i915#4525])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb2/igt@gem_exec_balancer@parallel-ordering.html
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb6/igt@gem_exec_balancer@parallel-ordering.html
* igt@gem_pread@exhaustion:
- shard-apl: [INCOMPLETE][96] ([i915#7248]) -> [WARN][97] ([i915#2658])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-apl6/igt@gem_pread@exhaustion.html
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-apl2/igt@gem_pread@exhaustion.html
- shard-glk: [WARN][98] ([i915#2658]) -> [INCOMPLETE][99] ([i915#7248]) +1 similar issue
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-glk1/igt@gem_pread@exhaustion.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-glk9/igt@gem_pread@exhaustion.html
* igt@gem_pwrite@basic-exhaustion:
- shard-apl: [WARN][100] ([i915#2658]) -> [INCOMPLETE][101] ([i915#7248])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-apl6/igt@gem_pwrite@basic-exhaustion.html
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-apl2/igt@gem_pwrite@basic-exhaustion.html
* igt@kms_plane_alpha_blend@alpha-basic@pipe-c-dp-1:
- shard-apl: [DMESG-FAIL][102] ([IGT#6]) -> [FAIL][103] ([i915#4573]) +1 similar issue
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-apl8/igt@kms_plane_alpha_blend@alpha-basic@pipe-c-dp-1.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-apl7/igt@kms_plane_alpha_blend@alpha-basic@pipe-c-dp-1.html
* igt@kms_psr2_sf@cursor-plane-update-sf:
- shard-iclb: [SKIP][104] ([i915#2920]) -> [SKIP][105] ([fdo#111068] / [i915#658])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb2/igt@kms_psr2_sf@cursor-plane-update-sf.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb7/igt@kms_psr2_sf@cursor-plane-update-sf.html
* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-sf:
- shard-iclb: [SKIP][106] ([i915#658]) -> [SKIP][107] ([i915#2920])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb8/igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-sf.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb2/igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-sf.html
* igt@kms_psr2_sf@overlay-plane-move-continuous-sf:
- shard-iclb: [SKIP][108] ([i915#2920]) -> [SKIP][109] ([i915#658])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb2/igt@kms_psr2_sf@overlay-plane-move-continuous-sf.html
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb5/igt@kms_psr2_sf@overlay-plane-move-continuous-sf.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
- shard-iclb: [SKIP][110] ([fdo#111068] / [i915#658]) -> [SKIP][111] ([i915#2920])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12382/shard-iclb8/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/shard-iclb2/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#6]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/6
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#109312]: https://bugs.freedesktop.org/show_bug.cgi?id=109312
[fdo#109313]: https://bugs.freedesktop.org/show_bug.cgi?id=109313
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[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#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1769]: https://gitlab.freedesktop.org/drm/intel/issues/1769
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1937]: https://gitlab.freedesktop.org/drm/intel/issues/1937
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2436]: https://gitlab.freedesktop.org/drm/intel/issues/2436
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[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#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#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[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#3318]: https://gitlab.freedesktop.org/drm/intel/issues/3318
[i915#3354]: https://gitlab.freedesktop.org/drm/intel/issues/3354
[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#3539]: https://gitlab.freedesktop.org/drm/intel/issues/3539
[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#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#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955
[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#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#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#4573]: https://gitlab.freedesktop.org/drm/intel/issues/4573
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[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#4859]: https://gitlab.freedesktop.org/drm/intel/issues/4859
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[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#5327]: https://gitlab.freedesktop.org/drm/intel/issues/5327
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5519]: https://gitlab.freedesktop.org/drm/intel/issues/5519
[i915#5563]: https://gitlab.freedesktop.org/drm/intel/issues/5563
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6117]: https://gitlab.freedesktop.org/drm/intel/issues/6117
[i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6344]: https://gitlab.freedesktop.org/drm/intel/issues/6344
[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#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#6991]: https://gitlab.freedesktop.org/drm/intel/issues/6991
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#7248]: https://gitlab.freedesktop.org/drm/intel/issues/7248
[i915#7307]: https://gitlab.freedesktop.org/drm/intel/issues/7307
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
Build changes
-------------
* Linux: CI_DRM_12382 -> Patchwork_110601v2
CI-20190529: 20190529
CI_DRM_12382: cb74864693414b221b3601572e75449558126e8b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7057: e2138d48c2c506816868c16cf3ba64f81bdead41 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_110601v2: cb74864693414b221b3601572e75449558126e8b @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110601v2/index.html
[-- Attachment #2: Type: text/html, Size: 32275 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2022-11-15 22:27 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-15 10:46 [PATCH v2] drm/i915/ttm: never purge busy objects Matthew Auld
2022-11-15 10:46 ` [Intel-gfx] " Matthew Auld
2022-11-15 13:45 ` Das, Nirmoy
2022-11-15 13:45 ` Das, Nirmoy
2022-11-15 16:20 ` Andrzej Hajda
2022-11-15 16:20 ` Andrzej Hajda
2022-11-15 16:30 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/ttm: never purge busy objects (rev2) Patchwork
2022-11-15 16:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-15 22:27 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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.