drm/i915: Prepare error capture for asynchronous migration
Subsystems (2)
v5 cover drm/i915: Prepare error capture for asynchronous migration
This patch series prepares error capture for asynchronous migration, where the vma pages may not reflect the pages the GPU is currently executing from but may be several migrations ahead.
The first patch introduces vma state snapshots that record the vma state at request submission time.
It also takes additional measures to make sure that
the capture list and request is not disappearing from under us while capturing. The latter may otherwise happen if a heartbeat triggered parallel capture is running during a manual reset which retires the request.
The second patch changes the allocation mode during capture to reflect that capturing is typically done in the fence signalling critical path. More details on the patch itself.
Finally the last patch is more of a POC patch and not strictly needed yet, but will be (or at least something very similar) soon for async unbinding. It will make sure that unbinding doesn't complete or signal completion before capture is done. Async reuse of memory can't happen until unbinding signals complete and without waiting for capture done, we might capture contents of reused memory.
Before the last patch the vma active is instead still keeping the vma alive, but that will not work with async unbinding anymore, and also it is still not clear how we guarantee keeping the vma alive long enough to even grab an active reference during capture.
v2:
- Mostly Fixes for selftests and rebinding. See patch 3. v3:
- Honor the unbind fence also when evicting for suspend on gen6.
- Minor cleanups on patch 3.
v4:
- Break out patch 2 from patch 1.
v5:
- Ditch a patch from the since it's already commited.
- Use __GFP_KSWAPD_RECLAIM rather than GFP_NOWAIT in patch 2.
Thomas Hellström (3):
drm/i915: Update error capture code to avoid using the current vma
state
drm/i915: Use __GFP_KSWAPD_RECLAIM in the capture code drm/i915: Initial introduction of vma resources
drivers/gpu/drm/i915/Makefile | 1 + .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 137 ++++++++++-- drivers/gpu/drm/i915/gt/intel_engine_cs.c | 8 +- .../drm/i915/gt/intel_execlists_submission.c | 2 +- drivers/gpu/drm/i915/i915_gpu_error.c | 180 ++++++++++----- drivers/gpu/drm/i915/i915_request.c | 63 ++++-- drivers/gpu/drm/i915/i915_request.h | 20 +- drivers/gpu/drm/i915/i915_vma.c | 206 +++++++++++++++++- drivers/gpu/drm/i915/i915_vma.h | 20 +- drivers/gpu/drm/i915/i915_vma_snapshot.c | 131 +++++++++++ drivers/gpu/drm/i915/i915_vma_snapshot.h | 112 ++++++++++ drivers/gpu/drm/i915/i915_vma_types.h | 5 + drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 98 +++++---- 13 files changed, 837 insertions(+), 146 deletions(-) create mode 100644 drivers/gpu/drm/i915/i915_vma_snapshot.c create mode 100644 drivers/gpu/drm/i915/i915_vma_snapshot.h
Signature · 1 line
2.31.1
PATCH v5 1/3 drm/i915: Update error capture code to avoid using the current vma state
With asynchronous migrations, the vma state may be several migrations ahead of the state that matches the request we're capturing. Address that by introducing an i915_vma_snapshot structure that can be used to snapshot relevant state at request submission. In order to make sure we access the correct memory, the snapshots take references on relevant sg-tables and memory regions.
Also move the capture list allocation out of the fence signaling critical path and use the CONFIG_DRM_I915_CAPTURE_ERROR define to avoid compiling in members and functions used for error capture when they're not used.
Finally, Introducing lockdep annotation means we will be start seeing lockdep splats in the capture code. This is because typically the capture code runs in the fence signalling critical path. These splats and the associated deadlocks will be worked around in an upcoming patch.
Splats look like these:
[ 234.842048] WARNING: possible circular locking dependency detected
[ 234.842050] 5.15.0-rc7+ #20 Tainted: G U W
[ 234.842052] ------------------------------------------------------
[ 234.842054] gem_exec_captur/1180 is trying to acquire lock:
[ 234.842056] ffffffffa3e51c00 (fs_reclaim){+.+.}-{0:0}, at: __kmalloc+0x4d/0x330
[ 234.842063]
but task is already holding lock:
[ 234.842064] ffffffffa3f57620 (dma_fence_map){++++}-{0:0}, at: i915_vma_snapshot_resource_pin+0x27/0x30 [i915]
[ 234.842138]
which lock already depends on the new lock.[ 234.842140]
the existing dependency chain (in reverse order) is:
[ 234.842142]
-> #2 (dma_fence_map){++++}-{0:0}:
[ 234.842145] __dma_fence_might_wait+0x41/0xa0
[ 234.842149] dma_resv_lockdep+0x1dc/0x28f
[ 234.842151] do_one_initcall+0x58/0x2d0
[ 234.842154] kernel_init_freeable+0x273/0x2bf
[ 234.842157] kernel_init+0x16/0x120
[ 234.842160] ret_from_fork+0x1f/0x30
[ 234.842163]
-> #1 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:
[ 234.842166] fs_reclaim_acquire+0x6d/0xd0
[ 234.842168] __kmalloc_node+0x51/0x3a0
[ 234.842171] alloc_cpumask_var_node+0x1b/0x30
[ 234.842174] native_smp_prepare_cpus+0xc7/0x292
[ 234.842177] kernel_init_freeable+0x160/0x2bf
[ 234.842179] kernel_init+0x16/0x120
[ 234.842181] ret_from_fork+0x1f/0x30
[ 234.842184]
-> #0 (fs_reclaim){+.+.}-{0:0}:
[ 234.842186] __lock_acquire+0x1161/0x1dc0
[ 234.842189] lock_acquire+0xb5/0x2b0
[ 234.842192] fs_reclaim_acquire+0xa1/0xd0
[ 234.842193] __kmalloc+0x4d/0x330
[ 234.842196] i915_vma_coredump_create+0x78/0x5b0 [i915]
[ 234.842253] intel_engine_coredump_add_vma+0x36/0xe0 [i915]
[ 234.842307] __i915_gpu_coredump+0x290/0x5e0 [i915]
[ 234.842365] i915_capture_error_state+0x57/0xa0 [i915]
[ 234.842415] intel_gt_handle_error+0x348/0x3e0 [i915]
[ 234.842462] intel_gt_debugfs_reset_store+0x3c/0x90 [i915]
[ 234.842504] simple_attr_write+0xc1/0xe0
[ 234.842507] full_proxy_write+0x53/0x80
[ 234.842509] vfs_write+0xbc/0x350
[ 234.842513] ksys_write+0x58/0xd0
[ 234.842514] do_syscall_64+0x38/0x90
[ 234.842516] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 234.842519]
other info that might help us debug this:[ 234.842521] Chain exists of:
fs_reclaim --> mmu_notifier_invalidate_range_start --> dma_fence_map[ 234.842526] Possible unsafe locking scenario:
[ 234.842528] CPU0 CPU1
[ 234.842529] ---- ----
[ 234.842531] lock(dma_fence_map);
[ 234.842532] lock(mmu_notifier_invalidate_range_start);
[ 234.842535] lock(dma_fence_map);
[ 234.842537] lock(fs_reclaim);
[ 234.842539]
*** DEADLOCK ***[ 234.842540] 4 locks held by gem_exec_captur/1180:
[ 234.842543] #0: ffff9007812d9460 (sb_writers#17){.+.+}-{0:0}, at: ksys_write+0x58/0xd0
[ 234.842547] #1: ffff900781d9ecb8 (&attr->mutex){+.+.}-{3:3}, at: simple_attr_write+0x3a/0xe0
[ 234.842552] #2: ffffffffc11913a8 (capture_mutex){+.+.}-{3:3}, at: i915_capture_error_state+0x1a/0xa0 [i915]
[ 234.842602] #3: ffffffffa3f57620 (dma_fence_map){++++}-{0:0}, at: i915_vma_snapshot_resource_pin+0x27/0x30 [i915]
[ 234.842656]
stack backtrace:
[ 234.842658] CPU: 0 PID: 1180 Comm: gem_exec_captur Tainted: G U W 5.15.0-rc7+ #20
[ 234.842661] Hardware name: ASUS System Product Name/PRIME B560M-A AC, BIOS 0403 01/26/2021
[ 234.842664] Call Trace:
[ 234.842666] dump_stack_lvl+0x57/0x72
[ 234.842669] check_noncircular+0xde/0x100
[ 234.842672] ? __lock_acquire+0x3bf/0x1dc0
[ 234.842675] __lock_acquire+0x1161/0x1dc0
[ 234.842678] lock_acquire+0xb5/0x2b0
[ 234.842680] ? __kmalloc+0x4d/0x330
[ 234.842683] ? finish_task_switch.isra.0+0xf2/0x360
[ 234.842686] ? i915_vma_coredump_create+0x78/0x5b0 [i915]
[ 234.842734] fs_reclaim_acquire+0xa1/0xd0
[ 234.842737] ? __kmalloc+0x4d/0x330
[ 234.842739] __kmalloc+0x4d/0x330
[ 234.842742] i915_vma_coredump_create+0x78/0x5b0 [i915]
[ 234.842793] ? capture_vma+0xbe/0x110 [i915]
[ 234.842844] intel_engine_coredump_add_vma+0x36/0xe0 [i915]
[ 234.842892] __i915_gpu_coredump+0x290/0x5e0 [i915]
[ 234.842939] i915_capture_error_state+0x57/0xa0 [i915]
[ 234.842985] intel_gt_handle_error+0x348/0x3e0 [i915]
[ 234.843032] ? __mutex_lock+0x81/0x830
[ 234.843035] ? simple_attr_write+0x3a/0xe0
[ 234.843038] ? __lock_acquire+0x3bf/0x1dc0
[ 234.843041] intel_gt_debugfs_reset_store+0x3c/0x90 [i915]
[ 234.843083] ? _copy_from_user+0x45/0x80
[ 234.843086] simple_attr_write+0xc1/0xe0
[ 234.843089] full_proxy_write+0x53/0x80
[ 234.843091] vfs_write+0xbc/0x350
[ 234.843094] ksys_write+0x58/0xd0
[ 234.843096] do_syscall_64+0x38/0x90
[ 234.843098] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 234.843101] RIP: 0033:0x7fa467480877
[ 234.843103] Code: 75 05 48 83 c4 58 c3 e8 37 4e ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24
[ 234.843108] RSP: 002b:00007ffd14d79b08 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[ 234.843112] RAX: ffffffffffffffda RBX: 00007ffd14d79b60 RCX: 00007fa467480877
[ 234.843114] RDX: 0000000000000014 RSI: 00007ffd14d79b60 RDI: 0000000000000007
[ 234.843116] RBP: 0000000000000007 R08: 0000000000000000 R09: 00007ffd14d79ab0
[ 234.843119] R10: ffffffffffffffff R11: 0000000000000246 R12: 0000000000000014
[ 234.843121] R13: 0000000000000000 R14: 00007ffd14d79b60 R15: 0000000000000005v4:
- Break out the capture allocation mode change to a separate patch. v5:
- Fix compilation error in the !CONFIG_DRM_I915_CAPTURE_ERROR case (kernel test robot)
--- drivers/gpu/drm/i915/Makefile | 1 + .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 135 ++++++++++--- drivers/gpu/drm/i915/gt/intel_engine_cs.c | 8 +- .../drm/i915/gt/intel_execlists_submission.c | 2 +- drivers/gpu/drm/i915/i915_gpu_error.c | 178 +++++++++++++----- drivers/gpu/drm/i915/i915_request.c | 63 +++++-- drivers/gpu/drm/i915/i915_request.h | 20 +- drivers/gpu/drm/i915/i915_vma_snapshot.c | 137 ++++++++++++++ drivers/gpu/drm/i915/i915_vma_snapshot.h | 112 +++++++++++ 9 files changed, 559 insertions(+), 97 deletions(-) create mode 100644 drivers/gpu/drm/i915/i915_vma_snapshot.c create mode 100644 drivers/gpu/drm/i915/i915_vma_snapshot.h
drivers/gpu/drm/i915/Makefile +1 -0
@@ -173,6 +173,7 @@ i915-y += \ i915_trace_points.o \ i915_ttm_buddy_manager.o \ i915_vma.o \ + i915_vma_snapshot.o \ intel_wopcm.o # general-purpose microcontroller (GuC) support
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c +112 -23
202 lines not on this page · raw message
drivers/gpu/drm/i915/gt/intel_engine_cs.c +6 -2
@@ -1676,14 +1676,18 @@ static void intel_engine_print_registers(struct intel_engine_cs *engine,static void print_request_ring (struct drm_printer *m,struct i915_request *rq) { +struct i915_vma_snapshot *vsnap = &rq->batch_snapshot;void *ring;int size; +if (!i915_vma_snapshot_present (vsnap)) + vsnap =NULL ; +drm_printf (m,"[head %04x, postfix %04x, tail %04x, batch 0x%08x_%08x]:\n" , rq->head, rq->postfix, rq->tail, - rq->batch ?upper_32_bits (rq->batch->node.start) : ~0u , - rq->batch ?lower_32_bits (rq->batch->node.start) : ~0u ); + vsnap ?upper_32_bits (vsnap->gtt_offset) : ~0u , + vsnap ?lower_32_bits (vsnap->gtt_offset) : ~0u ); size = rq->tail - rq->head;if (rq->tail < rq->head)
drivers/gpu/drm/i915/gt/intel_execlists_submission.c +1 -1
@@ -2186,7 +2186,7 @@ struct execlists_capture {static void execlists_capture_work (struct work_struct *work) {struct execlists_capture *cap =container_of (work,typeof (*cap), work); -const gfp_t gfp =GFP_KERNEL | __GFP_RETRY_MAYFAIL | __GFP_NOWARN; +const gfp_t gfp =GFP_NOWAIT | __GFP_RETRY_MAYFAIL | __GFP_NOWARN;struct intel_engine_cs *engine = cap->rq->engine;struct intel_gt_coredump *gt = cap->error->gt;struct intel_engine_capture_vma *vma;
drivers/gpu/drm/i915/i915_gpu_error.c +129 -49
318 lines not on this page · raw message
drivers/gpu/drm/i915/i915_request.c +46 -17
105 lines not on this page · raw message
drivers/gpu/drm/i915/i915_request.h +15 -5
@@ -40,6 +40,7 @@#include "i915_scheduler.h" #include "i915_selftest.h" #include "i915_sw_fence.h" +#include "i915_vma_snapshot.h" #include <uapi/drm/i915_drm.h>
@@ -48,11 +49,17 @@ struct drm_i915_gem_object;struct drm_printer ;struct i915_request ; +#ifdef CONFIG_DRM_I915_CAPTURE_ERROR struct i915_capture_list { +struct i915_vma_snapshot *vma_snapshot;struct i915_capture_list *next; -struct i915_vma *vma; }; +void i915_request_free_capture_list (struct i915_capture_list *capture); +#else +#define i915_request_free_capture_list (_a) do {} while (0) +#endif +#define RQ_TRACE (rq, fmt, ...) do { \ const struct i915_request *rq__ = (rq); \ ENGINE_TRACE(rq__->engine, "fence %llx:%lld, current %d " fmt, \
@@ -289,10 +296,12 @@ struct i915_request {/** Preallocate space in the ring for the emitting the request */ u32 reserved_space; -/** Batch buffer related to this request if any (used for -* error state dump only). -*/ -struct i915_vma *batch; +/** Batch buffer pointer for selftest internal use. */ + I915_SELFTEST_DECLARE(struct i915_vma *batch); + +struct i915_vma_snapshot batch_snapshot; + +#ifdef CONFIG_DRM_I915_CAPTURE_ERROR /** * Additional buffers requested by userspace to be captured upon * a GPU hang. The vma/obj on this list are protected by their
@@ -300,6 +309,7 @@ struct i915_request {* on the active_list (of their final request). */ struct i915_capture_list *capture_list; +#endif /** Time at which this request was emitted, in jiffies. */ unsigned long emitted_jiffies;
drivers/gpu/drm/i915/i915_vma_snapshot.c new file +137 -0
137 lines not on this page · raw message
drivers/gpu/drm/i915/i915_vma_snapshot.h new file +112 -0
112 lines not on this page · raw message
Signature · 1 line
2.31.1
PATCH v5 2/3 drm/i915: Use __GFP_KSWAPD_RECLAIM in the capture code
In reply to Thomas HellströmThe capture code is typically run entirely in the fence signalling critical path. Recently added lockdep annotation reveals a lockdep splat similar to the below one.
Fix the splats and the associated potential deadlocks using __GFP_KSWAPD_RECLAIM (which is the same as GFP_WAIT, but open-coded for clarity) rather than GFP_KERNEL for memory allocation in the capture path. This has the potential drawback that capture might fail in situations with memory pressure.
[ 234.842048] WARNING: possible circular locking dependency detected
[ 234.842050] 5.15.0-rc7+ #20 Tainted: G U W
[ 234.842052] ------------------------------------------------------
[ 234.842054] gem_exec_captur/1180 is trying to acquire lock:
[ 234.842056] ffffffffa3e51c00 (fs_reclaim){+.+.}-{0:0}, at: __kmalloc+0x4d/0x330
[ 234.842063]
but task is already holding lock:
[ 234.842064] ffffffffa3f57620 (dma_fence_map){++++}-{0:0}, at: i915_vma_snapshot_resource_pin+0x27/0x30 [i915]
[ 234.842138]
which lock already depends on the new lock.[ 234.842140]
the existing dependency chain (in reverse order) is:
[ 234.842142]
-> #2 (dma_fence_map){++++}-{0:0}:
[ 234.842145] __dma_fence_might_wait+0x41/0xa0
[ 234.842149] dma_resv_lockdep+0x1dc/0x28f
[ 234.842151] do_one_initcall+0x58/0x2d0
[ 234.842154] kernel_init_freeable+0x273/0x2bf
[ 234.842157] kernel_init+0x16/0x120
[ 234.842160] ret_from_fork+0x1f/0x30
[ 234.842163]
-> #1 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:
[ 234.842166] fs_reclaim_acquire+0x6d/0xd0
[ 234.842168] __kmalloc_node+0x51/0x3a0
[ 234.842171] alloc_cpumask_var_node+0x1b/0x30
[ 234.842174] native_smp_prepare_cpus+0xc7/0x292
[ 234.842177] kernel_init_freeable+0x160/0x2bf
[ 234.842179] kernel_init+0x16/0x120
[ 234.842181] ret_from_fork+0x1f/0x30
[ 234.842184]
-> #0 (fs_reclaim){+.+.}-{0:0}:
[ 234.842186] __lock_acquire+0x1161/0x1dc0
[ 234.842189] lock_acquire+0xb5/0x2b0
[ 234.842192] fs_reclaim_acquire+0xa1/0xd0
[ 234.842193] __kmalloc+0x4d/0x330
[ 234.842196] i915_vma_coredump_create+0x78/0x5b0 [i915]
[ 234.842253] intel_engine_coredump_add_vma+0x36/0xe0 [i915]
[ 234.842307] __i915_gpu_coredump+0x290/0x5e0 [i915]
[ 234.842365] i915_capture_error_state+0x57/0xa0 [i915]
[ 234.842415] intel_gt_handle_error+0x348/0x3e0 [i915]
[ 234.842462] intel_gt_debugfs_reset_store+0x3c/0x90 [i915]
[ 234.842504] simple_attr_write+0xc1/0xe0
[ 234.842507] full_proxy_write+0x53/0x80
[ 234.842509] vfs_write+0xbc/0x350
[ 234.842513] ksys_write+0x58/0xd0
[ 234.842514] do_syscall_64+0x38/0x90
[ 234.842516] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 234.842519]
other info that might help us debug this:[ 234.842521] Chain exists of:
fs_reclaim --> mmu_notifier_invalidate_range_start --> dma_fence_map[ 234.842526] Possible unsafe locking scenario:
[ 234.842528] CPU0 CPU1
[ 234.842529] ---- ----
[ 234.842531] lock(dma_fence_map);
[ 234.842532] lock(mmu_notifier_invalidate_range_start);
[ 234.842535] lock(dma_fence_map);
[ 234.842537] lock(fs_reclaim);
[ 234.842539]
*** DEADLOCK ***[ 234.842540] 4 locks held by gem_exec_captur/1180:
[ 234.842543] #0: ffff9007812d9460 (sb_writers#17){.+.+}-{0:0}, at: ksys_write+0x58/0xd0
[ 234.842547] #1: ffff900781d9ecb8 (&attr->mutex){+.+.}-{3:3}, at: simple_attr_write+0x3a/0xe0
[ 234.842552] #2: ffffffffc11913a8 (capture_mutex){+.+.}-{3:3}, at: i915_capture_error_state+0x1a/0xa0 [i915]
[ 234.842602] #3: ffffffffa3f57620 (dma_fence_map){++++}-{0:0}, at: i915_vma_snapshot_resource_pin+0x27/0x30 [i915]
[ 234.842656]
stack backtrace:
[ 234.842658] CPU: 0 PID: 1180 Comm: gem_exec_captur Tainted: G U W 5.15.0-rc7+ #20
[ 234.842661] Hardware name: ASUS System Product Name/PRIME B560M-A AC, BIOS 0403 01/26/2021
[ 234.842664] Call Trace:
[ 234.842666] dump_stack_lvl+0x57/0x72
[ 234.842669] check_noncircular+0xde/0x100
[ 234.842672] ? __lock_acquire+0x3bf/0x1dc0
[ 234.842675] __lock_acquire+0x1161/0x1dc0
[ 234.842678] lock_acquire+0xb5/0x2b0
[ 234.842680] ? __kmalloc+0x4d/0x330
[ 234.842683] ? finish_task_switch.isra.0+0xf2/0x360
[ 234.842686] ? i915_vma_coredump_create+0x78/0x5b0 [i915]
[ 234.842734] fs_reclaim_acquire+0xa1/0xd0
[ 234.842737] ? __kmalloc+0x4d/0x330
[ 234.842739] __kmalloc+0x4d/0x330
[ 234.842742] i915_vma_coredump_create+0x78/0x5b0 [i915]
[ 234.842793] ? capture_vma+0xbe/0x110 [i915]
[ 234.842844] intel_engine_coredump_add_vma+0x36/0xe0 [i915]
[ 234.842892] __i915_gpu_coredump+0x290/0x5e0 [i915]
[ 234.842939] i915_capture_error_state+0x57/0xa0 [i915]
[ 234.842985] intel_gt_handle_error+0x348/0x3e0 [i915]
[ 234.843032] ? __mutex_lock+0x81/0x830
[ 234.843035] ? simple_attr_write+0x3a/0xe0
[ 234.843038] ? __lock_acquire+0x3bf/0x1dc0
[ 234.843041] intel_gt_debugfs_reset_store+0x3c/0x90 [i915]
[ 234.843083] ? _copy_from_user+0x45/0x80
[ 234.843086] simple_attr_write+0xc1/0xe0
[ 234.843089] full_proxy_write+0x53/0x80
[ 234.843091] vfs_write+0xbc/0x350
[ 234.843094] ksys_write+0x58/0xd0
[ 234.843096] do_syscall_64+0x38/0x90
[ 234.843098] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 234.843101] RIP: 0033:0x7fa467480877
[ 234.843103] Code: 75 05 48 83 c4 58 c3 e8 37 4e ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24
[ 234.843108] RSP: 002b:00007ffd14d79b08 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[ 234.843112] RAX: ffffffffffffffda RBX: 00007ffd14d79b60 RCX: 00007fa467480877
[ 234.843114] RDX: 0000000000000014 RSI: 00007ffd14d79b60 RDI: 0000000000000007
[ 234.843116] RBP: 0000000000000007 R08: 0000000000000000 R09: 00007ffd14d79ab0
[ 234.843119] R10: ffffffffffffffff R11: 0000000000000246 R12: 0000000000000014
[ 234.843121] R13: 0000000000000000 R14: 00007ffd14d79b60 R15: 0000000000000005v5:
- Use __GFP_KSWAPD_RECLAIM rather than __GFP_NOWAIT for clarity. (Daniel Vetter)
--- drivers/gpu/drm/i915/i915_gpu_error.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_gpu_error.c +1 -1
@@ -50,7 +50,7 @@#include "i915_scatterlist.h" #include "i915_vma_snapshot.h" -#define ALLOW_FAIL (GFP_KERNEL | __GFP_RETRY_MAYFAIL | __GFP_NOWARN) +#define ALLOW_FAIL (__GFP_KSWAPD_RECLAIM | __GFP_RETRY_MAYFAIL | __GFP_NOWARN)#define ATOMIC_MAYFAIL (GFP_ATOMIC | __GFP_NOWARN) static void __sg_set_buf(struct scatterlist *sg,
Signature · 1 line
2.31.1
PATCH v5 3/3 drm/i915: Initial introduction of vma resources
In reply to Thomas HellströmThe vma resource are needed for asynchronous bind management and are similar to TTM resources. They contain the data needed for asynchronous unbinding (typically the vm range, any backend private information and a means to do refcounting and to hold the unbinding for error capture).
When a vma is bound, a vma resource is created and attached to the vma, and on async unbinding it is detached from the vma, and instead the vm records the fence marking unbind complete. This fence needs to be waited on before we can bind the same region again, so either the fence can be recorded for this particular range only, using an interval tree, or as a simpler approach, for the whole vm. The latter means no binding can take place on a vm until all detached vma resources scheduled for unbind are signaled. With an interval tree fence recording, the interval tree needs to be searched for fences to be signaled before binding can take place.
But most of that is for later, this patch only introduces stub vma resources without unbind capability and the fences of which are waited for sync during unbinding. At this point we're interested in the hold capability as a POC for error capture. Note that the current sync waiting at unbind time is done uninterruptible, but that's OK since we're only ever waiting during error capture, and in that case there's very little gpu activity (if any) that can stall.
v2:
- Fix the mock gtt selftest to bind with vma resources.
- Update a code comment.
- Account for rebinding the same vma with different I915_VMA_*_BIND flags v3:
- Some style fixups.
- Move the sync fence wait to __i915_vma_evict instead of __i915_vma_unbind to catch also the evict case on suspend.
v4:
- Remove a minor fix that incorrectly landed in this patch.
--- .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 2 +- drivers/gpu/drm/i915/i915_vma.c | 206 +++++++++++++++++- drivers/gpu/drm/i915/i915_vma.h | 20 +- drivers/gpu/drm/i915/i915_vma_snapshot.c | 14 +- drivers/gpu/drm/i915/i915_vma_snapshot.h | 2 +- drivers/gpu/drm/i915/i915_vma_types.h | 5 + drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 98 +++++---- 7 files changed, 288 insertions(+), 59 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c +1 -1
@@ -1376,7 +1376,7 @@ eb_relocate_entry(struct i915_execbuffer *eb, GRAPHICS_VER(eb->i915) == 6) { err =i915_vma_bind (target->vma, target->vma->obj->cache_level, -PIN_GLOBAL ,NULL ); +PIN_GLOBAL ,NULL ,NULL );if (err)return err; }
drivers/gpu/drm/i915/i915_vma.c +200 -6
298 lines not on this page · raw message
drivers/gpu/drm/i915/i915_vma.h +19 -1
@@ -206,7 +206,8 @@ struct i915_vma_work *i915_vma_work(void);int i915_vma_bind (struct i915_vma *vma,enum i915_cache_level cache_level,u32 flags, -struct i915_vma_work *work); +struct i915_vma_work *work, +struct i915_vma_resource *vma_res);bool i915_gem_valid_gtt_space (struct i915_vma *vma,unsigned long color); bool i915_vma_misplaced(const struct i915_vma *vma,
@@ -433,7 +434,24 @@ static inline int i915_vma_sync(struct i915_vma *vma) return i915_active_wait(&vma->active); } +bool i915_vma_resource_hold (struct i915_vma_resource *vma_res, +bool *lockdep_cookie); + +void i915_vma_resource_unhold (struct i915_vma_resource *vma_res, +bool lockdep_cookie); + +void i915_vma_resource_put (struct i915_vma_resource *vma_res); + +struct i915_vma_resource *i915_vma_get_current_resource (struct i915_vma *vma); + +struct i915_vma_resource *i915_vma_resource_alloc (void ); +void i915_vma_module_exit (void );int i915_vma_module_init (void ); +#ifdef CONFIG_DRM_I915_SELFTEST +void i915_vma_resource_init (struct i915_vma_resource *vma_res, +struct i915_vma *vma); +#endif +#endif
drivers/gpu/drm/i915/i915_vma_snapshot.c +4 -10
@@ -36,7 +36,7 @@ void i915_vma_snapshot_init(struct i915_vma_snapshot *vsnap,if (vma->obj->mm.region) vsnap->mr =intel_memory_region_get (vma->obj->mm.region);kref_init (&vsnap->kref); - vsnap->vma_resource = &vma->active; + vsnap->vma_resource =i915_vma_get_current_resource (vma); vsnap->onstack = false; vsnap->present = true; }
@@ -63,6 +63,7 @@ static void vma_snapshot_release(struct kref *ref)container_of (ref,typeof (*vsnap), kref); vsnap->present = false; +i915_vma_resource_put (vsnap->vma_resource);if (vsnap->mr)intel_memory_region_put (vsnap->mr);if (vsnap->pages_rsgt)
@@ -112,12 +113,7 @@ void i915_vma_snapshot_put_onstack(struct i915_vma_snapshot *vsnap)bool i915_vma_snapshot_resource_pin (struct i915_vma_snapshot *vsnap,bool *lockdep_cookie) { -bool pinned =i915_active_acquire_if_busy (vsnap->vma_resource); - -if (pinned) - *lockdep_cookie =dma_fence_begin_signalling (); - -return pinned; +return i915_vma_resource_hold (vsnap->vma_resource, lockdep_cookie); }/**
@@ -131,7 +127,5 @@ bool i915_vma_snapshot_resource_pin(struct i915_vma_snapshot *vsnap,void i915_vma_snapshot_resource_unpin (struct i915_vma_snapshot *vsnap,bool lockdep_cookie) { -dma_fence_end_signalling (lockdep_cookie); - -return i915_active_release (vsnap->vma_resource); +i915_vma_resource_unhold (vsnap->vma_resource, lockdep_cookie); }
drivers/gpu/drm/i915/i915_vma_snapshot.h +1 -1
@@ -49,7 +49,7 @@ struct i915_vma_snapshot {struct i915_refct_sgt *pages_rsgt;struct intel_memory_region *mr;struct kref kref; -struct i915_active *vma_resource; +struct i915_vma_resource *vma_resource;u32 page_sizes; bool onstack:1; bool present:1;
drivers/gpu/drm/i915/i915_vma_types.h +5 -0
@@ -95,6 +95,8 @@ enum i915_cache_level;* */ +struct i915_vma_resource ; +struct intel_remapped_plane_info {/* in gtt pages */ u32 offset;
@@ -284,6 +286,9 @@ struct i915_vma {struct list_head evict_link;struct list_head closed_link; + +/** The async vma resource. Protected by the vm_mutex */ + struct i915_vma_resource *resource; };#endif
drivers/gpu/drm/i915/selftests/i915_gem_gtt.c +58 -40
152 lines not on this page · raw message
Signature · 1 line
2.31.1
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Prepare error capture for asynchronous migration
In reply to Thomas Hellström== Series Details ==
== Series Details ==
Series: drm/i915: Prepare error capture for asynchronous migration
URL : https://patchwork.freedesktop.org/series/96493/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 4fd880f7f960 drm/i915: Update error capture code to avoid using the current vma state -:923: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #923: new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 957 lines checked 9378a0be88f4 drm/i915: Use __GFP_KSWAPD_RECLAIM in the capture code 1c9961abf806 drm/i915: Initial introduction of vma resources
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Prepare error capture for asynchronous migration
In reply to Thomas Hellström== Series Details ==
== Series Details ==
Series: drm/i915: Prepare error capture for asynchronous migration
URL : https://patchwork.freedesktop.org/series/96493/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10827 -> Patchwork_21503
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/index.html
Participating hosts (39 -> 34)
------------------------------
Missing (5): bat-dg1-6 fi-bsw-cyan fi-icl-u2 bat-adlp-4 fi-pnv-d510
Known issues
------------
Here are the changes found in Patchwork_21503 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@debugfs_test@read_all_entries:
- fi-apl-guc: [PASS][1] -> [DMESG-WARN][2] ([i915#1610])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/fi-apl-guc/igt@debugfs_test@read_all_entries.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/fi-apl-guc/igt@debugfs_test@read_all_entries.html
#### Possible fixes ####
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [DMESG-WARN][3] ([i915#4269]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/fi-cml-u2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/fi-cml-u2/igt@[email protected]
[i915#1610]: https://gitlab.freedesktop.org/drm/intel/issues/1610
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
Build changes
-------------
* Linux: CI_DRM_10827 -> Patchwork_21503
CI-20190529: 20190529
CI_DRM_10827: e6d8dc4d0d95b13d1575f02beead4517de3ee045 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6267: 5c3b8f7ad9a5cfe1f0e747d92da7910243cf287d @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21503: 1c9961abf806f10cf7c0ff761991288f5128debf @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
1c9961abf806 drm/i915: Initial introduction of vma resources 9378a0be88f4 drm/i915: Use __GFP_KSWAPD_RECLAIM in the capture code 4fd880f7f960 drm/i915: Update error capture code to avoid using the current vma state
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Prepare error capture for asynchronous migration
In reply to Thomas Hellström== Series Details ==
== Series Details ==
Series: drm/i915: Prepare error capture for asynchronous migration
URL : https://patchwork.freedesktop.org/series/96493/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10827_full -> Patchwork_21503_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_21503_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_21503_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_21503_full:
### Piglit changes ###
#### Possible regressions ####
* spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-2darray (NEW):
- pig-kbl-iris: NOTRUN -> [INCOMPLETE][1] +5 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/pig-kbl-iris/spec@arb_gpu_shader5@[email protected]
New tests
---------
New tests have been introduced between CI_DRM_10827_full and Patchwork_21503_full:
### New Piglit tests (6) ###
* spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-2darray:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-2drect:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-cubearray:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegatheroffset@fs-r-0-unorm-2darray:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegatheroffsets@fs-r-0-unorm-2d:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
* spec@arb_gpu_shader5@texturegatheroffsets@fs-r-0-unorm-2darray:
- Statuses : 1 incomplete(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_21503_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@preservation-s3@vecs0:
- shard-kbl: [PASS][2] -> [DMESG-WARN][3] ([i915#180]) +5 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-kbl7/igt@gem_ctx_isolation@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl1/igt@gem_ctx_isolation@[email protected]
* igt@gem_ctx_persistence@legacy-engines-hang@blt:
- shard-skl: NOTRUN -> [SKIP][4] ([fdo#109271]) +272 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl4/igt@gem_ctx_persistence@[email protected]
* igt@gem_eio@in-flight-contexts-immediate:
- shard-iclb: [PASS][5] -> [TIMEOUT][6] ([i915#3070])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb8/igt@[email protected]
* igt@gem_exec_fair@basic-deadline:
- shard-skl: NOTRUN -> [FAIL][7] ([i915#2846])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl6/igt@[email protected]
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [PASS][8] -> [FAIL][9] ([i915#2842]) +1 similar issue
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-kbl7/igt@gem_exec_fair@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: NOTRUN -> [FAIL][10] ([i915#2842]) +2 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_whisper@basic-queues-all:
- shard-glk: NOTRUN -> [DMESG-WARN][11] ([i915#118])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-glk3/igt@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-skl: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#2190])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl4/igt@[email protected]
* igt@gem_render_copy@x-tiled-to-vebox-yf-tiled:
- shard-kbl: NOTRUN -> [SKIP][13] ([fdo#109271]) +133 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl2/igt@[email protected]
* igt@gem_softpin@evict-snoop-interruptible:
- shard-tglb: NOTRUN -> [SKIP][14] ([fdo#109312])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@gen9_exec_parse@bb-chained:
- shard-tglb: NOTRUN -> [SKIP][15] ([i915#2856]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb1/igt@[email protected]
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-tglb: NOTRUN -> [SKIP][16] ([i915#1904])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb8/igt@[email protected]
* igt@i915_pm_dc@dc6-dpms:
- shard-skl: NOTRUN -> [FAIL][17] ([i915#454])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl9/igt@[email protected]
* igt@i915_pm_lpsp@screens-disabled:
- shard-tglb: NOTRUN -> [SKIP][18] ([i915#1902])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@i915_pm_rpm@gem-execbuf-stress-pc8:
- shard-glk: NOTRUN -> [SKIP][19] ([fdo#109271]) +37 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-glk3/igt@[email protected]
* igt@i915_pm_rpm@modeset-pc8-residency-stress:
- shard-tglb: NOTRUN -> [SKIP][20] ([fdo#109506] / [i915#2411])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@kms_big_fb@linear-32bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][21] ([fdo#111614])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb8/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-kbl: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#3777])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl7/igt@[email protected]
- shard-glk: NOTRUN -> [SKIP][23] ([fdo#109271] / [i915#3777])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-glk3/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip:
- shard-skl: NOTRUN -> [FAIL][24] ([i915#3743]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl7/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html
* igt@kms_big_fb@yf-tiled-16bpp-rotate-180:
- shard-tglb: NOTRUN -> [SKIP][25] ([fdo#111615]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-skl: NOTRUN -> [SKIP][26] ([fdo#109271] / [i915#3777]) +3 similar issues
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl7/igt@[email protected]
* igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][27] ([fdo#109271] / [i915#3886]) +16 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl7/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][28] ([i915#3689]) +2 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb8/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_ccs.html
* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][29] ([i915#3689] / [i915#3886]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#3886]) +1 similar issue
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-glk3/igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs:
- shard-kbl: NOTRUN -> [SKIP][31] ([fdo#109271] / [i915#3886]) +6 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl2/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][32] ([fdo#109271] / [i915#3886]) +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-apl4/igt@kms_ccs@pipe-c-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-d-bad-pixel-format-y_tiled_ccs:
- shard-snb: NOTRUN -> [SKIP][33] ([fdo#109271]) +37 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-snb5/igt@kms_ccs@pipe-d-bad-pixel-format-y_tiled_ccs.html
* igt@kms_chamelium@hdmi-aspect-ratio:
- shard-glk: NOTRUN -> [SKIP][34] ([fdo#109271] / [fdo#111827]) +3 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-glk3/igt@[email protected]
- shard-skl: NOTRUN -> [SKIP][35] ([fdo#109271] / [fdo#111827]) +24 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl6/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-storm:
- shard-kbl: NOTRUN -> [SKIP][36] ([fdo#109271] / [fdo#111827]) +13 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl2/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][37] ([fdo#109284] / [fdo#111827]) +3 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-with-enabled-mode:
- shard-snb: NOTRUN -> [SKIP][38] ([fdo#109271] / [fdo#111827]) +2 similar issues
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-snb5/igt@[email protected]
* igt@kms_color_chamelium@pipe-b-ctm-0-75:
- shard-apl: NOTRUN -> [SKIP][39] ([fdo#109271] / [fdo#111827])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-apl4/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-kbl: NOTRUN -> [TIMEOUT][40] ([i915#1319])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl2/igt@[email protected]
* igt@kms_content_protection@uevent:
- shard-apl: NOTRUN -> [FAIL][41] ([i915#2105])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-apl4/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-32x32-sliding:
- shard-tglb: NOTRUN -> [SKIP][42] ([i915#3319])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-max-size-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][43] ([i915#3359]) +2 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb8/igt@[email protected]
* igt@kms_cursor_crc@pipe-d-cursor-512x170-offscreen:
- shard-tglb: NOTRUN -> [SKIP][44] ([fdo#109279] / [i915#3359])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: NOTRUN -> [FAIL][45] ([i915#2346] / [i915#533])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@pipe-d-single-bo:
- shard-apl: NOTRUN -> [SKIP][46] ([fdo#109271] / [i915#533])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-apl4/igt@[email protected]
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-kbl: [PASS][47] -> [INCOMPLETE][48] ([i915#180] / [i915#636])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-kbl3/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl1/igt@[email protected]
* igt@kms_flip@flip-vs-absolute-wf_vblank@a-edp1:
- shard-skl: [PASS][49] -> [FAIL][50] ([i915#2122]) +1 similar issue
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-skl8/igt@kms_flip@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl3/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@c-edp1:
- shard-skl: NOTRUN -> [FAIL][51] ([i915#79])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl2/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@c-edp1:
- shard-skl: NOTRUN -> [INCOMPLETE][52] ([i915#198])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl9/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@a-dp1:
- shard-apl: [PASS][53] -> [DMESG-WARN][54] ([i915#180]) +2 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-apl7/igt@kms_flip@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-apl1/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs:
- shard-skl: NOTRUN -> [INCOMPLETE][55] ([i915#3699])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl6/igt@[email protected]
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile:
- shard-iclb: [PASS][56] -> [SKIP][57] ([i915#3701])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb7/igt@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb2/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-mmap-gtt:
- shard-tglb: NOTRUN -> [SKIP][58] ([fdo#111825]) +13 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-mmap-gtt.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-pwrite:
- shard-apl: NOTRUN -> [SKIP][59] ([fdo#109271]) +21 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-apl4/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-pwrite.html
* igt@kms_pipe_b_c_ivb@pipe-b-double-modeset-then-modeset-pipe-c:
- shard-tglb: NOTRUN -> [SKIP][60] ([fdo#109289])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@kms_pipe_crc_basic@hang-read-crc-pipe-d:
- shard-skl: NOTRUN -> [SKIP][61] ([fdo#109271] / [i915#533]) +1 similar issue
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl7/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: NOTRUN -> [DMESG-WARN][62] ([i915#180])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-skl: NOTRUN -> [FAIL][63] ([fdo#108145] / [i915#265]) +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
- shard-kbl: NOTRUN -> [FAIL][64] ([i915#265])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl2/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-alpha-basic:
- shard-kbl: NOTRUN -> [FAIL][65] ([fdo#108145] / [i915#265]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl2/igt@[email protected]
* igt@kms_plane_lowres@pipe-d-tiling-none:
- shard-tglb: NOTRUN -> [SKIP][66] ([i915#3536])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb8/igt@[email protected]
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
- shard-glk: NOTRUN -> [SKIP][67] ([fdo#109271] / [i915#658])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-glk3/igt@[email protected]
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-skl: NOTRUN -> [SKIP][68] ([fdo#109271] / [i915#658]) +4 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl9/igt@[email protected]
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-kbl: NOTRUN -> [SKIP][69] ([fdo#109271] / [i915#658]) +3 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl3/igt@[email protected]
* igt@kms_psr@psr2_cursor_render:
- shard-iclb: [PASS][70] -> [SKIP][71] ([fdo#109441])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb2/igt@kms_psr@psr2_cursor_render.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb8/igt@kms_psr@psr2_cursor_render.html
- shard-tglb: NOTRUN -> [FAIL][72] ([i915#132] / [i915#3467])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb8/igt@kms_psr@psr2_cursor_render.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: NOTRUN -> [DMESG-WARN][73] ([i915#180] / [i915#295])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl6/igt@[email protected]
* igt@kms_vblank@pipe-d-wait-idle:
- shard-kbl: NOTRUN -> [SKIP][74] ([fdo#109271] / [i915#533]) +2 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl4/igt@[email protected]
* igt@kms_writeback@writeback-invalid-parameters:
- shard-skl: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#2437])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl2/igt@[email protected]
* igt@nouveau_crc@pipe-c-ctx-flip-skip-current-frame:
- shard-tglb: NOTRUN -> [SKIP][76] ([i915#2530]) +1 similar issue
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb8/igt@[email protected]
* igt@prime_nv_test@nv_i915_sharing:
- shard-tglb: NOTRUN -> [SKIP][77] ([fdo#109291])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@prime_nv_test@nv_i915_sharing.html
* igt@prime_vgem@coherency-gtt:
- shard-tglb: NOTRUN -> [SKIP][78] ([fdo#111656])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@sysfs_clients@fair-0:
- shard-skl: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#2994]) +3 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl2/igt@[email protected]
* igt@sysfs_clients@split-10:
- shard-glk: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#2994])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-glk3/igt@[email protected]
* igt@sysfs_clients@split-25:
- shard-kbl: NOTRUN -> [SKIP][81] ([fdo#109271] / [i915#2994]) +1 similar issue
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl3/igt@[email protected]
#### Possible fixes ####
* igt@gem_eio@in-flight-contexts-1us:
- shard-tglb: [TIMEOUT][82] ([i915#3063]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-tglb6/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@[email protected]
* igt@gem_exec_fair@basic-none@vecs0:
- shard-kbl: [FAIL][84] ([i915#2842]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-kbl7/igt@gem_exec_fair@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-tglb: [FAIL][86] ([i915#2842]) -> [PASS][87]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-tglb8/igt@gem_exec_fair@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb8/igt@gem_exec_fair@[email protected]
* igt@i915_pm_dc@dc6-dpms:
- shard-iclb: [FAIL][88] ([i915#454]) -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb3/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb4/igt@[email protected]
* igt@i915_selftest@live@hangcheck:
- shard-snb: [INCOMPLETE][90] ([i915#3921]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-snb5/igt@i915_selftest@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-snb5/igt@i915_selftest@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-apl: [DMESG-WARN][92] ([i915#180]) -> [PASS][93]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-apl1/igt@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-apl4/igt@[email protected]
* igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@c-edp1:
- shard-skl: [FAIL][94] ([i915#2122]) -> [PASS][95] +1 similar issue
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-skl3/igt@kms_flip@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a2:
- shard-glk: [FAIL][96] ([i915#79]) -> [PASS][97]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-glk8/igt@kms_flip@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-glk6/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@a-edp1:
- shard-tglb: [INCOMPLETE][98] ([i915#2411] / [i915#456]) -> [PASS][99]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-tglb7/igt@kms_flip@[email protected]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb6/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: [DMESG-WARN][100] ([i915#180]) -> [PASS][101] +10 similar issues
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-kbl6/igt@kms_flip@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-kbl2/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile:
- shard-iclb: [SKIP][102] ([i915#3701]) -> [PASS][103]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb2/igt@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb8/igt@[email protected]
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [FAIL][104] ([i915#1188]) -> [PASS][105]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-skl9/igt@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-glk: [DMESG-WARN][106] ([i915#118]) -> [PASS][107]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-glk3/igt@[email protected]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-glk5/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][108] ([fdo#108145] / [i915#265]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-skl1/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl4/igt@[email protected]
* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [SKIP][110] ([fdo#109441]) -> [PASS][111] +2 similar issues
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb7/igt@kms_psr@psr2_sprite_mmap_gtt.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][112] ([i915#31]) -> [PASS][113]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-apl2/igt@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-apl8/igt@[email protected]
* igt@kms_vblank@pipe-d-ts-continuation-suspend:
- shard-tglb: [INCOMPLETE][114] ([i915#3896]) -> [PASS][115]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-tglb7/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-tglb8/igt@[email protected]
* igt@prime_mmap_coherency@ioctl-errors:
- shard-skl: [DMESG-WARN][116] ([i915#1982]) -> [PASS][117]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-skl9/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-skl8/igt@[email protected]
* igt@sysfs_timeslice_duration@timeout@vecs0:
- shard-iclb: [FAIL][118] ([i915#1755]) -> [PASS][119]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb8/igt@sysfs_timeslice_duration@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb1/igt@sysfs_timeslice_duration@[email protected]
- shard-apl: [FAIL][120] ([i915#1755]) -> [PASS][121]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-apl7/igt@sysfs_timeslice_duration@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-apl3/igt@sysfs_timeslice_duration@[email protected]
#### Warnings ####
* igt@i915_pm_dc@dc9-dpms:
- shard-iclb: [SKIP][122] ([i915#4281]) -> [FAIL][123] ([i915#4275])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb3/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb6/igt@[email protected]
* igt@kms_psr2_sf@plane-move-sf-dmg-area-0:
- shard-iclb: [SKIP][124] ([i915#2920]) -> [SKIP][125] ([i915#658])
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb2/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb8/igt@[email protected]
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-iclb: [SKIP][126] ([i915#658]) -> [SKIP][127] ([i915#2920]) +2 similar issues
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10827/shard-iclb7/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/shard-iclb2/igt@[email protected]
* igt@runner@aborted:
- shard-kbl: ([FAIL][128], [FAIL][129], [FAIL][130], [FAIL][131], [FAIL][132], [FAIL][133], [FAIL][134], [FAIL][135], [FAIL][136], [FAIL][137], [FAIL][138], [FAIL][139], [FAIL][140]) ([i915#1436] / [i915#180] / [i915#1814] / [i915#3002] / [i915#3363] / [i915#4312] / [i915#602]) -> ([FAIL][141], [FAIL][142], [FAIL][143], [FAIL][144], [FAIL][145], [FAIL][146], [FAIL][147], [FAIL][148], [FAIL][149], [FAIL][150], [FAIL][151], [FAIL][152]) ([i915#1436] / [i915#180] /
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/index.html
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Prepare error capture for asynchronous migration
Quoted 35 lines · Patchwork
Project List - Patchwork *Patch Details*
*Series:* drm/i915: Prepare error capture for asynchronous migration
*URL:* https://patchwork.freedesktop.org/series/96493/
*State:* failure
*Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/index.htmlCI Bug Log - changes from
CI_DRM_10827_full->Patchwork_21503_fullSummary
*FAILURE*
Serious unknown changes coming with
Patchwork_21503_fullabsolutely need to be verified manually.If you think the reported changes have nothing to do with the changes introduced in
Patchwork_21503_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.Participating hosts (10 -> 10)No changes in participating hosts
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_21503_full:Piglit changes
Quoted 7 lines
Possible regressions
* spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-2darray (NEW):
o pig-kbl-iris: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/pig-kbl-iris/spec@arb_gpu_shader5@[email protected]>
+5 similar issues
Lakshmi, This failure is unrelated.
Thanks,
Thomas
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Prepare error capture for asynchronous migration
We don’t have the test in our db “spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-2darray”. So, I cannot really address this issue.
FYI @Latvala, Petri<mailto:[email protected]>
From: Thomas Hellström <[email protected]>
Sent: Tuesday, November 2, 2021 9:29 AM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Prepare error capture for asynchronous migration
On 11/2/21 17:02, Patchwork wrote:
Patch Details
Series:
drm/i915: Prepare error capture for asynchronous migration
URL:
https://patchwork.freedesktop.org/series/96493/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/index.html
CI Bug Log - changes from CI_DRM_10827_full -> Patchwork_21503_full Summary
FAILURE
Serious unknown changes coming with Patchwork_21503_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_21503_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (10 -> 10)
No changes in participating hosts
Possible new issues
Here are the unknown changes that may have been introduced in Patchwork_21503_full:
Piglit changes
Possible regressions
* spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-2darray (NEW):
* pig-kbl-iris: NOTRUN -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/pig-kbl-iris/spec@arb_gpu_shader5@[email protected]> +5 similar issues
Lakshmi, This failure is unrelated.
Thanks,
Thomas