Skip to contentSkip to conversation

drm/i915/gem: Break out some shmem backend utils

PATCH Superseded Matthew Auld 6 participants 25 messages Oct 6, 2021 – Oct 8, 2021

Subsystems (2)

v7 of 9 Superseded Latest is v9 →

lore
Share & tools
lore
#0 lore raw

PATCH v7 1/8 drm/i915/gem: Break out some shmem backend utils

From: Thomas Hellström <[email protected]>

Break out some shmem backend utils for future reuse by the TTM backend:
shmem_alloc_st(), shmem_free_st() and __shmem_writeback() which we can use to provide a shmem-backed TTM page pool for cached-only TTM buffer objects.

Main functional change here is that we now compute the page sizes using the dma segments rather than using the physical page address segments.

v2(Reported-by: kernel test robot <[email protected]>)
- Make sure we initialise the mapping on the error path in shmem_get_pages()

---
 drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 181 +++++++++++++---------
 1 file changed, 106 insertions(+), 75 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_shmem.c +106 -75
index 11f072193f3b..36b711ae9e28 100644
@@ -25,46 +25,61 @@ static void check_release_pagevec(struct pagevec *pvec)
 	cond_resched();
 }
 
-static int shmem_get_pages(struct drm_i915_gem_object *obj)
+static void shmem_free_st(struct sg_table *st, struct address_space *mapping,
+			  bool dirty, bool backup)
 {
-	struct drm_i915_private *i915 = to_i915(obj->base.dev);
-	struct intel_memory_region *mem = obj->mm.region;
-	const unsigned long page_count = obj->base.size / PAGE_SIZE;
+	struct sgt_iter sgt_iter;
+	struct pagevec pvec;
+	struct page *page;
+
+	mapping_clear_unevictable(mapping);
+
+	pagevec_init(&pvec);
+	for_each_sgt_page(page, sgt_iter, st) {
+		if (dirty)
+			set_page_dirty(page);
+
+		if (backup)
+			mark_page_accessed(page);
+
+		if (!pagevec_add(&pvec, page))
+			check_release_pagevec(&pvec);
+	}
+	if (pagevec_count(&pvec))
+		check_release_pagevec(&pvec);
+
+	sg_free_table(st);
+	kfree(st);
+}
+
+static struct sg_table *shmem_alloc_st(struct drm_i915_private *i915,
+				       size_t size, struct intel_memory_region *mr,
+				       struct address_space *mapping,
+				       unsigned int max_segment)
+{
+	const unsigned long page_count = size / PAGE_SIZE;
 	unsigned long i;
-	struct address_space *mapping;
 	struct sg_table *st;
 	struct scatterlist *sg;
-	struct sgt_iter sgt_iter;
 	struct page *page;
 	unsigned long last_pfn = 0;	/* suppress gcc warning */
-	unsigned int max_segment = i915_sg_segment_size();
-	unsigned int sg_page_sizes;
 	gfp_t noreclaim;
 	int ret;
 
-	/*
-	 * Assert that the object is not currently in any GPU domain. As it
-	 * wasn't in the GTT, there shouldn't be any way it could have been in
-	 * a GPU cache
-	 */
-	GEM_BUG_ON(obj->read_domains & I915_GEM_GPU_DOMAINS);
-	GEM_BUG_ON(obj->write_domain & I915_GEM_GPU_DOMAINS);
-
 	/*
 	 * If there's no chance of allocating enough pages for the whole
 	 * object, bail early.
 	 */
-	if (obj->base.size > resource_size(&mem->region))
-		return -ENOMEM;
+	if (size > resource_size(&mr->region))
+		return ERR_PTR(-ENOMEM);
 
 	st = kmalloc(sizeof(*st), GFP_KERNEL);
 	if (!st)
-		return -ENOMEM;
+		return ERR_PTR(-ENOMEM);
 
-rebuild_st:
 	if (sg_alloc_table(st, page_count, GFP_KERNEL)) {
 		kfree(st);
-		return -ENOMEM;
+		return ERR_PTR(-ENOMEM);
 	}
 
 	/*
@@ -73,14 +88,12 @@ static int shmem_get_pages(struct drm_i915_gem_object *obj)
 	 *
 	 * Fail silently without starting the shrinker
 	 */
-	mapping = obj->base.filp->f_mapping;
 	mapping_set_unevictable(mapping);
 	noreclaim = mapping_gfp_constraint(mapping, ~__GFP_RECLAIM);
 	noreclaim |= __GFP_NORETRY | __GFP_NOWARN;
 
 	sg = st->sgl;
 	st->nents = 0;
-	sg_page_sizes = 0;
 	for (i = 0; i < page_count; i++) {
 		const unsigned int shrink[] = {
 			I915_SHRINK_BOUND | I915_SHRINK_UNBOUND,
@@ -135,10 +148,9 @@ static int shmem_get_pages(struct drm_i915_gem_object *obj)
 		if (!i ||
 		    sg->length >= max_segment ||
 		    page_to_pfn(page) != last_pfn + 1) {
-			if (i) {
-				sg_page_sizes |= sg->length;
+			if (i)
 				sg = sg_next(sg);
-			}
+
 			st->nents++;
 			sg_set_page(sg, page, PAGE_SIZE, 0);
 		} else {
@@ -149,14 +161,65 @@ static int shmem_get_pages(struct drm_i915_gem_object *obj)
 		/* Check that the i965g/gm workaround works. */
 		GEM_BUG_ON(gfp & __GFP_DMA32 && last_pfn >= 0x00100000UL);
 	}
-	if (sg) { /* loop terminated early; short sg table */
-		sg_page_sizes |= sg->length;
+	if (sg) /* loop terminated early; short sg table */
 		sg_mark_end(sg);
-	}
 
 	/* Trim unused sg entries to avoid wasting memory. */
 	i915_sg_trim(st);
 
+	return st;
+err_sg:
+	sg_mark_end(sg);
+	if (sg != st->sgl) {
+		shmem_free_st(st, mapping, false, false);
+	} else {
+		mapping_clear_unevictable(mapping);
+		sg_free_table(st);
+		kfree(st);
+	}
+
+	/*
+	 * shmemfs first checks if there is enough memory to allocate the page
+	 * and reports ENOSPC should there be insufficient, along with the usual
+	 * ENOMEM for a genuine allocation failure.
+	 *
+	 * We use ENOSPC in our driver to mean that we have run out of aperture
+	 * space and so want to translate the error from shmemfs back to our
+	 * usual understanding of ENOMEM.
+	 */
+	if (ret == -ENOSPC)
+		ret = -ENOMEM;
+
+	return ERR_PTR(ret);
+}
+
+static int shmem_get_pages(struct drm_i915_gem_object *obj)
+{
+	struct drm_i915_private *i915 = to_i915(obj->base.dev);
+	struct intel_memory_region *mem = obj->mm.region;
+	struct address_space *mapping = obj->base.filp->f_mapping;
+	const unsigned long page_count = obj->base.size / PAGE_SIZE;
+	unsigned int max_segment = i915_sg_segment_size();
+	struct sg_table *st;
+	struct sgt_iter sgt_iter;
+	struct page *page;
+	int ret;
+
+	/*
+	 * Assert that the object is not currently in any GPU domain. As it
+	 * wasn't in the GTT, there shouldn't be any way it could have been in
+	 * a GPU cache
+	 */
+	GEM_BUG_ON(obj->read_domains & I915_GEM_GPU_DOMAINS);
+	GEM_BUG_ON(obj->write_domain & I915_GEM_GPU_DOMAINS);
+
+rebuild_st:
+	st = shmem_alloc_st(i915, obj->base.size, mem, mapping, max_segment);
+	if (IS_ERR(st)) {
+		ret = PTR_ERR(st);
+		goto err_st;
+	}
+
 	ret = i915_gem_gtt_prepare_pages(obj, st);
 	if (ret) {
 		/*
@@ -168,6 +231,7 @@ static int shmem_get_pages(struct drm_i915_gem_object *obj)
 			for_each_sgt_page(page, sgt_iter, st)
 				put_page(page);
 			sg_free_table(st);
+			kfree(st);
 
 			max_segment = PAGE_SIZE;
 			goto rebuild_st;
@@ -200,28 +264,12 @@ static int shmem_get_pages(struct drm_i915_gem_object *obj)
 	if (IS_JSL_EHL(i915) && obj->flags & I915_BO_ALLOC_USER)
 		obj->cache_dirty = true;
 
-	__i915_gem_object_set_pages(obj, st, sg_page_sizes);
+	__i915_gem_object_set_pages(obj, st, i915_sg_dma_sizes(st->sgl));
 
 	return 0;
 
-err_sg:
-	sg_mark_end(sg);
 err_pages:
-	mapping_clear_unevictable(mapping);
-	if (sg != st->sgl) {
-		struct pagevec pvec;
-
-		pagevec_init(&pvec);
-		for_each_sgt_page(page, sgt_iter, st) {
-			if (!pagevec_add(&pvec, page))
-				check_release_pagevec(&pvec);
-		}
-		if (pagevec_count(&pvec))
-			check_release_pagevec(&pvec);
-	}
-	sg_free_table(st);
-	kfree(st);
-
+	shmem_free_st(st, mapping, false, false);
 	/*
 	 * shmemfs first checks if there is enough memory to allocate the page
 	 * and reports ENOSPC should there be insufficient, along with the usual
@@ -231,6 +279,7 @@ static int shmem_get_pages(struct drm_i915_gem_object *obj)
 	 * space and so want to translate the error from shmemfs back to our
 	 * usual understanding of ENOMEM.
 	 */
+err_st:
 	if (ret == -ENOSPC)
 		ret = -ENOMEM;
 
@@ -251,10 +300,8 @@ shmem_truncate(struct drm_i915_gem_object *obj)
 	obj->mm.pages = ERR_PTR(-EFAULT);
 }
 
-static void
-shmem_writeback(struct drm_i915_gem_object *obj)
+static void __shmem_writeback(size_t size, struct address_space *mapping)
 {
-	struct address_space *mapping;
 	struct writeback_control wbc = {
 		.sync_mode = WB_SYNC_NONE,
 		.nr_to_write = SWAP_CLUSTER_MAX,
@@ -270,10 +317,9 @@ shmem_writeback(struct drm_i915_gem_object *obj)
 	 * instead of invoking writeback so they are aged and paged out
 	 * as normal.
 	 */
-	mapping = obj->base.filp->f_mapping;
 
 	/* Begin writeback on each dirty page */
-	for (i = 0; i < obj->base.size >> PAGE_SHIFT; i++) {
+	for (i = 0; i < size >> PAGE_SHIFT; i++) {
 		struct page *page;
 
 		page = find_lock_page(mapping, i);
@@ -296,6 +342,12 @@ shmem_writeback(struct drm_i915_gem_object *obj)
 	}
 }
 
+static void
+shmem_writeback(struct drm_i915_gem_object *obj)
+{
+	__shmem_writeback(obj->base.size, obj->base.filp->f_mapping);
+}
+
 void
 __i915_gem_object_release_shmem(struct drm_i915_gem_object *obj,
 				struct sg_table *pages,
@@ -316,11 +368,6 @@ __i915_gem_object_release_shmem(struct drm_i915_gem_object *obj,
 
 void i915_gem_object_put_pages_shmem(struct drm_i915_gem_object *obj, struct sg_table *pages)
 {
-	struct sgt_iter sgt_iter;
-	struct pagevec pvec;
-	struct page *page;
-
-	GEM_WARN_ON(IS_DGFX(to_i915(obj->base.dev)));
 	__i915_gem_object_release_shmem(obj, pages, true);
 
 	i915_gem_gtt_finish_pages(obj, pages);
@@ -328,25 +375,9 @@ void i915_gem_object_put_pages_shmem(struct drm_i915_gem_object *obj, struct sg_
 	if (i915_gem_object_needs_bit17_swizzle(obj))
 		i915_gem_object_save_bit_17_swizzle(obj, pages);
 
-	mapping_clear_unevictable(file_inode(obj->base.filp)->i_mapping);
-
-	pagevec_init(&pvec);
-	for_each_sgt_page(page, sgt_iter, pages) {
-		if (obj->mm.dirty)
-			set_page_dirty(page);
-
-		if (obj->mm.madv == I915_MADV_WILLNEED)
-			mark_page_accessed(page);
-
-		if (!pagevec_add(&pvec, page))
-			check_release_pagevec(&pvec);
-	}
-	if (pagevec_count(&pvec))
-		check_release_pagevec(&pvec);
+	shmem_free_st(pages, file_inode(obj->base.filp)->i_mapping,
+		      obj->mm.dirty, obj->mm.madv == I915_MADV_WILLNEED);
 	obj->mm.dirty = false;
-
-	sg_free_table(pages);
-	kfree(pages);
 }
 
 static void
Signature · 1 line
2.26.3
#1 lore raw

PATCH v7 2/8 drm/i915/ttm: add tt shmem backend

For cached objects we can allocate our pages directly in shmem. This should make it possible(in a later patch) to utilise the existing i915-gem shrinker code for such objects. For now this is still disabled.

v2(Thomas):
- Add optional try_to_writeback hook for objects. Importantly we need to check if the object is even still shrinkable; in between us dropping the shrinker LRU lock and acquiring the object lock it could for example have been moved. Also we need to differentiate between "lazy" shrinking and the immediate writeback mode. Also later we need to handle objects which don't even have mm.pages, so bundling this into put_pages() would require somehow handling that edge case, hence just letting the ttm backend handle everything in try_to_writeback doesn't seem too bad.
v3(Thomas):
- Likely a bad idea to touch the object from the unpopulate hook, since it's not possible to hold a reference, without also creating circular dependency, so likely this is too fragile. For now just ensure we at least mark the pages as dirty/accessed when called from the shrinker on WILLNEED objects.
- s/try_to_writeback/shrinker_release_pages, since this can do more than just writeback.
- Get rid of do_backup boolean and just set the SWAPPED flag prior to calling unpopulate.
- Keep shmem_tt as lowest priority for the TTM LRU bo_swapout walk, since these just get skipped anyway. We can try to come up with something better later.
v4(Thomas):
- s/PCI_DMA/DMA/. Also drop NO_KERNEL_MAPPING and NO_WARN, which apparently doesn't do anything with streaming mappings.
- Just pass along the error for ->truncate, and assume nothing.

---
 drivers/gpu/drm/i915/gem/i915_gem_object.h    |  11 +-
 .../gpu/drm/i915/gem/i915_gem_object_types.h  |   4 +-
 drivers/gpu/drm/i915/gem/i915_gem_pages.c     |   6 +-
 drivers/gpu/drm/i915/gem/i915_gem_shmem.c     |  18 +-
 drivers/gpu/drm/i915/gem/i915_gem_shrinker.c  |  17 +-
 drivers/gpu/drm/i915/gem/i915_gem_ttm.c       | 233 ++++++++++++++++--
 6 files changed, 247 insertions(+), 42 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_object.h +9 -2
index 9df3ee60604e..e641db297e0e 100644
@@ -93,7 +93,6 @@ void i915_gem_flush_free_objects(struct drm_i915_private *i915);
 
 struct sg_table *
 __i915_gem_object_unset_pages(struct drm_i915_gem_object *obj);
-void i915_gem_object_truncate(struct drm_i915_gem_object *obj);
 
 /**
  * i915_gem_object_lookup_rcu - look up a temporary GEM object from its handle
@@ -449,7 +448,7 @@ i915_gem_object_unpin_pages(struct drm_i915_gem_object *obj)
 }
 
 int __i915_gem_object_put_pages(struct drm_i915_gem_object *obj);
-void i915_gem_object_truncate(struct drm_i915_gem_object *obj);
+int i915_gem_object_truncate(struct drm_i915_gem_object *obj);
 void i915_gem_object_writeback(struct drm_i915_gem_object *obj);
 
 /**
@@ -612,6 +611,14 @@ int i915_gem_object_wait_migration(struct drm_i915_gem_object *obj,
 bool i915_gem_object_placement_possible(struct drm_i915_gem_object *obj,
 					enum intel_memory_type type);
 
+struct sg_table *shmem_alloc_st(struct drm_i915_private *i915,
+				size_t size, struct intel_memory_region *mr,
+				struct address_space *mapping,
+				unsigned int max_segment);
+void shmem_free_st(struct sg_table *st, struct address_space *mapping,
+		   bool dirty, bool backup);
+void __shmem_writeback(size_t size, struct address_space *mapping);
+
 #ifdef CONFIG_MMU_NOTIFIER
 static inline bool
 i915_gem_object_is_userptr(struct drm_i915_gem_object *obj)
drivers/gpu/drm/i915/gem/i915_gem_object_types.h +3 -1
index 7c3da4e3e737..7dd5f804aab3 100644
@@ -54,8 +54,10 @@ struct drm_i915_gem_object_ops {
 	int (*get_pages)(struct drm_i915_gem_object *obj);
 	void (*put_pages)(struct drm_i915_gem_object *obj,
 			  struct sg_table *pages);
-	void (*truncate)(struct drm_i915_gem_object *obj);
+	int (*truncate)(struct drm_i915_gem_object *obj);
 	void (*writeback)(struct drm_i915_gem_object *obj);
+	int (*shrinker_release_pages)(struct drm_i915_gem_object *obj,
+				      bool should_writeback);
 
 	int (*pread)(struct drm_i915_gem_object *obj,
 		     const struct drm_i915_gem_pread *arg);
drivers/gpu/drm/i915/gem/i915_gem_pages.c +4 -2
index 8eb1c3a6fc9c..ea6d9b3d2d6b 100644
@@ -158,11 +158,13 @@ int i915_gem_object_pin_pages_unlocked(struct drm_i915_gem_object *obj)
 }
 
 /* Immediately discard the backing storage */
-void i915_gem_object_truncate(struct drm_i915_gem_object *obj)
+int i915_gem_object_truncate(struct drm_i915_gem_object *obj)
 {
 	drm_gem_free_mmap_offset(&obj->base);
 	if (obj->ops->truncate)
-		obj->ops->truncate(obj);
+		return obj->ops->truncate(obj);
+
+	return 0;
 }
 
 /* Try to discard unwanted pages */
drivers/gpu/drm/i915/gem/i915_gem_shmem.c +10 -8
index 36b711ae9e28..8375dc23f233 100644
@@ -25,8 +25,8 @@ static void check_release_pagevec(struct pagevec *pvec)
 	cond_resched();
 }
 
-static void shmem_free_st(struct sg_table *st, struct address_space *mapping,
-			  bool dirty, bool backup)
+void shmem_free_st(struct sg_table *st, struct address_space *mapping,
+		   bool dirty, bool backup)
 {
 	struct sgt_iter sgt_iter;
 	struct pagevec pvec;
@@ -52,10 +52,10 @@ static void shmem_free_st(struct sg_table *st, struct address_space *mapping,
 	kfree(st);
 }
 
-static struct sg_table *shmem_alloc_st(struct drm_i915_private *i915,
-				       size_t size, struct intel_memory_region *mr,
-				       struct address_space *mapping,
-				       unsigned int max_segment)
+struct sg_table *shmem_alloc_st(struct drm_i915_private *i915,
+				size_t size, struct intel_memory_region *mr,
+				struct address_space *mapping,
+				unsigned int max_segment)
 {
 	const unsigned long page_count = size / PAGE_SIZE;
 	unsigned long i;
@@ -286,7 +286,7 @@ static int shmem_get_pages(struct drm_i915_gem_object *obj)
 	return ret;
 }
 
-static void
+static int
 shmem_truncate(struct drm_i915_gem_object *obj)
 {
 	/*
@@ -298,9 +298,11 @@ shmem_truncate(struct drm_i915_gem_object *obj)
 	shmem_truncate_range(file_inode(obj->base.filp), 0, (loff_t)-1);
 	obj->mm.madv = __I915_MADV_PURGED;
 	obj->mm.pages = ERR_PTR(-EFAULT);
+
+	return 0;
 }
 
-static void __shmem_writeback(size_t size, struct address_space *mapping)
+void __shmem_writeback(size_t size, struct address_space *mapping)
 {
 	struct writeback_control wbc = {
 		.sync_mode = WB_SYNC_NONE,
drivers/gpu/drm/i915/gem/i915_gem_shrinker.c +11 -6
index 5ab136ffdeb2..ae2a8d54b7a4 100644
@@ -56,19 +56,24 @@ static bool unsafe_drop_pages(struct drm_i915_gem_object *obj,
 	return false;
 }
 
-static void try_to_writeback(struct drm_i915_gem_object *obj,
-			     unsigned int flags)
+static int try_to_writeback(struct drm_i915_gem_object *obj, unsigned int flags)
 {
+	if (obj->ops->shrinker_release_pages)
+		return obj->ops->shrinker_release_pages(obj,
+							flags & I915_SHRINK_WRITEBACK);
+
 	switch (obj->mm.madv) {
 	case I915_MADV_DONTNEED:
 		i915_gem_object_truncate(obj);
-		return;
+		return 0;
 	case __I915_MADV_PURGED:
-		return;
+		return 0;
 	}
 
 	if (flags & I915_SHRINK_WRITEBACK)
 		i915_gem_object_writeback(obj);
+
+	return 0;
 }
 
 /**
@@ -222,8 +227,8 @@ i915_gem_shrink(struct i915_gem_ww_ctx *ww,
 				}
 
 				if (!__i915_gem_object_put_pages(obj)) {
-					try_to_writeback(obj, shrink);
-					count += obj->base.size >> PAGE_SHIFT;
+					if (!try_to_writeback(obj, shrink))
+						count += obj->base.size >> PAGE_SHIFT;
 				}
 				if (!ww)
 					i915_gem_object_unlock(obj);
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +210 -23

349 lines not on this page · raw message

Signature · 1 line
2.26.3
#2 lore raw

PATCH v7 3/8 drm/i915/gtt: drop unneeded make_unshrinkable

In reply to Matthew Auld

We already do this when mapping the pages.

---
 drivers/gpu/drm/i915/gt/gen6_ppgtt.c | 1 -
 drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 1 -
 2 files changed, 2 deletions(-)
drivers/gpu/drm/i915/gt/gen6_ppgtt.c +0 -1
index 890191f286e3..baea9770200a 100644
@@ -185,7 +185,6 @@ static void gen6_alloc_va_range(struct i915_address_space *vm,
 
 			pt = stash->pt[0];
 			__i915_gem_object_pin_pages(pt->base);
-			i915_gem_object_make_unshrinkable(pt->base);
 
 			fill32_px(pt, vm->scratch[0]->encode);
 
drivers/gpu/drm/i915/gt/gen8_ppgtt.c +0 -1
index 037a9a6e4889..8af2f709571c 100644
@@ -301,7 +301,6 @@ static void __gen8_ppgtt_alloc(struct i915_address_space * const vm,
 
 			pt = stash->pt[!!lvl];
 			__i915_gem_object_pin_pages(pt->base);
-			i915_gem_object_make_unshrinkable(pt->base);
 
 			fill_px(pt, vm->scratch[lvl]->encode);
 
Signature · 1 line
2.26.3
#3 lore raw

PATCH v7 4/8 drm/i915: drop unneeded make_unshrinkable in free_object

In reply to Matthew Auld

The comment here is no longer accurate, since the current shrinker code requires a full ref before touching any objects. Also unset_pages() should already do the required make_unshrinkable() for us, if needed, which is also nicely balanced with set_pages().

---
 drivers/gpu/drm/i915/gem/i915_gem_object.c | 9 ---------
 1 file changed, 9 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_object.c +0 -9
index 76ce6a1500bc..1dc3c1940c32 100644
@@ -337,15 +337,6 @@ static void i915_gem_free_object(struct drm_gem_object *gem_obj)
 	 */
 	atomic_inc(&i915->mm.free_count);
 
-	/*
-	 * This serializes freeing with the shrinker. Since the free
-	 * is delayed, first by RCU then by the workqueue, we want the
-	 * shrinker to be able to free pages of unreferenced objects,
-	 * or else we may oom whilst there are plenty of deferred
-	 * freed objects.
-	 */
-	i915_gem_object_make_unshrinkable(obj);
-
 	/*
 	 * Since we require blocking on struct_mutex to unbind the freed
 	 * object from the GPU before releasing resources back to the
Signature · 1 line
2.26.3
#4 lore raw

PATCH v7 5/8 drm/i915: add some kernel-doc for shrink_pin and friends

In reply to Matthew Auld

Attempt to document shrink_pin and the other relevant interfaces that interact with it, before we start messing with it.

---
 .../gpu/drm/i915/gem/i915_gem_object_types.h  | 24 +++++++++++++-
 drivers/gpu/drm/i915/gem/i915_gem_shrinker.c  | 31 +++++++++++++++++++
 2 files changed, 54 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/gem/i915_gem_object_types.h +23 -1
index 7dd5f804aab3..f4233c4e8d2e 100644
@@ -461,6 +461,28 @@ struct drm_i915_gem_object {
 		 * instead go through the pin/unpin interfaces.
 		 */
 		atomic_t pages_pin_count;
+
+		/**
+		 * @shrink_pin: Prevents the pages from being made visible to
+		 * the shrinker, while the shrink_pin is non-zero. Most users
+		 * should pretty much never have to care about this, outside of
+		 * some special use cases.
+		 *
+		 * By default most objects will start out as visible to the
+		 * shrinker(if I915_GEM_OBJECT_IS_SHRINKABLE) as soon as the
+		 * backing pages are attached to the object, like in
+		 * __i915_gem_object_set_pages(). They will then be removed the
+		 * shrinker list once the pages are released.
+		 *
+		 * The @shrink_pin is incremented by calling
+		 * i915_gem_object_make_unshrinkable(), which will also remove
+		 * the object from the shrinker list, if the pin count was zero.
+		 *
+		 * Callers will then typically call
+		 * i915_gem_object_make_shrinkable() or
+		 * i915_gem_object_make_purgeable() to decrement the pin count,
+		 * and make the pages visible again.
+		 */
 		atomic_t shrink_pin;
 
 		/**
@@ -522,7 +544,7 @@ struct drm_i915_gem_object {
 		struct i915_gem_object_page_iter get_dma_page;
 
 		/**
-		 * Element within i915->mm.unbound_list or i915->mm.bound_list,
+		 * Element within i915->mm.shrink_list or i915->mm.purge_list,
 		 * locked by i915->mm.obj_lock.
 		 */
 		struct list_head link;
drivers/gpu/drm/i915/gem/i915_gem_shrinker.c +31 -0
index ae2a8d54b7a4..66121fedc655 100644
@@ -463,6 +463,16 @@ void i915_gem_shrinker_taints_mutex(struct drm_i915_private *i915,
 
 #define obj_to_i915(obj__) to_i915((obj__)->base.dev)
 
+/**
+ * i915_gem_object_make_unshrinkable - Hide the object from the shrinker. By
+ * default all object types that support shrinking(see IS_SHRINKABLE), will also
+ * make the object visible to the shrinker after allocating the system memory
+ * pages.
+ * @obj: The GEM object.
+ *
+ * This is typically used for special kernel internal objects that can't be
+ * easily processed by the shrinker, like if they are perma-pinned.
+ */
 void i915_gem_object_make_unshrinkable(struct drm_i915_gem_object *obj)
 {
 	struct drm_i915_private *i915 = obj_to_i915(obj);
@@ -513,12 +523,33 @@ static void __i915_gem_object_make_shrinkable(struct drm_i915_gem_object *obj,
 	spin_unlock_irqrestore(&i915->mm.obj_lock, flags);
 }
 
+/**
+ * i915_gem_object_make_shrinkable - Move the object to the tail of the
+ * shrinkable list. Objects on this list might be swapped out. Used with
+ * WILLNEED objects.
+ * @obj: The GEM object.
+ *
+ * MUST only be called on objects which have backing pages.
+ *
+ * MUST be balanced with previous call to i915_gem_object_make_unshrinkable().
+ */
 void i915_gem_object_make_shrinkable(struct drm_i915_gem_object *obj)
 {
 	__i915_gem_object_make_shrinkable(obj,
 					  &obj_to_i915(obj)->mm.shrink_list);
 }
 
+/**
+ * i915_gem_object_make_purgeable - Move the object to the tail of the purgeable
+ * list. Used with DONTNEED objects. Unlike with shrinkable objects, the
+ * shrinker will attempt to discard the backing pages, instead of trying to swap
+ * them out.
+ * @obj: The GEM object.
+ *
+ * MUST only be called on objects which have backing pages.
+ *
+ * MUST be balanced with previous call to i915_gem_object_make_unshrinkable().
+ */
 void i915_gem_object_make_purgeable(struct drm_i915_gem_object *obj)
 {
 	__i915_gem_object_make_shrinkable(obj,
Signature · 1 line
2.26.3
#5 lore raw

PATCH v7 6/8 drm/i915/ttm: move shrinker management into adjust_lru

In reply to Matthew Auld

We currently just evict lmem objects to system memory when under memory pressure. For this case we might lack the usual object mm.pages, which effectively hides the pages from the i915-gem shrinker, until we actually "attach" the TT to the object, or in the case of lmem-only objects it just gets migrated back to lmem when touched again.

For all cases we can just adjust the i915 shrinker LRU each time we also adjust the TTM LRU. The two cases we care about are:

1) When something is moved by TTM, including when initially populating an object. Importantly this covers the case where TTM moves something from lmem <-> smem, outside of the normal get_pages() interface, which should still ensure the shmem pages underneath are reclaimable.

2) When calling into i915_gem_object_unlock(). The unlock should ensure the object is removed from the shinker LRU, if it was indeed swapped out, or just purged, when the shrinker drops the object lock.

v2(Thomas):
- Handle managing the shrinker LRU in adjust_lru, where it is always safe to touch the object.
v3(Thomas):
- Pretty much a re-write. This time piggy back off the shrink_pin stuff, which actually seems to fit quite well for what we want here.
v4(Thomas):
- Just use a simple boolean for tracking ttm_shrinkable.

---
 drivers/gpu/drm/i915/gem/i915_gem_object.h    |  8 +++
 .../gpu/drm/i915/gem/i915_gem_object_types.h  | 14 ++++-
 drivers/gpu/drm/i915/gem/i915_gem_pages.c     |  5 +-
 drivers/gpu/drm/i915/gem/i915_gem_shrinker.c  | 45 +++++++++++---
 drivers/gpu/drm/i915/gem/i915_gem_ttm.c       | 60 +++++++++++++++++--
 5 files changed, 114 insertions(+), 18 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_object.h +8 -0
index e641db297e0e..3eac8cf2ae10 100644
@@ -294,6 +294,12 @@ i915_gem_object_is_shrinkable(const struct drm_i915_gem_object *obj)
 	return i915_gem_object_type_has(obj, I915_GEM_OBJECT_IS_SHRINKABLE);
 }
 
+static inline bool
+i915_gem_object_has_self_managed_shrink_list(const struct drm_i915_gem_object *obj)
+{
+	return i915_gem_object_type_has(obj, I915_GEM_OBJECT_SELF_MANAGED_SHRINK_LIST);
+}
+
 static inline bool
 i915_gem_object_is_proxy(const struct drm_i915_gem_object *obj)
 {
@@ -531,6 +537,8 @@ i915_gem_object_pin_to_display_plane(struct drm_i915_gem_object *obj,
 
 void i915_gem_object_make_unshrinkable(struct drm_i915_gem_object *obj);
 void i915_gem_object_make_shrinkable(struct drm_i915_gem_object *obj);
+void __i915_gem_object_make_shrinkable(struct drm_i915_gem_object *obj);
+void __i915_gem_object_make_purgeable(struct drm_i915_gem_object *obj);
 void i915_gem_object_make_purgeable(struct drm_i915_gem_object *obj);
 
 static inline bool cpu_write_needs_clflush(struct drm_i915_gem_object *obj)
drivers/gpu/drm/i915/gem/i915_gem_object_types.h +11 -3
index f4233c4e8d2e..5718a09f5533 100644
@@ -34,9 +34,11 @@ struct i915_lut_handle {
 
 struct drm_i915_gem_object_ops {
 	unsigned int flags;
-#define I915_GEM_OBJECT_IS_SHRINKABLE	BIT(1)
-#define I915_GEM_OBJECT_IS_PROXY	BIT(2)
-#define I915_GEM_OBJECT_NO_MMAP		BIT(3)
+#define I915_GEM_OBJECT_IS_SHRINKABLE			BIT(1)
+/* Skip the shrinker management in set_pages/unset_pages */
+#define I915_GEM_OBJECT_SELF_MANAGED_SHRINK_LIST	BIT(2)
+#define I915_GEM_OBJECT_IS_PROXY			BIT(3)
+#define I915_GEM_OBJECT_NO_MMAP				BIT(4)
 
 	/* Interface between the GEM object and its backing storage.
 	 * get_pages() is called once prior to the use of the associated set
@@ -485,6 +487,12 @@ struct drm_i915_gem_object {
 		 */
 		atomic_t shrink_pin;
 
+		/**
+		 * @ttm_shrinkable: True when the object is using shmem pages
+		 * underneath. Protected by the object lock.
+		 */
+		bool ttm_shrinkable;
+
 		/**
 		 * Priority list of potential placements for this object.
 		 */
drivers/gpu/drm/i915/gem/i915_gem_pages.c +3 -2
index ea6d9b3d2d6b..308e22a80af4 100644
@@ -68,7 +68,7 @@ void __i915_gem_object_set_pages(struct drm_i915_gem_object *obj,
 		shrinkable = false;
 	}
 
-	if (shrinkable) {
+	if (shrinkable && !i915_gem_object_has_self_managed_shrink_list(obj)) {
 		struct list_head *list;
 		unsigned long flags;
 
@@ -210,7 +210,8 @@ __i915_gem_object_unset_pages(struct drm_i915_gem_object *obj)
 	if (i915_gem_object_is_volatile(obj))
 		obj->mm.madv = I915_MADV_WILLNEED;
 
-	i915_gem_object_make_unshrinkable(obj);
+	if (!i915_gem_object_has_self_managed_shrink_list(obj))
+		i915_gem_object_make_unshrinkable(obj);
 
 	if (obj->mm.mapping) {
 		unmap_object(obj, page_mask_bits(obj->mm.mapping));
drivers/gpu/drm/i915/gem/i915_gem_shrinker.c +38 -7

71 lines not on this page · raw message

drivers/gpu/drm/i915/gem/i915_gem_ttm.c +54 -6

114 lines not on this page · raw message

Signature · 1 line
2.26.3
#6 lore raw

PATCH v7 7/8 drm/i915/ttm: use cached system pages when evicting lmem

In reply to Matthew Auld

This should let us do an accelerated copy directly to the shmem pages when temporarily moving lmem-only objects, where the i915-gem shrinker can later kick in to swap out the pages, if needed.

---
 drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +4 -4
index 5521c5457a4f..0006ab35cd4d 100644
@@ -134,11 +134,11 @@ static enum ttm_caching
 i915_ttm_select_tt_caching(const struct drm_i915_gem_object *obj)
 {
 	/*
-	 * Objects only allowed in system get cached cpu-mappings.
-	 * Other objects get WC mapping for now. Even if in system.
+	 * Objects only allowed in system get cached cpu-mappings, or when
+	 * evicting lmem-only buffers to system for swapping. Other objects get
+	 * WC mapping for now. Even if in system.
 	 */
-	if (obj->mm.region->type == INTEL_MEMORY_SYSTEM &&
-	    obj->mm.n_placements <= 1)
+	if (obj->mm.n_placements <= 1)
 		return ttm_cached;
 
 	return ttm_write_combined;
Signature · 1 line
2.26.3
#7 lore raw

PATCH v7 8/8 drm/i915/ttm: enable shmem tt backend

In reply to Matthew Auld

Turn on the shmem tt backend, and enable shrinking.

---
 drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +2 -1
index 0006ab35cd4d..c889beb7696e 100644
@@ -1094,7 +1094,8 @@ static u64 i915_ttm_mmap_offset(struct drm_i915_gem_object *obj)
 
 static const struct drm_i915_gem_object_ops i915_gem_ttm_obj_ops = {
 	.name = "i915_gem_object_ttm",
-	.flags = I915_GEM_OBJECT_SELF_MANAGED_SHRINK_LIST,
+	.flags = I915_GEM_OBJECT_IS_SHRINKABLE |
+		 I915_GEM_OBJECT_SELF_MANAGED_SHRINK_LIST,
 
 	.get_pages = i915_ttm_get_pages,
 	.put_pages = i915_ttm_put_pages,
Signature · 1 line
2.26.3
#8 lore raw

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Matthew Auld
== Series Details ==

== Series Details ==

Series: series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
URL : https://patchwork.freedesktop.org/series/95501/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
c4bb02dc6bd4 drm/i915/gem: Break out some shmem backend utils
1d7586376c20 drm/i915/ttm: add tt shmem backend
-:16: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#16: 
    dropping the shrinker LRU lock and acquiring the object lock it could for

total: 0 errors, 1 warnings, 0 checks, 486 lines checked
b12519d84ec2 drm/i915/gtt: drop unneeded make_unshrinkable
74573c5598ba drm/i915: drop unneeded make_unshrinkable in free_object
b3479dc20fbe drm/i915: add some kernel-doc for shrink_pin and friends
564952863348 drm/i915/ttm: move shrinker management into adjust_lru
-:19: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #19:
an object. Importantly this covers the case where TTM moves something from

total: 0 errors, 1 warnings, 0 checks, 248 lines checked e2a24624b079 drm/i915/ttm: use cached system pages when evicting lmem 0d374b80323e drm/i915/ttm: enable shmem tt backend

#9 lore raw

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Matthew Auld
== Series Details ==

== Series Details ==

Series: series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
URL : https://patchwork.freedesktop.org/series/95501/
State : warning

== Summary ==

$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:27:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:27:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:27:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:32:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:32:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:49:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:49:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:49:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:56:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_engine_stats.h:56:9: warning: trying to copy expression type 31
+drivers/gpu/drm/i915/gt/intel_reset.c:1392:5: warning: context imbalance in 'intel_gt_reset_trylock' - different lock contexts for basic block
+drivers/gpu/drm/i915/i915_perf.c:1442:15: warning: memset with byte count of 16777216
+drivers/gpu/drm/i915/i915_perf.c:1496:15: warning: memset with byte count of 16777216
+./include/asm-generic/bitops/find.h:112:45: warning: shift count is negative (-262080)
+./include/asm-generic/bitops/find.h:32:31: warning: shift count is negative (-262080)
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'fwtable_read16' - different lock contexts for basic block
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'fwtable_read32' - different lock contexts for basic block
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'fwtable_read64' - different lock contexts for basic block
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'fwtable_read8' - different lock contexts for basic block
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'fwtable_write16' - different lock contexts for basic block
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'fwtable_write32' - different lock contexts for basic block
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'fwtable_write8' - different lock contexts for basic block
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'gen6_write16' - different lock contexts for basic block
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'gen6_write32' - different lock contexts for basic block
+./include/linux/spinlock.h:418:9: warning: context imbalance in 'gen6_write8' - different lock contexts for basic block
#10 lore raw

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Matthew Auld
== Series Details ==

== Series Details ==

Series: series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
URL : https://patchwork.freedesktop.org/series/95501/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_10688 -> Patchwork_21264
====================================================

Summary
-------

**SUCCESS**

No regressions found.

External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html

Known issues
------------

Here are the changes found in Patchwork_21264 that come from known issues:

### IGT changes ###

#### Issues hit ####

* igt@amdgpu/amd_basic@semaphore:
- fi-bdw-5557u: NOTRUN -> [SKIP][1] ([fdo#109271]) +27 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/fi-bdw-5557u/igt@amdgpu/[email protected]

* igt@core_hotunplug@unbind-rebind:
- fi-bdw-5557u: NOTRUN -> [WARN][2] ([i915#3718])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/fi-bdw-5557u/igt@[email protected]

* igt@kms_chamelium@dp-crc-fast:
- fi-kbl-7500u: [PASS][3] -> [FAIL][4] ([i915#1372])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/fi-kbl-7500u/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/fi-kbl-7500u/igt@[email protected]
- fi-bdw-5557u: NOTRUN -> [SKIP][5] ([fdo#109271] / [fdo#111827]) +8 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/fi-bdw-5557u/igt@[email protected]

* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [PASS][6] -> [DMESG-WARN][7] ([i915#95])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/fi-cml-u2/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/fi-cml-u2/igt@[email protected]

#### Possible fixes ####

* igt@i915_pm_rpm@module-reload:
- {fi-tgl-dsi}: [DMESG-WARN][8] ([i915#1982] / [i915#2411]) -> [PASS][9]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/fi-tgl-dsi/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/fi-tgl-dsi/igt@[email protected]

* igt@i915_selftest@live@hangcheck:
- {fi-hsw-gt1}: [DMESG-WARN][10] ([i915#3303]) -> [PASS][11]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/fi-hsw-gt1/igt@i915_selftest@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/fi-hsw-gt1/igt@i915_selftest@[email protected]

* igt@kms_flip@basic-plain-flip@c-dp1:
- fi-cfl-8109u: [FAIL][12] ([i915#4165]) -> [PASS][13]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/fi-cfl-8109u/igt@kms_flip@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/fi-cfl-8109u/igt@kms_flip@[email protected]

* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b:
- fi-cfl-8109u: [DMESG-WARN][14] ([i915#295]) -> [PASS][15] +14 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/fi-cfl-8109u/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/fi-cfl-8109u/igt@[email protected]

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1372]: https://gitlab.freedesktop.org/drm/intel/issues/1372
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#295]: https://gitlab.freedesktop.org/drm/intel/issues/295
[i915#3303]: https://gitlab.freedesktop.org/drm/intel/issues/3303
[i915#3718]: https://gitlab.freedesktop.org/drm/intel/issues/3718
[i915#4165]: https://gitlab.freedesktop.org/drm/intel/issues/4165
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95

Participating hosts (45 -> 36)
------------------------------

Missing (9): fi-ilk-m540 bat-dg1-6 fi-tgl-u2 fi-hsw-4200u fi-bsw-cyan fi-ilk-650 fi-apl-guc fi-ctg-p8600 bat-jsl-1

Build changes
-------------

* Linux: CI_DRM_10688 -> Patchwork_21264

CI-20190529: 20190529
CI_DRM_10688: 639fd9206601fb81fbddc3a6f8d2d89816a8ba68 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6233: a2e7a4583f0f68218c53cfe7b0ea8cc34b49cae9 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21264: 0d374b80323e61f9cd9ffdbbb890b90c3a4d1e71 @ git://anongit.freedesktop.org/gfx-ci/linux

== Linux commits ==

0d374b80323e drm/i915/ttm: enable shmem tt backend e2a24624b079 drm/i915/ttm: use cached system pages when evicting lmem 564952863348 drm/i915/ttm: move shrinker management into adjust_lru b3479dc20fbe drm/i915: add some kernel-doc for shrink_pin and friends 74573c5598ba drm/i915: drop unneeded make_unshrinkable in free_object b12519d84ec2 drm/i915/gtt: drop unneeded make_unshrinkable 1d7586376c20 drm/i915/ttm: add tt shmem backend c4bb02dc6bd4 drm/i915/gem: Break out some shmem backend utils

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html

#11 lore raw

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Matthew Auld
== Series Details ==

== Series Details ==

Series: series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
URL : https://patchwork.freedesktop.org/series/95501/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_10688_full -> Patchwork_21264_full
====================================================

Summary
-------

**FAILURE**

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

Possible new issues
-------------------

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

### IGT changes ###

#### Possible regressions ####

* igt@gem_sync@basic-many-each:
- shard-apl: NOTRUN -> [INCOMPLETE][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]

* igt@i915_pm_dc@dc9-dpms:
- shard-iclb: [PASS][2] -> [FAIL][3]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb5/igt@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@[email protected]

#### Suppressed ####

The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.

* {igt@gem_pxp@dmabuf-shared-protected-dst-is-context-refcounted}:
- shard-iclb: NOTRUN -> [SKIP][4]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* {igt@gem_pxp@verify-pxp-execution-after-suspend-resume}:
- shard-tglb: NOTRUN -> [SKIP][5] +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

Known issues
------------

Here are the changes found in Patchwork_21264_full that come from known issues:

### IGT changes ###

#### Issues hit ####

* igt@feature_discovery@psr2:
- shard-iclb: NOTRUN -> [SKIP][6] ([i915#658]) +1 similar issue
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@gem_ctx_isolation@preservation-s3@vecs0:
- shard-skl: [PASS][7] -> [INCOMPLETE][8] ([i915#146] / [i915#198])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl10/igt@gem_ctx_isolation@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl7/igt@gem_ctx_isolation@[email protected]

* igt@gem_ctx_param@set-priority-not-supported:
- shard-tglb: NOTRUN -> [SKIP][9] ([fdo#109314])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@gem_ctx_persistence@smoketest:
- shard-snb: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#1099]) +4 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@gem_eio@in-flight-contexts-immediate:
- shard-skl: [PASS][11] -> [TIMEOUT][12] ([i915#3063])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl5/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@[email protected]

* igt@gem_eio@unwedge-stress:
- shard-snb: NOTRUN -> [FAIL][13] ([i915#3354])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@gem_exec_fair@basic-none@vcs1:
- shard-kbl: [PASS][14] -> [FAIL][15] ([i915#2842])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@gem_exec_fair@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl1/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][16] -> [FAIL][17] ([i915#2842])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb3/igt@gem_exec_fair@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace@vcs1:
- shard-iclb: NOTRUN -> [FAIL][18] ([i915#2842])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-sync@rcs0:
- shard-kbl: [PASS][19] -> [SKIP][20] ([fdo#109271]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl3/igt@gem_exec_fair@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl6/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [PASS][21] -> [FAIL][22] ([i915#2842])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-glk5/igt@gem_exec_fair@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-glk7/igt@gem_exec_fair@[email protected]
- shard-iclb: [PASS][23] -> [FAIL][24] ([i915#2849])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb1/igt@gem_exec_fair@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb7/igt@gem_exec_fair@[email protected]

* igt@gem_exec_flush@basic-batch-kernel-default-cmd:
- shard-tglb: NOTRUN -> [SKIP][25] ([fdo#109313])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@gem_exec_params@no-blt:
- shard-iclb: NOTRUN -> [SKIP][26] ([fdo#109283])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@gem_exec_params@no-vebox:
- shard-tglb: NOTRUN -> [SKIP][27] ([fdo#109283])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@gem_mmap_gtt@cpuset-medium-copy-xy:
- shard-apl: NOTRUN -> [DMESG-WARN][28] ([i915#180] / [i915#203] / [i915#62]) +4 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]

* igt@gem_pread@exhaustion:
- shard-kbl: NOTRUN -> [WARN][29] ([i915#2658])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@gem_pwrite@basic-exhaustion:
- shard-apl: NOTRUN -> [WARN][30] ([i915#2658])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@gem_userptr_blits@dmabuf-sync:
- shard-tglb: NOTRUN -> [SKIP][31] ([i915#3323])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@gem_userptr_blits@dmabuf-unsync:
- shard-tglb: NOTRUN -> [SKIP][32] ([i915#3297])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@gem_userptr_blits@input-checking:
- shard-apl: NOTRUN -> [DMESG-WARN][33] ([i915#3002]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][34] ([i915#2724])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@gen3_render_tiledy_blits:
- shard-tglb: NOTRUN -> [SKIP][35] ([fdo#109289]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@gen3_render_tiledy_blits.html

* igt@gen9_exec_parse@batch-without-end:
- shard-iclb: NOTRUN -> [SKIP][36] ([i915#2856])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@gen9_exec_parse@bb-start-cmd:
- shard-tglb: NOTRUN -> [SKIP][37] ([i915#2856]) +2 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@i915_module_load@reload-with-fault-injection:
- shard-skl: [PASS][38] -> [DMESG-WARN][39] ([i915#1982]) +2 similar issues
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl6/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl4/igt@[email protected]

* igt@i915_pm_dc@dc6-dpms:
- shard-iclb: [PASS][40] -> [FAIL][41] ([i915#454])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb7/igt@[email protected]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@i915_selftest@live@gt_lrc:
- shard-tglb: NOTRUN -> [DMESG-FAIL][42] ([i915#2373])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@i915_selftest@live@gt_lrc.html

* igt@i915_selftest@live@gt_pm:
- shard-tglb: NOTRUN -> [DMESG-FAIL][43] ([i915#1759] / [i915#2291])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@i915_selftest@live@gt_pm.html

* igt@i915_selftest@live@mman:
- shard-apl: NOTRUN -> [DMESG-WARN][44] ([i915#203]) +33 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@i915_selftest@[email protected]

* igt@i915_suspend@sysfs-reader:
- shard-apl: [PASS][45] -> [DMESG-WARN][46] ([i915#180]) +3 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-apl2/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl1/igt@[email protected]

* igt@kms_big_fb@linear-64bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][47] ([fdo#110725] / [fdo#111614])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-kbl: NOTRUN -> [SKIP][48] ([fdo#109271] / [i915#3777])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180:
- shard-apl: NOTRUN -> [DMESG-WARN][49] ([i915#180] / [i915#1982] / [i915#203] / [i915#62])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]

* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-apl: NOTRUN -> [SKIP][50] ([fdo#109271] / [i915#3777])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]

* igt@kms_big_fb@yf-tiled-32bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][51] ([fdo#111615]) +3 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-async-flip:
- shard-iclb: NOTRUN -> [SKIP][52] ([fdo#110723])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-kbl: NOTRUN -> [SKIP][53] ([fdo#109271] / [i915#3886]) +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html
- shard-skl: NOTRUN -> [SKIP][54] ([fdo#109271] / [i915#3886])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][55] ([fdo#109278] / [i915#3886])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#3886]) +11 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][57] ([i915#3689] / [i915#3886]) +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-missing-ccs-buffer-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][58] ([i915#3689]) +3 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_ccs@pipe-c-missing-ccs-buffer-yf_tiled_ccs.html

* igt@kms_chamelium@dp-hpd:
- shard-skl: NOTRUN -> [SKIP][59] ([fdo#109271] / [fdo#111827])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]

* igt@kms_chamelium@hdmi-mode-timings:
- shard-snb: NOTRUN -> [SKIP][60] ([fdo#109271] / [fdo#111827]) +14 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb7/igt@[email protected]

* igt@kms_color@pipe-d-ctm-0-75:
- shard-iclb: NOTRUN -> [SKIP][61] ([fdo#109278] / [i915#1149])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-iclb: NOTRUN -> [SKIP][62] ([fdo#109284] / [fdo#111827]) +1 similar issue
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_color_chamelium@pipe-a-ctm-limited-range:
- shard-apl: NOTRUN -> [SKIP][63] ([fdo#109271] / [fdo#111827]) +23 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]

* igt@kms_color_chamelium@pipe-c-ctm-limited-range:
- shard-kbl: NOTRUN -> [SKIP][64] ([fdo#109271] / [fdo#111827]) +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_color_chamelium@pipe-d-ctm-green-to-red:
- shard-tglb: NOTRUN -> [SKIP][65] ([fdo#109284] / [fdo#111827]) +6 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_content_protection@atomic-dpms:
- shard-apl: NOTRUN -> [TIMEOUT][66] ([i915#1319])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]

* igt@kms_content_protection@legacy:
- shard-kbl: NOTRUN -> [TIMEOUT][67] ([i915#1319])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_cursor_crc@pipe-a-cursor-512x512-offscreen:
- shard-iclb: NOTRUN -> [SKIP][68] ([fdo#109278] / [fdo#109279])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [PASS][69] -> [DMESG-WARN][70] ([i915#180]) +3 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl3/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl7/igt@[email protected]

* igt@kms_cursor_crc@pipe-b-cursor-32x10-random:
- shard-kbl: NOTRUN -> [SKIP][71] ([fdo#109271]) +73 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_cursor_crc@pipe-b-cursor-512x170-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][72] ([i915#3359])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@kms_cursor_crc@pipe-b-cursor-512x512-random:
- shard-tglb: NOTRUN -> [SKIP][73] ([fdo#109279] / [i915#3359])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_cursor_crc@pipe-c-cursor-32x32-onscreen:
- shard-tglb: NOTRUN -> [SKIP][74] ([i915#3319])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_cursor_crc@pipe-d-cursor-64x64-rapid-movement:
- shard-iclb: NOTRUN -> [SKIP][75] ([fdo#109278]) +7 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-skl: [PASS][76] -> [FAIL][77] ([i915#2346])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl3/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]

* igt@kms_dp_tiled_display@basic-test-pattern-with-chamelium:
- shard-tglb: NOTRUN -> [SKIP][78] ([i915#3528])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [PASS][79] -> [INCOMPLETE][80] ([i915#180] / [i915#1982])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-apl6/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]
- shard-tglb: [PASS][81] -> [INCOMPLETE][82] ([i915#456])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb5/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb7/igt@[email protected]

* igt@kms_flip@2x-absolute-wf_vblank:
- shard-tglb: NOTRUN -> [SKIP][83] ([fdo#111825] / [i915#3966])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_flip@2x-absolute-wf_vblank.html

* igt@kms_flip@2x-plain-flip-ts-check@ab-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][84] -> [FAIL][85] ([i915#2122])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-glk4/igt@kms_flip@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-glk6/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-skl: [PASS][86] -> [FAIL][87] ([i915#79])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl9/igt@kms_flip@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl2/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-expired-vblank@a-edp1:
- shard-skl: NOTRUN -> [FAIL][88] ([i915#79])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-suspend@a-edp1:
- shard-tglb: [PASS][89] -> [INCOMPLETE][90] ([i915#2411] / [i915#456])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb5/igt@kms_flip@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb7/igt@kms_flip@[email protected]

* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-blt:
- shard-snb: NOTRUN -> [SKIP][91] ([fdo#109271]) +309 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc:
- shard-iclb: NOTRUN -> [SKIP][92] ([fdo#109280])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc.html

* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite:
- shard-tglb: NOTRUN -> [SKIP][93] ([fdo#111825]) +15 similar issues
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite.html

* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][94] -> [FAIL][95] ([i915#1188])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl5/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl10/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-a-alpha-basic:
- shard-apl: NOTRUN -> [FAIL][96] ([fdo#108145] / [i915#265]) +1 similar issue
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-kbl: NOTRUN -> [FAIL][97] ([i915#265])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][98] ([i915#265])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][99] ([fdo#108145] / [i915#265]) +1 similar issue
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@[email protected]

* igt@kms_plane_lowres@pipe-c-tiling-x:
- shard-tglb: NOTRUN -> [SKIP][100] ([i915#3536])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-apl: NOTRUN -> [SKIP][101] ([fdo#109271] / [i915#2733])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html

* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
- shard-kbl: NOTRUN -> [SKIP][102] ([fdo#109271] / [i915#658])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-apl: NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#658]) +4 similar issues
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]

* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [PASS][104] -> [SKIP][105] ([fdo#109441]) +1 similar issue
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_psr@psr2_cursor_plane_onoff.html

* igt@kms_psr@psr2_primary_blt:
- shard-tglb: NOTRUN -> [FAIL][106] ([i915#132] / [i915#3467])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_psr@psr2_primary_blt.html

* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: NOTRUN -> [SKIP][107] ([fdo#109441])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@kms_psr@psr2_primary_mmap_cpu.html

* igt@kms_setmode@basic:
- shard-snb: NOTRUN -> [FAIL][108] ([i915#31])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@kms_vblank@pipe-d-wait-idle:
- shard-apl: NOTRUN -> [SKIP][109] ([fdo#109271] / [i915#533]) +2 similar issues
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]

* igt@kms_writeback@writeback-fb-id:
- shard-apl: NOTRUN -> [SKIP][110] ([fdo#109271] / [i915#2437])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]

* igt@nouveau_crc@pipe-b-ctx-flip-detection:
- shard-tglb: NOTRUN -> [SKIP][111] ([i915#2530]) +1 similar issue
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame:
- shard-apl: NOTRUN -> [SKIP][112] ([fdo#109271]) +249 similar issues
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@nouveau_crc@pipe-d-source-outp-complete:
- shard-skl: NOTRUN -> [SKIP][113] ([fdo#109271]) +17 similar issues
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][114] ([fdo#109278] / [i915#2530])
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@perf@polling:
- shard-skl: [PASS][115] -> [FAIL][116] ([i915#1542])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl4/igt@[email protected]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl5/igt@[email protected]

* igt@prime_nv_api@i915_nv_import_twice:
- shard-iclb: NOTRUN -> [SKIP][117] ([fdo#109291]) +2 similar issues
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@prime_nv_api@i915_nv_import_twice.html

* igt@prime_nv_api@i915_self_import_to_different_fd:
- shard-tglb: NOTRUN -> [SKIP][118] ([fdo#109291]) +2 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@prime_nv_api@i915_self_import_to_different_fd.html

* igt@sysfs_clients@recycle-many:
- shard-apl: NOTRUN -> [SKIP][119] ([fdo#109271] / [i915#2994]) +1 similar issue
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]

* igt@sysfs_heartbeat_interval@mixed@bcs0:
- shard-skl: [PASS][120] -> [WARN][121] ([i915#4055])
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@sysfs_heartbeat_interval@[email protected]

* igt@sysfs_heartbeat_interval@mixed@vcs0:
- shard-skl: [PASS][122] -> [FAIL][123] ([i915#1731])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@sysfs_heartbeat_interval@[email protected]

#### Possible fixes ####

* igt@gem_eio@unwedge-stress:
- shard-iclb: [TIMEOUT][124] ([i915#2369] / [i915#2481] / [i915#3070]) -> [PASS][125]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb6/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb6/igt@[email protected]

* igt@gem_exec_fair@basic-none@vecs0:
- shard-kbl: [FAIL][126] ([i915#2842]) -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@gem_exec_fair@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl1/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace@bcs0:
- shard-iclb: [FAIL][128] ([i915#2842]) -> [PASS][129]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb5/igt@gem_exec_fair@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@gem_exec_fair@[email protected]

* igt@gem_sync@basic-many-each:
- shard-kbl: [INCOMPLETE][130] -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl4/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@gem_workarounds@suspend-resume:
- shard-kbl: [DMESG-WARN][132] ([i915#180]) -> [PASS][133] +1 similar issue
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl7/igt@[email protected]

* igt

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html

#12 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Quoted 25 lines · Patchwork

*Patch Details*
*Series:* series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:* https://patchwork.freedesktop.org/series/95501/
*State:* failure
*Details:*
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html CI Bug Log - changes from CI_DRM_10688_full -> Patchwork_21264_full Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI. Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:
IGT changes Possible regressions

Quoted 7 lines
   -

   igt@gem_sync@basic-many-each:
   - shard-apl: NOTRUN -> INCOMPLETE
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]>

Looks unrelated to this series. There were some recent changes merged in this area in the last day or so.

Quoted 10 lines
   -
      -

   igt@i915_pm_dc@dc9-dpms:
   - shard-iclb: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb5/igt@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@[email protected]>

Also unrelated.

Quoted 694 lines
   -

Suppressed

The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.

   -

   {igt@gem_pxp@dmabuf-shared-protected-dst-is-context-refcounted}:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]>
   -

   {igt@gem_pxp@verify-pxp-execution-after-suspend-resume}:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]>
      +1 similar issue

Known issues

Here are the changes found in Patchwork_21264_full that come from known issues:
IGT changes Issues hit

   -

   igt@feature_discovery@psr2:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]>
      ([i915#658]) +1 similar issue
   -

   igt@gem_ctx_isolation@preservation-s3@vecs0:
   - shard-skl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl10/igt@gem_ctx_isolation@[email protected]>
      -> INCOMPLETE
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl7/igt@gem_ctx_isolation@[email protected]>
      ([i915#146] / [i915#198])
   -

   igt@gem_ctx_param@set-priority-not-supported:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]>
      ([fdo#109314])
   -

   igt@gem_ctx_persistence@smoketest:
   - shard-snb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]>
      ([fdo#109271] / [i915#1099]) +4 similar issues
   -

   igt@gem_eio@in-flight-contexts-immediate:
   - shard-skl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl5/igt@[email protected]>
      -> TIMEOUT
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@[email protected]>
      ([i915#3063])
   -

   igt@gem_eio@unwedge-stress:
   - shard-snb: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]>
      ([i915#3354])
   -

   igt@gem_exec_fair@basic-none@vcs1:
   - shard-kbl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@gem_exec_fair@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl1/igt@gem_exec_fair@[email protected]>
      ([i915#2842])
   -

   igt@gem_exec_fair@basic-pace-share@rcs0:
   - shard-tglb: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb3/igt@gem_exec_fair@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@gem_exec_fair@[email protected]>
      ([i915#2842])
   -

   igt@gem_exec_fair@basic-pace@vcs1:
   - shard-iclb: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@gem_exec_fair@[email protected]>
      ([i915#2842])
   -

   igt@gem_exec_fair@basic-sync@rcs0:
   - shard-kbl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl3/igt@gem_exec_fair@[email protected]>
      -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl6/igt@gem_exec_fair@[email protected]>
      ([fdo#109271]) +1 similar issue
   -

   igt@gem_exec_fair@basic-throttle@rcs0:
   -

      shard-glk: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-glk5/igt@gem_exec_fair@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-glk7/igt@gem_exec_fair@[email protected]>
      ([i915#2842])
      -

      shard-iclb: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb1/igt@gem_exec_fair@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb7/igt@gem_exec_fair@[email protected]>
      ([i915#2849])
      -

   igt@gem_exec_flush@basic-batch-kernel-default-cmd:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]>
      ([fdo#109313])
   -

   igt@gem_exec_params@no-blt:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]>
      ([fdo#109283])
   -

   igt@gem_exec_params@no-vebox:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]>
      ([fdo#109283])
   -

   igt@gem_mmap_gtt@cpuset-medium-copy-xy:
   - shard-apl: NOTRUN -> DMESG-WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]>
      ([i915#180] / [i915#203] / [i915#62]) +4 similar issues
   -

   igt@gem_pread@exhaustion:
   - shard-kbl: NOTRUN -> WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]>
      ([i915#2658])
   -

   igt@gem_pwrite@basic-exhaustion:
   - shard-apl: NOTRUN -> WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]>
      ([i915#2658])
   -

   igt@gem_userptr_blits@dmabuf-sync:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]>
      ([i915#3323])
   -

   igt@gem_userptr_blits@dmabuf-unsync:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]>
      ([i915#3297])
   -

   igt@gem_userptr_blits@input-checking:
   - shard-apl: NOTRUN -> DMESG-WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]>
      ([i915#3002]) +1 similar issue
   -

   igt@gem_userptr_blits@vma-merge:
   - shard-snb: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]>
      ([i915#2724])
   -

   igt@gen3_render_tiledy_blits:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@gen3_render_tiledy_blits.html>
      ([fdo#109289]) +1 similar issue
   -

   igt@gen9_exec_parse@batch-without-end:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]>
      ([i915#2856])
   -

   igt@gen9_exec_parse@bb-start-cmd:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]>
      ([i915#2856]) +2 similar issues
   -

   igt@i915_module_load@reload-with-fault-injection:
   - shard-skl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl6/igt@[email protected]>
      -> DMESG-WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl4/igt@[email protected]>
      ([i915#1982]) +2 similar issues
   -

   igt@i915_pm_dc@dc6-dpms:
   - shard-iclb: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb7/igt@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]>
      ([i915#454])
   -

   igt@i915_selftest@live@gt_lrc:
   - shard-tglb: NOTRUN -> DMESG-FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@i915_selftest@live@gt_lrc.html>
      ([i915#2373])
   -

   igt@i915_selftest@live@gt_pm:
   - shard-tglb: NOTRUN -> DMESG-FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@i915_selftest@live@gt_pm.html>
      ([i915#1759] / [i915#2291])
   -

   igt@i915_selftest@live@mman:
   - shard-apl: NOTRUN -> DMESG-WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@i915_selftest@[email protected]>
      ([i915#203]) +33 similar issues
   -

   igt@i915_suspend@sysfs-reader:
   - shard-apl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-apl2/igt@[email protected]>
      -> DMESG-WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl1/igt@[email protected]>
      ([i915#180]) +3 similar issues
   -

   igt@kms_big_fb@linear-64bpp-rotate-270:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]>
      ([fdo#110725] / [fdo#111614])
   -

   igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip:
   - shard-kbl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]>
      ([fdo#109271] / [i915#3777])
   -

   igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180:
   - shard-apl: NOTRUN -> DMESG-WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]>
      ([i915#180] / [i915#1982] / [i915#203] / [i915#62])
   -

   igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip:
   - shard-apl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]>
      ([fdo#109271] / [i915#3777])
   -

   igt@kms_big_fb@yf-tiled-32bpp-rotate-270:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]>
      ([fdo#111615]) +3 similar issues
   -

   igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-async-flip:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]>
      ([fdo#110723])
   -

   igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
   -

      shard-kbl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html>
      ([fdo#109271] / [i915#3886]) +1 similar issue
      -

      shard-skl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html>
      ([fdo#109271] / [i915#3886])
      -

   igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html>
      ([fdo#109278] / [i915#3886])
   -

   igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs:
   - shard-apl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs.html>
      ([fdo#109271] / [i915#3886]) +11 similar issues
   -

   igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html>
      ([i915#3689] / [i915#3886]) +1 similar issue
   -

   igt@kms_ccs@pipe-c-missing-ccs-buffer-yf_tiled_ccs:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_ccs@pipe-c-missing-ccs-buffer-yf_tiled_ccs.html>
      ([i915#3689]) +3 similar issues
   -

   igt@kms_chamelium@dp-hpd:
   - shard-skl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]>
      ([fdo#109271] / [fdo#111827])
   -

   igt@kms_chamelium@hdmi-mode-timings:
   - shard-snb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb7/igt@[email protected]>
      ([fdo#109271] / [fdo#111827]) +14 similar issues
   -

   igt@kms_color@pipe-d-ctm-0-75:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]>
      ([fdo#109278] / [i915#1149])
   -

   igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]>
      ([fdo#109284] / [fdo#111827]) +1 similar issue
   -

   igt@kms_color_chamelium@pipe-a-ctm-limited-range:
   - shard-apl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]>
      ([fdo#109271] / [fdo#111827]) +23 similar issues
   -

   igt@kms_color_chamelium@pipe-c-ctm-limited-range:
   - shard-kbl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]>
      ([fdo#109271] / [fdo#111827]) +1 similar issue
   -

   igt@kms_color_chamelium@pipe-d-ctm-green-to-red:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]>
      ([fdo#109284] / [fdo#111827]) +6 similar issues
   -

   igt@kms_content_protection@atomic-dpms:
   - shard-apl: NOTRUN -> TIMEOUT
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]>
      ([i915#1319])
   -

   igt@kms_content_protection@legacy:
   - shard-kbl: NOTRUN -> TIMEOUT
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]>
      ([i915#1319])
   -

   igt@kms_cursor_crc@pipe-a-cursor-512x512-offscreen:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]>
      ([fdo#109278] / [fdo#109279])
   -

   igt@kms_cursor_crc@pipe-a-cursor-suspend:
   - shard-kbl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl3/igt@[email protected]>
      -> DMESG-WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl7/igt@[email protected]>
      ([i915#180]) +3 similar issues
   -

   igt@kms_cursor_crc@pipe-b-cursor-32x10-random:
   - shard-kbl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]>
      ([fdo#109271]) +73 similar issues
   -

   igt@kms_cursor_crc@pipe-b-cursor-512x170-rapid-movement:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]>
      ([i915#3359])
   -

   igt@kms_cursor_crc@pipe-b-cursor-512x512-random:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]>
      ([fdo#109279] / [i915#3359])
   -

   igt@kms_cursor_crc@pipe-c-cursor-32x32-onscreen:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]>
      ([i915#3319])
   -

   igt@kms_cursor_crc@pipe-d-cursor-64x64-rapid-movement:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]>
      ([fdo#109278]) +7 similar issues
   -

   igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
   - shard-skl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl3/igt@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]>
      ([i915#2346])
   -

   igt@kms_dp_tiled_display@basic-test-pattern-with-chamelium:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]>
      ([i915#3528])
   -

   igt@kms_fbcon_fbt@fbc-suspend:
   -

      shard-apl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-apl6/igt@[email protected]>
      -> INCOMPLETE
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]>
      ([i915#180] / [i915#1982])
      -

      shard-tglb: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb5/igt@[email protected]>
      -> INCOMPLETE
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb7/igt@[email protected]>
      ([i915#456])
      -

   igt@kms_flip@2x-absolute-wf_vblank:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_flip@2x-absolute-wf_vblank.html>
      ([fdo#111825] / [i915#3966])
   -

   igt@kms_flip@2x-plain-flip-ts-check@ab-hdmi-a1-hdmi-a2:
   - shard-glk: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-glk4/igt@kms_flip@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-glk6/igt@kms_flip@[email protected]>
      ([i915#2122])
   -

   igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
   - shard-skl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl9/igt@kms_flip@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl2/igt@kms_flip@[email protected]>
      ([i915#79])
   -

   igt@kms_flip@flip-vs-expired-vblank@a-edp1:
   - shard-skl: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@kms_flip@[email protected]>
      ([i915#79])
   -

   igt@kms_flip@flip-vs-suspend@a-edp1:
   - shard-tglb: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb5/igt@kms_flip@[email protected]>
      -> INCOMPLETE
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb7/igt@kms_flip@[email protected]>
      ([i915#2411] / [i915#456])
   -

   igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-blt:
   - shard-snb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]>
      ([fdo#109271]) +309 similar issues
   -

   igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc.html>
      ([fdo#109280])
   -

   igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite.html>
      ([fdo#111825]) +15 similar issues
   -

   igt@kms_hdr@bpc-switch-dpms:
   - shard-skl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl5/igt@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl10/igt@[email protected]>
      ([i915#1188])
   -

   igt@kms_plane_alpha_blend@pipe-a-alpha-basic:
   - shard-apl: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]>
      ([fdo#108145] / [i915#265]) +1 similar issue
   -

   igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
   - shard-kbl: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@[email protected]>
      ([i915#265])
   -

   igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
   - shard-apl: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]>
      ([i915#265])
   -

   igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
   - shard-kbl: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@[email protected]>
      ([fdo#108145] / [i915#265]) +1 similar issue
   -

   igt@kms_plane_lowres@pipe-c-tiling-x:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]>
      ([i915#3536])
   -

   igt@kms_plane_scaling
   @scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
   - shard-apl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html>
      ([fdo#109271] / [i915#2733])
   -

   igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
   - shard-kbl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]>
      ([fdo#109271] / [i915#658])
   -

   igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
   - shard-apl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]>
      ([fdo#109271] / [i915#658]) +4 similar issues
   -

   igt@kms_psr@psr2_cursor_plane_onoff:
   - shard-iclb: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html>
      -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_psr@psr2_cursor_plane_onoff.html>
      ([fdo#109441]) +1 similar issue
   -

   igt@kms_psr@psr2_primary_blt:
   - shard-tglb: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_psr@psr2_primary_blt.html>
      ([i915#132] / [i915#3467])
   -

   igt@kms_psr@psr2_primary_mmap_cpu:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@kms_psr@psr2_primary_mmap_cpu.html>
      ([fdo#109441])
   -

   igt@kms_setmode@basic:
   - shard-snb: NOTRUN -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]>
      ([i915#31])
   -

   igt@kms_vblank@pipe-d-wait-idle:
   - shard-apl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]>
      ([fdo#109271] / [i915#533]) +2 similar issues
   -

   igt@kms_writeback@writeback-fb-id:
   - shard-apl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]>
      ([fdo#109271] / [i915#2437])
   -

   igt@nouveau_crc@pipe-b-ctx-flip-detection:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]>
      ([i915#2530]) +1 similar issue
   -

   igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame:
   - shard-apl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]>
      ([fdo#109271]) +249 similar issues
   -

   igt@nouveau_crc@pipe-d-source-outp-complete:
   -

      shard-skl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]>
      ([fdo#109271]) +17 similar issues
      -

      shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]>
      ([fdo#109278] / [i915#2530])
      -

   igt@perf@polling:
   - shard-skl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl4/igt@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl5/igt@[email protected]>
      ([i915#1542])
   -

   igt@prime_nv_api@i915_nv_import_twice:
   - shard-iclb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@prime_nv_api@i915_nv_import_twice.html>
      ([fdo#109291]) +2 similar issues
   -

   igt@prime_nv_api@i915_self_import_to_different_fd:
   - shard-tglb: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@prime_nv_api@i915_self_import_to_different_fd.html>
      ([fdo#109291]) +2 similar issues
   -

   igt@sysfs_clients@recycle-many:
   - shard-apl: NOTRUN -> SKIP
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]>
      ([fdo#109271] / [i915#2994]) +1 similar issue
   -

   igt@sysfs_heartbeat_interval@mixed@bcs0:
   - shard-skl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]>
      -> WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@sysfs_heartbeat_interval@[email protected]>
      ([i915#4055])
   -

   igt@sysfs_heartbeat_interval@mixed@vcs0:
   - shard-skl: PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]>
      -> FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@sysfs_heartbeat_interval@[email protected]>
      ([i915#1731])

Possible fixes

   -

   igt@gem_eio@unwedge-stress:
   - shard-iclb: TIMEOUT
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb6/igt@[email protected]>
      ([i915#2369] / [i915#2481] / [i915#3070]) -> PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb6/igt@[email protected]>
   -

   igt@gem_exec_fair@basic-none@vecs0:
   - shard-kbl: FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@gem_exec_fair@[email protected]>
      ([i915#2842]) -> PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl1/igt@gem_exec_fair@[email protected]>
   -

   igt@gem_exec_fair@basic-pace@bcs0:
   - shard-iclb: FAIL
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb5/igt@gem_exec_fair@[email protected]>
      ([i915#2842]) -> PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@gem_exec_fair@[email protected]>
   -

   igt@gem_sync@basic-many-each:
   - shard-kbl: INCOMPLETE
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl4/igt@[email protected]>
      -> PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]>
   -

   igt@gem_workarounds@suspend-resume:
   - shard-kbl: DMESG-WARN
      <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@[email protected]>
      ([i915#180]) -> PASS
      <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl7/igt@[email protected]>
      +1 similar issue
   -

   igt
#13 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Patchwork

Hi,

Quoted 30 lines · Patchwork

*Patch Details*
*Series:* series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:* https://patchwork.freedesktop.org/series/95501/ <https://patchwork.freedesktop.org/series/95501/>
*State:* failure
*Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html>

CI Bug Log - changes from CI_DRM_10688_full -> Patchwork_21264_full

Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

IGT changes

Quoted 8 lines

Possible regressions

*

igt@gem_sync@basic-many-each:

o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]>

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each
<1> [188.935462] BUG: kernel NULL pointer dereference, address: 0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode
<1> [188.935495] #PF: error_code(0x0002) - not-present page
<6> [188.935504] PGD 0 P4D 0
<4> [188.935512] Oops: 0002 [#1] PREEMPT SMP NOPTI
<4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1
<4> [188.935535] Hardware name: /NUC6CAYB, BIOS AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018
<4> [188.935546] RIP: 0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01 41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS: 00010202
<4> [188.935593] RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI: ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09: 00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12: ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15: 0000000000000000
<4> [188.935643] FS: 00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000
<4> [188.935655] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [188.935665] CR2: 0000000000000010 CR3: 000000012d0a4000 CR4: 00000000003506e0
<4> [188.935676] Call Trace:

<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915]
<4> [188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915]
<4> [188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936533]  drm_ioctl_kernel+0xae/0x140
<4> [188.936546]  drm_ioctl+0x201/0x3d0
<4> [188.936555]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936820]  ? __fget_files+0xc2/0x1c0
<4> [188.936830]  ? __fget_files+0xda/0x1c0
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0
<4> [188.936848]  do_syscall_64+0x3a/0xb0
<4> [188.936859]  entry_SYSCALL_64_after_hwframe+0x44/0xae

Regards,

Tvrtko

#15 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Christian König
Quoted 43 lines · Christian König

Am 07.10.21 um 11:15 schrieb Tvrtko Ursulin:

Quoted 42 lines

Hi,

Quoted 39 lines · Patchwork

*Patch Details*
*Series:*    series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:*    https://patchwork.freedesktop.org/series/95501/ <https://patchwork.freedesktop.org/series/95501/>
*State:*    failure
*Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html>

  CI Bug Log - changes from CI_DRM_10688_full -> Patchwork_21264_full

    Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

    Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

      IGT changes

        Possible regressions

  *

    igt@gem_sync@basic-many-each:

      o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]>

Quoted 39 lines
Quoted 1 line

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

Probably the later. I'm going to take a look.

Thanks for the notice,
Christian.

Quoted 32 lines

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each
<1> [188.935462] BUG: kernel NULL pointer dereference, address: 0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode
<1> [188.935495] #PF: error_code(0x0002) - not-present page
<6> [188.935504] PGD 0 P4D 0
<4> [188.935512] Oops: 0002 [#1] PREEMPT SMP NOPTI
<4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1
<4> [188.935535] Hardware name:  /NUC6CAYB, BIOS AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018
<4> [188.935546] RIP: 0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01 41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS: 00010202
<4> [188.935593] RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI: ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09: 00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12: ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15: 0000000000000000
<4> [188.935643] FS:  00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000
<4> [188.935655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [188.935665] CR2: 0000000000000010 CR3: 000000012d0a4000 CR4: 00000000003506e0
<4> [188.935676] Call Trace:
<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915]
<4> [188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915]
<4> [188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936533]  drm_ioctl_kernel+0xae/0x140
<4> [188.936546]  drm_ioctl+0x201/0x3d0
<4> [188.936555]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936820]  ? __fget_files+0xc2/0x1c0
<4> [188.936830]  ? __fget_files+0xda/0x1c0
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0
<4> [188.936848]  do_syscall_64+0x3a/0xb0
<4> [188.936859]  entry_SYSCALL_64_after_hwframe+0x44/0xae

FWIW if you disassemble the code it seems to be crashing in:

(*shared)[(*shared_count)++] = fence; // mov %r14, (%rdx, %rax, 8)

RDX is *shared, RAX is *shared_count, RCX is *shared_count++ (for the next iteration. R13 is share and R12 shared_count.

That *shared can contain 0000000000000010 makes no sense to me. At least yet. :)

Regards,

Tvrtko

#14 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Tvrtko Ursulin

Am 07.10.21 um 11:15 schrieb Tvrtko Ursulin:

Quoted 35 lines

Hi,

Quoted 32 lines · Patchwork

*Patch Details*
*Series:*    series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:*    https://patchwork.freedesktop.org/series/95501/ <https://patchwork.freedesktop.org/series/95501/>
*State:*    failure
*Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html>

  CI Bug Log - changes from CI_DRM_10688_full -> Patchwork_21264_full

    Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

    Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

      IGT changes

        Possible regressions

Quoted 7 lines
Quoted 6 lines

  *

    igt@gem_sync@basic-many-each:

      o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]>

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

Probably the later. I'm going to take a look.

Thanks for the notice,
Christian.

Quoted 36 lines

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each
<1> [188.935462] BUG: kernel NULL pointer dereference, address: 0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode
<1> [188.935495] #PF: error_code(0x0002) - not-present page
<6> [188.935504] PGD 0 P4D 0
<4> [188.935512] Oops: 0002 [#1] PREEMPT SMP NOPTI
<4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1
<4> [188.935535] Hardware name:  /NUC6CAYB, BIOS AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018
<4> [188.935546] RIP: 0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01 41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS: 00010202
<4> [188.935593] RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI: ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09: 00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12: ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15: 0000000000000000
<4> [188.935643] FS:  00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000
<4> [188.935655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [188.935665] CR2: 0000000000000010 CR3: 000000012d0a4000 CR4: 00000000003506e0
<4> [188.935676] Call Trace:
<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915]
<4> [188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915]
<4> [188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936533]  drm_ioctl_kernel+0xae/0x140
<4> [188.936546]  drm_ioctl+0x201/0x3d0
<4> [188.936555]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936820]  ? __fget_files+0xc2/0x1c0
<4> [188.936830]  ? __fget_files+0xda/0x1c0
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0
<4> [188.936848]  do_syscall_64+0x3a/0xb0
<4> [188.936859]  entry_SYSCALL_64_after_hwframe+0x44/0xae

Regards,

Tvrtko

#17 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Christian König
Quoted 92 lines · Christian König

Am 07.10.21 um 12:51 schrieb Tvrtko Ursulin:

Quoted 91 lines · Christian König
Quoted 43 lines

Am 07.10.21 um 11:15 schrieb Tvrtko Ursulin:

Quoted 42 lines

Hi,

Quoted 39 lines · Patchwork

*Patch Details*
*Series:*    series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:*    https://patchwork.freedesktop.org/series/95501/ <https://patchwork.freedesktop.org/series/95501/>
*State:*    failure
*Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html>

  CI Bug Log - changes from CI_DRM_10688_full -> Patchwork_21264_full

    Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

    Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

      IGT changes

        Possible regressions

  *

    igt@gem_sync@basic-many-each:

      o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]>

Quoted 39 lines
Quoted 1 line

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

Probably the later. I'm going to take a look.

Thanks for the notice,
Christian.

Quoted 32 lines

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each
<1> [188.935462] BUG: kernel NULL pointer dereference, address: 0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode
<1> [188.935495] #PF: error_code(0x0002) - not-present page
<6> [188.935504] PGD 0 P4D 0
<4> [188.935512] Oops: 0002 [#1] PREEMPT SMP NOPTI
<4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1
<4> [188.935535] Hardware name:  /NUC6CAYB, BIOS AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018
<4> [188.935546] RIP: 0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01 41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS: 00010202
<4> [188.935593] RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI: ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09: 00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12: ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15: 0000000000000000
<4> [188.935643] FS:  00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000
<4> [188.935655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [188.935665] CR2: 0000000000000010 CR3: 000000012d0a4000 CR4: 00000000003506e0
<4> [188.935676] Call Trace:
<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915]
<4> [188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915]
<4> [188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936533]  drm_ioctl_kernel+0xae/0x140
<4> [188.936546]  drm_ioctl+0x201/0x3d0
<4> [188.936555]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936820]  ? __fget_files+0xc2/0x1c0
<4> [188.936830]  ? __fget_files+0xda/0x1c0
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0
<4> [188.936848]  do_syscall_64+0x3a/0xb0
<4> [188.936859] entry_SYSCALL_64_after_hwframe+0x44/0xae

FWIW if you disassemble the code it seems to be crashing in:

  (*shared)[(*shared_count)++] = fence; // mov %r14, (%rdx, %rax, 8)

RDX is *shared, RAX is *shared_count, RCX is *shared_count++ (for the next iteration. R13 is share and R12 shared_count.

Quoted 7 lines
Quoted 1 line

That *shared can contain 0000000000000010 makes no sense to me. At least yet. :)

Yeah, me neither. I've gone over the whole code multiple time now and absolutely don't get what's happening here.

Adding some more selftests didn't helped either. As far as I can see the code works as intended.

Do we have any other reports of crashes?

Yes, sporadic but present across different platforms since the change went it: https://intel-gfx-ci.01.org/tree/drm-tip/igt@[email protected]. So issue is probably real.

Did not find any other tests failing with the same signature. Lakshmi are you perhaps able to search for the same or similar signature across the whole set of recent results?

Regards,

Tvrtko

#16 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Tvrtko Ursulin

Am 07.10.21 um 12:51 schrieb Tvrtko Ursulin:

Quoted 85 lines · Christian König
Quoted 43 lines

Am 07.10.21 um 11:15 schrieb Tvrtko Ursulin:

Quoted 42 lines

Hi,

Quoted 39 lines · Patchwork

*Patch Details*
*Series:*    series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:*    https://patchwork.freedesktop.org/series/95501/ <https://patchwork.freedesktop.org/series/95501/>
*State:*    failure
*Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html>

  CI Bug Log - changes from CI_DRM_10688_full -> Patchwork_21264_full

    Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

    Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

      IGT changes

        Possible regressions

  *

    igt@gem_sync@basic-many-each:

      o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]>

Quoted 39 lines
Quoted 1 line

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

Probably the later. I'm going to take a look.

Thanks for the notice,
Christian.

Quoted 32 lines

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each
<1> [188.935462] BUG: kernel NULL pointer dereference, address: 0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode
<1> [188.935495] #PF: error_code(0x0002) - not-present page
<6> [188.935504] PGD 0 P4D 0
<4> [188.935512] Oops: 0002 [#1] PREEMPT SMP NOPTI
<4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1
<4> [188.935535] Hardware name:  /NUC6CAYB, BIOS AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018
<4> [188.935546] RIP: 0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01 41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS: 00010202
<4> [188.935593] RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI: ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09: 00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12: ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15: 0000000000000000
<4> [188.935643] FS:  00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000
<4> [188.935655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [188.935665] CR2: 0000000000000010 CR3: 000000012d0a4000 CR4: 00000000003506e0
<4> [188.935676] Call Trace:
<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915]
<4> [188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915]
<4> [188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936533]  drm_ioctl_kernel+0xae/0x140
<4> [188.936546]  drm_ioctl+0x201/0x3d0
<4> [188.936555]  ? i915_gem_object_wait+0x410/0x410 [i915]
<4> [188.936820]  ? __fget_files+0xc2/0x1c0
<4> [188.936830]  ? __fget_files+0xda/0x1c0
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0
<4> [188.936848]  do_syscall_64+0x3a/0xb0
<4> [188.936859] entry_SYSCALL_64_after_hwframe+0x44/0xae

Quoted 7 lines

FWIW if you disassemble the code it seems to be crashing in:

  (*shared)[(*shared_count)++] = fence; // mov %r14, (%rdx, %rax, 8)

RDX is *shared, RAX is *shared_count, RCX is *shared_count++ (for the next iteration. R13 is share and R12 shared_count.

That *shared can contain 0000000000000010 makes no sense to me. At least yet. :)

Yeah, me neither. I've gone over the whole code multiple time now and absolutely don't get what's happening here.

Adding some more selftests didn't helped either. As far as I can see the code works as intended.

Do we have any other reports of crashes?

Thanks,
Christian.

Quoted 4 lines

Regards,

Tvrtko

#23 lore raw

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Matthew Auld
== Series Details ==

== Series Details ==

Series: series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
URL : https://patchwork.freedesktop.org/series/95501/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_10688_full -> Patchwork_21264_full
====================================================

Summary
-------

**FAILURE**

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

Possible new issues
-------------------

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

### IGT changes ###

#### Possible regressions ####

* igt@gem_pxp@dmabuf-shared-protected-dst-is-context-refcounted:
- shard-iclb: NOTRUN -> [SKIP][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

#### Suppressed ####

The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.

* igt@gem_pxp@verify-pxp-key-change-after-suspend-resume:
- {shard-rkl}: NOTRUN -> [SKIP][2] +24 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-rkl-2/igt@[email protected]

Known issues
------------

Here are the changes found in Patchwork_21264_full that come from known issues:

### IGT changes ###

#### Issues hit ####

* igt@feature_discovery@psr2:
- shard-iclb: NOTRUN -> [SKIP][3] ([i915#658]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@gem_ctx_isolation@preservation-s3@vecs0:
- shard-skl: [PASS][4] -> [INCOMPLETE][5] ([i915#146] / [i915#198])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl10/igt@gem_ctx_isolation@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl7/igt@gem_ctx_isolation@[email protected]

* igt@gem_ctx_param@set-priority-not-supported:
- shard-tglb: NOTRUN -> [SKIP][6] ([fdo#109314])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@gem_ctx_persistence@smoketest:
- shard-snb: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#1099]) +4 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@gem_eio@in-flight-contexts-immediate:
- shard-skl: [PASS][8] -> [TIMEOUT][9] ([i915#3063])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl5/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@[email protected]

* igt@gem_eio@unwedge-stress:
- shard-snb: NOTRUN -> [FAIL][10] ([i915#3354])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@gem_exec_fair@basic-none@vcs1:
- shard-kbl: [PASS][11] -> [FAIL][12] ([i915#2842])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@gem_exec_fair@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl1/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][13] -> [FAIL][14] ([i915#2842])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb3/igt@gem_exec_fair@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace@vcs1:
- shard-iclb: NOTRUN -> [FAIL][15] ([i915#2842])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-sync@rcs0:
- shard-kbl: [PASS][16] -> [SKIP][17] ([fdo#109271]) +1 similar issue
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl3/igt@gem_exec_fair@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl6/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [PASS][18] -> [FAIL][19] ([i915#2842])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-glk5/igt@gem_exec_fair@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-glk7/igt@gem_exec_fair@[email protected]
- shard-iclb: [PASS][20] -> [FAIL][21] ([i915#2849])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb1/igt@gem_exec_fair@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb7/igt@gem_exec_fair@[email protected]

* igt@gem_exec_flush@basic-batch-kernel-default-cmd:
- shard-tglb: NOTRUN -> [SKIP][22] ([fdo#109313])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@gem_exec_params@no-blt:
- shard-iclb: NOTRUN -> [SKIP][23] ([fdo#109283])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@gem_exec_params@no-vebox:
- shard-tglb: NOTRUN -> [SKIP][24] ([fdo#109283])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@gem_mmap_gtt@cpuset-medium-copy-xy:
- shard-apl: NOTRUN -> [DMESG-WARN][25] ([i915#180] / [i915#203] / [i915#62]) +4 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]

* igt@gem_pread@exhaustion:
- shard-kbl: NOTRUN -> [WARN][26] ([i915#2658])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@gem_pwrite@basic-exhaustion:
- shard-apl: NOTRUN -> [WARN][27] ([i915#2658])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@gem_pxp@verify-pxp-execution-after-suspend-resume:
- shard-tglb: NOTRUN -> [SKIP][28] ([i915#4270]) +1 similar issue
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@gem_sync@basic-many-each:
- shard-apl: NOTRUN -> [INCOMPLETE][29] ([i915#4274])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]

* igt@gem_userptr_blits@dmabuf-sync:
- shard-tglb: NOTRUN -> [SKIP][30] ([i915#3323])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@gem_userptr_blits@dmabuf-unsync:
- shard-tglb: NOTRUN -> [SKIP][31] ([i915#3297])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@gem_userptr_blits@input-checking:
- shard-apl: NOTRUN -> [DMESG-WARN][32] ([i915#3002]) +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][33] ([i915#2724])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@gen3_render_tiledy_blits:
- shard-tglb: NOTRUN -> [SKIP][34] ([fdo#109289]) +1 similar issue
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@gen3_render_tiledy_blits.html

* igt@gen9_exec_parse@batch-without-end:
- shard-iclb: NOTRUN -> [SKIP][35] ([i915#2856])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@gen9_exec_parse@bb-start-cmd:
- shard-tglb: NOTRUN -> [SKIP][36] ([i915#2856]) +2 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@i915_module_load@reload-with-fault-injection:
- shard-skl: [PASS][37] -> [DMESG-WARN][38] ([i915#1982]) +2 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl6/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl4/igt@[email protected]

* igt@i915_pm_dc@dc6-dpms:
- shard-iclb: [PASS][39] -> [FAIL][40] ([i915#454])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb7/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@i915_pm_dc@dc9-dpms:
- shard-iclb: [PASS][41] -> [FAIL][42] ([i915#4275])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb5/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@[email protected]

* igt@i915_selftest@live@gt_lrc:
- shard-tglb: NOTRUN -> [DMESG-FAIL][43] ([i915#2373])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@i915_selftest@live@gt_lrc.html

* igt@i915_selftest@live@gt_pm:
- shard-tglb: NOTRUN -> [DMESG-FAIL][44] ([i915#1759] / [i915#2291])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@i915_selftest@live@gt_pm.html

* igt@i915_selftest@live@mman:
- shard-apl: NOTRUN -> [DMESG-WARN][45] ([i915#203]) +33 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@i915_selftest@[email protected]

* igt@i915_suspend@sysfs-reader:
- shard-apl: [PASS][46] -> [DMESG-WARN][47] ([i915#180]) +3 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-apl2/igt@[email protected]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl1/igt@[email protected]

* igt@kms_big_fb@linear-64bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][48] ([fdo#110725] / [fdo#111614])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-kbl: NOTRUN -> [SKIP][49] ([fdo#109271] / [i915#3777])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180:
- shard-apl: NOTRUN -> [DMESG-WARN][50] ([i915#180] / [i915#1982] / [i915#203] / [i915#62])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]

* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-apl: NOTRUN -> [SKIP][51] ([fdo#109271] / [i915#3777])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]

* igt@kms_big_fb@yf-tiled-32bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][52] ([fdo#111615]) +3 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-async-flip:
- shard-iclb: NOTRUN -> [SKIP][53] ([fdo#110723])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-kbl: NOTRUN -> [SKIP][54] ([fdo#109271] / [i915#3886]) +1 similar issue
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html
- shard-skl: NOTRUN -> [SKIP][55] ([fdo#109271] / [i915#3886])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][56] ([fdo#109278] / [i915#3886])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#3886]) +11 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][58] ([i915#3689] / [i915#3886]) +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-missing-ccs-buffer-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][59] ([i915#3689]) +3 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_ccs@pipe-c-missing-ccs-buffer-yf_tiled_ccs.html

* igt@kms_chamelium@dp-hpd:
- shard-skl: NOTRUN -> [SKIP][60] ([fdo#109271] / [fdo#111827])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]

* igt@kms_chamelium@hdmi-mode-timings:
- shard-snb: NOTRUN -> [SKIP][61] ([fdo#109271] / [fdo#111827]) +14 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb7/igt@[email protected]

* igt@kms_color@pipe-d-ctm-0-75:
- shard-iclb: NOTRUN -> [SKIP][62] ([fdo#109278] / [i915#1149])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-iclb: NOTRUN -> [SKIP][63] ([fdo#109284] / [fdo#111827]) +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_color_chamelium@pipe-a-ctm-limited-range:
- shard-apl: NOTRUN -> [SKIP][64] ([fdo#109271] / [fdo#111827]) +23 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]

* igt@kms_color_chamelium@pipe-c-ctm-limited-range:
- shard-kbl: NOTRUN -> [SKIP][65] ([fdo#109271] / [fdo#111827]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_color_chamelium@pipe-d-ctm-green-to-red:
- shard-tglb: NOTRUN -> [SKIP][66] ([fdo#109284] / [fdo#111827]) +6 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_content_protection@atomic-dpms:
- shard-apl: NOTRUN -> [TIMEOUT][67] ([i915#1319])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]

* igt@kms_content_protection@legacy:
- shard-kbl: NOTRUN -> [TIMEOUT][68] ([i915#1319])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_cursor_crc@pipe-a-cursor-512x512-offscreen:
- shard-iclb: NOTRUN -> [SKIP][69] ([fdo#109278] / [fdo#109279])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [PASS][70] -> [DMESG-WARN][71] ([i915#180]) +3 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl3/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl7/igt@[email protected]

* igt@kms_cursor_crc@pipe-b-cursor-32x10-random:
- shard-kbl: NOTRUN -> [SKIP][72] ([fdo#109271]) +73 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_cursor_crc@pipe-b-cursor-512x170-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][73] ([i915#3359])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@kms_cursor_crc@pipe-b-cursor-512x512-random:
- shard-tglb: NOTRUN -> [SKIP][74] ([fdo#109279] / [i915#3359])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_cursor_crc@pipe-c-cursor-32x32-onscreen:
- shard-tglb: NOTRUN -> [SKIP][75] ([i915#3319])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_cursor_crc@pipe-d-cursor-64x64-rapid-movement:
- shard-iclb: NOTRUN -> [SKIP][76] ([fdo#109278]) +7 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-skl: [PASS][77] -> [FAIL][78] ([i915#2346])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl3/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]

* igt@kms_dp_tiled_display@basic-test-pattern-with-chamelium:
- shard-tglb: NOTRUN -> [SKIP][79] ([i915#3528])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [PASS][80] -> [INCOMPLETE][81] ([i915#180] / [i915#1982])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-apl6/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]
- shard-tglb: [PASS][82] -> [INCOMPLETE][83] ([i915#456])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb5/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb7/igt@[email protected]

* igt@kms_flip@2x-absolute-wf_vblank:
- shard-tglb: NOTRUN -> [SKIP][84] ([fdo#111825] / [i915#3966])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_flip@2x-absolute-wf_vblank.html

* igt@kms_flip@2x-plain-flip-ts-check@ab-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][85] -> [FAIL][86] ([i915#2122])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-glk4/igt@kms_flip@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-glk6/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-skl: [PASS][87] -> [FAIL][88] ([i915#79])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl9/igt@kms_flip@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl2/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-expired-vblank@a-edp1:
- shard-skl: NOTRUN -> [FAIL][89] ([i915#79])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-suspend@a-edp1:
- shard-tglb: [PASS][90] -> [INCOMPLETE][91] ([i915#2411] / [i915#456])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb5/igt@kms_flip@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb7/igt@kms_flip@[email protected]

* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-blt:
- shard-snb: NOTRUN -> [SKIP][92] ([fdo#109271]) +313 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc:
- shard-iclb: NOTRUN -> [SKIP][93] ([fdo#109280])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc.html

* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite:
- shard-tglb: NOTRUN -> [SKIP][94] ([fdo#111825]) +15 similar issues
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite.html

* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][95] -> [FAIL][96] ([i915#1188])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl5/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl10/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-a-alpha-basic:
- shard-apl: NOTRUN -> [FAIL][97] ([fdo#108145] / [i915#265]) +1 similar issue
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-kbl: NOTRUN -> [FAIL][98] ([i915#265])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][99] ([i915#265])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][100] ([fdo#108145] / [i915#265]) +1 similar issue
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@[email protected]

* igt@kms_plane_lowres@pipe-c-tiling-x:
- shard-tglb: NOTRUN -> [SKIP][101] ([i915#3536])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-apl: NOTRUN -> [SKIP][102] ([fdo#109271] / [i915#2733])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html

* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
- shard-kbl: NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#658])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-apl: NOTRUN -> [SKIP][104] ([fdo#109271] / [i915#658]) +4 similar issues
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]

* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [PASS][105] -> [SKIP][106] ([fdo#109441]) +1 similar issue
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_psr@psr2_cursor_plane_onoff.html

* igt@kms_psr@psr2_primary_blt:
- shard-tglb: NOTRUN -> [FAIL][107] ([i915#132] / [i915#3467])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_psr@psr2_primary_blt.html

* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: NOTRUN -> [SKIP][108] ([fdo#109441])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@kms_psr@psr2_primary_mmap_cpu.html

* igt@kms_setmode@basic:
- shard-snb: NOTRUN -> [FAIL][109] ([i915#31])
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@kms_vblank@pipe-d-wait-idle:
- shard-apl: NOTRUN -> [SKIP][110] ([fdo#109271] / [i915#533]) +2 similar issues
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]

* igt@kms_writeback@writeback-fb-id:
- shard-apl: NOTRUN -> [SKIP][111] ([fdo#109271] / [i915#2437])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]

* igt@nouveau_crc@pipe-b-ctx-flip-detection:
- shard-tglb: NOTRUN -> [SKIP][112] ([i915#2530]) +1 similar issue
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame:
- shard-apl: NOTRUN -> [SKIP][113] ([fdo#109271]) +255 similar issues
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@nouveau_crc@pipe-d-source-outp-complete:
- shard-skl: NOTRUN -> [SKIP][114] ([fdo#109271]) +17 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][115] ([fdo#109278] / [i915#2530])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@perf@polling:
- shard-skl: [PASS][116] -> [FAIL][117] ([i915#1542])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl4/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl5/igt@[email protected]

* igt@prime_nv_api@i915_nv_import_twice:
- shard-iclb: NOTRUN -> [SKIP][118] ([fdo#109291]) +2 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@prime_nv_api@i915_nv_import_twice.html

* igt@prime_nv_api@i915_self_import_to_different_fd:
- shard-tglb: NOTRUN -> [SKIP][119] ([fdo#109291]) +2 similar issues
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@prime_nv_api@i915_self_import_to_different_fd.html

* igt@sysfs_clients@recycle-many:
- shard-apl: NOTRUN -> [SKIP][120] ([fdo#109271] / [i915#2994]) +1 similar issue
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]

* igt@sysfs_heartbeat_interval@mixed@bcs0:
- shard-skl: [PASS][121] -> [WARN][122] ([i915#4055])
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@sysfs_heartbeat_interval@[email protected]

* igt@sysfs_heartbeat_interval@mixed@vcs0:
- shard-skl: [PASS][123] -> [FAIL][124] ([i915#1731])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@sysfs_heartbeat_interval@[email protected]

#### Possible fixes ####

* igt@gem_eio@unwedge-stress:
- shard-iclb: [TIMEOUT][125] ([i915#2369] / [i915#2481] / [i915#3070]) -> [PASS][126]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb6/igt@[email protected]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb6/igt@[email protected]

* igt@gem_exec_fair@basic-none@vecs0:
- shard-kbl: [FAIL][127] ([i915#2842]) -> [PASS][128]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@gem_exec_fair@[email protected]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl1/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace@bcs0:
- shard-iclb: [FAIL][129] ([i915#2842]) -> [PASS][130]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb5/igt@gem_exec_fair@[email protected]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@gem_exec_fair@[email protected]

* igt@gem_sync@basic-many-each:
- shard-kbl: [INCOMPLETE][131] ([i915#4274]) -> [PASS][132]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl4/igt@[email protected]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@gem_workarounds@suspend-resume:
- shard

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html

#24 lore raw

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Matthew Auld
== Series Details ==

== Series Details ==

Series: series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
URL : https://patchwork.freedesktop.org/series/95501/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_10688_full -> Patchwork_21264_full
====================================================

Summary
-------

**SUCCESS**

No regressions found.

Possible new issues
-------------------

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

### IGT changes ###

#### Suppressed ####

The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.

* igt@gem_pxp@verify-pxp-key-change-after-suspend-resume:
- {shard-rkl}: NOTRUN -> [SKIP][1] +24 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-rkl-2/igt@[email protected]

Known issues
------------

Here are the changes found in Patchwork_21264_full that come from known issues:

### IGT changes ###

#### Issues hit ####

* igt@feature_discovery@psr2:
- shard-iclb: NOTRUN -> [SKIP][2] ([i915#658]) +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@gem_ctx_isolation@preservation-s3@vecs0:
- shard-skl: [PASS][3] -> [INCOMPLETE][4] ([i915#146] / [i915#198])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl10/igt@gem_ctx_isolation@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl7/igt@gem_ctx_isolation@[email protected]

* igt@gem_ctx_param@set-priority-not-supported:
- shard-tglb: NOTRUN -> [SKIP][5] ([fdo#109314])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@gem_ctx_persistence@smoketest:
- shard-snb: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#1099]) +4 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@gem_eio@in-flight-contexts-immediate:
- shard-skl: [PASS][7] -> [TIMEOUT][8] ([i915#3063])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl5/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@[email protected]

* igt@gem_eio@unwedge-stress:
- shard-snb: NOTRUN -> [FAIL][9] ([i915#3354])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@gem_exec_fair@basic-none@vcs1:
- shard-kbl: [PASS][10] -> [FAIL][11] ([i915#2842])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@gem_exec_fair@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl1/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][12] -> [FAIL][13] ([i915#2842])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb3/igt@gem_exec_fair@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace@vcs1:
- shard-iclb: NOTRUN -> [FAIL][14] ([i915#2842])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-sync@rcs0:
- shard-kbl: [PASS][15] -> [SKIP][16] ([fdo#109271]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl3/igt@gem_exec_fair@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl6/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [PASS][17] -> [FAIL][18] ([i915#2842])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-glk5/igt@gem_exec_fair@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-glk7/igt@gem_exec_fair@[email protected]
- shard-iclb: [PASS][19] -> [FAIL][20] ([i915#2849])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb1/igt@gem_exec_fair@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb7/igt@gem_exec_fair@[email protected]

* igt@gem_exec_flush@basic-batch-kernel-default-cmd:
- shard-tglb: NOTRUN -> [SKIP][21] ([fdo#109313])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@gem_exec_params@no-blt:
- shard-iclb: NOTRUN -> [SKIP][22] ([fdo#109283])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@gem_exec_params@no-vebox:
- shard-tglb: NOTRUN -> [SKIP][23] ([fdo#109283])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@gem_mmap_gtt@cpuset-medium-copy-xy:
- shard-apl: NOTRUN -> [DMESG-WARN][24] ([i915#180] / [i915#203] / [i915#62]) +4 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]

* igt@gem_pread@exhaustion:
- shard-kbl: NOTRUN -> [WARN][25] ([i915#2658])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@gem_pwrite@basic-exhaustion:
- shard-apl: NOTRUN -> [WARN][26] ([i915#2658])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@gem_pxp@dmabuf-shared-protected-dst-is-context-refcounted:
- shard-iclb: NOTRUN -> [SKIP][27] ([i915#4270])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@gem_pxp@verify-pxp-execution-after-suspend-resume:
- shard-tglb: NOTRUN -> [SKIP][28] ([i915#4270]) +1 similar issue
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@gem_sync@basic-many-each:
- shard-apl: NOTRUN -> [INCOMPLETE][29] ([i915#4274])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]

* igt@gem_userptr_blits@dmabuf-sync:
- shard-tglb: NOTRUN -> [SKIP][30] ([i915#3323])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@gem_userptr_blits@dmabuf-unsync:
- shard-tglb: NOTRUN -> [SKIP][31] ([i915#3297])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@gem_userptr_blits@input-checking:
- shard-apl: NOTRUN -> [DMESG-WARN][32] ([i915#3002]) +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][33] ([i915#2724])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@gen3_render_tiledy_blits:
- shard-tglb: NOTRUN -> [SKIP][34] ([fdo#109289]) +1 similar issue
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@gen3_render_tiledy_blits.html

* igt@gen9_exec_parse@batch-without-end:
- shard-iclb: NOTRUN -> [SKIP][35] ([i915#2856])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@gen9_exec_parse@bb-start-cmd:
- shard-tglb: NOTRUN -> [SKIP][36] ([i915#2856]) +2 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@i915_module_load@reload-with-fault-injection:
- shard-skl: [PASS][37] -> [DMESG-WARN][38] ([i915#1982]) +2 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl6/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl4/igt@[email protected]

* igt@i915_pm_dc@dc6-dpms:
- shard-iclb: [PASS][39] -> [FAIL][40] ([i915#454])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb7/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@i915_pm_dc@dc9-dpms:
- shard-iclb: [PASS][41] -> [FAIL][42] ([i915#4275])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb5/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@[email protected]

* igt@i915_selftest@live@gt_lrc:
- shard-tglb: NOTRUN -> [DMESG-FAIL][43] ([i915#2373])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@i915_selftest@live@gt_lrc.html

* igt@i915_selftest@live@gt_pm:
- shard-tglb: NOTRUN -> [DMESG-FAIL][44] ([i915#1759] / [i915#2291])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@i915_selftest@live@gt_pm.html

* igt@i915_selftest@live@mman:
- shard-apl: NOTRUN -> [DMESG-WARN][45] ([i915#203]) +33 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@i915_selftest@[email protected]

* igt@i915_suspend@sysfs-reader:
- shard-apl: [PASS][46] -> [DMESG-WARN][47] ([i915#180]) +3 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-apl2/igt@[email protected]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl1/igt@[email protected]

* igt@kms_big_fb@linear-64bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][48] ([fdo#110725] / [fdo#111614])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-kbl: NOTRUN -> [SKIP][49] ([fdo#109271] / [i915#3777])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180:
- shard-apl: NOTRUN -> [DMESG-WARN][50] ([i915#180] / [i915#1982] / [i915#203] / [i915#62])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]

* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-apl: NOTRUN -> [SKIP][51] ([fdo#109271] / [i915#3777])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]

* igt@kms_big_fb@yf-tiled-32bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][52] ([fdo#111615]) +3 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-async-flip:
- shard-iclb: NOTRUN -> [SKIP][53] ([fdo#110723])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-kbl: NOTRUN -> [SKIP][54] ([fdo#109271] / [i915#3886]) +1 similar issue
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html
- shard-skl: NOTRUN -> [SKIP][55] ([fdo#109271] / [i915#3886])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][56] ([fdo#109278] / [i915#3886])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#3886]) +11 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][58] ([i915#3689] / [i915#3886]) +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-missing-ccs-buffer-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][59] ([i915#3689]) +3 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_ccs@pipe-c-missing-ccs-buffer-yf_tiled_ccs.html

* igt@kms_chamelium@dp-hpd:
- shard-skl: NOTRUN -> [SKIP][60] ([fdo#109271] / [fdo#111827])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]

* igt@kms_chamelium@hdmi-mode-timings:
- shard-snb: NOTRUN -> [SKIP][61] ([fdo#109271] / [fdo#111827]) +14 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb7/igt@[email protected]

* igt@kms_color@pipe-d-ctm-0-75:
- shard-iclb: NOTRUN -> [SKIP][62] ([fdo#109278] / [i915#1149])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-iclb: NOTRUN -> [SKIP][63] ([fdo#109284] / [fdo#111827]) +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_color_chamelium@pipe-a-ctm-limited-range:
- shard-apl: NOTRUN -> [SKIP][64] ([fdo#109271] / [fdo#111827]) +23 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]

* igt@kms_color_chamelium@pipe-c-ctm-limited-range:
- shard-kbl: NOTRUN -> [SKIP][65] ([fdo#109271] / [fdo#111827]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_color_chamelium@pipe-d-ctm-green-to-red:
- shard-tglb: NOTRUN -> [SKIP][66] ([fdo#109284] / [fdo#111827]) +6 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_content_protection@atomic-dpms:
- shard-apl: NOTRUN -> [TIMEOUT][67] ([i915#1319])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl6/igt@[email protected]

* igt@kms_content_protection@legacy:
- shard-kbl: NOTRUN -> [TIMEOUT][68] ([i915#1319])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_cursor_crc@pipe-a-cursor-512x512-offscreen:
- shard-iclb: NOTRUN -> [SKIP][69] ([fdo#109278] / [fdo#109279])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [PASS][70] -> [DMESG-WARN][71] ([i915#180]) +3 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl3/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl7/igt@[email protected]

* igt@kms_cursor_crc@pipe-b-cursor-32x10-random:
- shard-kbl: NOTRUN -> [SKIP][72] ([fdo#109271]) +73 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_cursor_crc@pipe-b-cursor-512x170-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][73] ([i915#3359])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@kms_cursor_crc@pipe-b-cursor-512x512-random:
- shard-tglb: NOTRUN -> [SKIP][74] ([fdo#109279] / [i915#3359])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_cursor_crc@pipe-c-cursor-32x32-onscreen:
- shard-tglb: NOTRUN -> [SKIP][75] ([i915#3319])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_cursor_crc@pipe-d-cursor-64x64-rapid-movement:
- shard-iclb: NOTRUN -> [SKIP][76] ([fdo#109278]) +7 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-skl: [PASS][77] -> [FAIL][78] ([i915#2346])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl3/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]

* igt@kms_dp_tiled_display@basic-test-pattern-with-chamelium:
- shard-tglb: NOTRUN -> [SKIP][79] ([i915#3528])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [PASS][80] -> [INCOMPLETE][81] ([i915#180] / [i915#1982])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-apl6/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl8/igt@[email protected]
- shard-tglb: [PASS][82] -> [INCOMPLETE][83] ([i915#456])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb5/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb7/igt@[email protected]

* igt@kms_flip@2x-absolute-wf_vblank:
- shard-tglb: NOTRUN -> [SKIP][84] ([fdo#111825] / [i915#3966])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_flip@2x-absolute-wf_vblank.html

* igt@kms_flip@2x-plain-flip-ts-check@ab-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][85] -> [FAIL][86] ([i915#2122])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-glk4/igt@kms_flip@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-glk6/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-skl: [PASS][87] -> [FAIL][88] ([i915#79])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl9/igt@kms_flip@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl2/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-expired-vblank@a-edp1:
- shard-skl: NOTRUN -> [FAIL][89] ([i915#79])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-suspend@a-edp1:
- shard-tglb: [PASS][90] -> [INCOMPLETE][91] ([i915#2411] / [i915#456])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-tglb5/igt@kms_flip@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb7/igt@kms_flip@[email protected]

* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-blt:
- shard-snb: NOTRUN -> [SKIP][92] ([fdo#109271]) +313 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc:
- shard-iclb: NOTRUN -> [SKIP][93] ([fdo#109280])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-mmap-wc.html

* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite:
- shard-tglb: NOTRUN -> [SKIP][94] ([fdo#111825]) +15 similar issues
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite.html

* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][95] -> [FAIL][96] ([i915#1188])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl5/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl10/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-a-alpha-basic:
- shard-apl: NOTRUN -> [FAIL][97] ([fdo#108145] / [i915#265]) +1 similar issue
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-kbl: NOTRUN -> [FAIL][98] ([i915#265])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][99] ([i915#265])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][100] ([fdo#108145] / [i915#265]) +1 similar issue
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl2/igt@[email protected]

* igt@kms_plane_lowres@pipe-c-tiling-x:
- shard-tglb: NOTRUN -> [SKIP][101] ([i915#3536])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@[email protected]

* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-apl: NOTRUN -> [SKIP][102] ([fdo#109271] / [i915#2733])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html

* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
- shard-kbl: NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#658])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-apl: NOTRUN -> [SKIP][104] ([fdo#109271] / [i915#658]) +4 similar issues
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]

* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [PASS][105] -> [SKIP][106] ([fdo#109441]) +1 similar issue
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb1/igt@kms_psr@psr2_cursor_plane_onoff.html

* igt@kms_psr@psr2_primary_blt:
- shard-tglb: NOTRUN -> [FAIL][107] ([i915#132] / [i915#3467])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@kms_psr@psr2_primary_blt.html

* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: NOTRUN -> [SKIP][108] ([fdo#109441])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@kms_psr@psr2_primary_mmap_cpu.html

* igt@kms_setmode@basic:
- shard-snb: NOTRUN -> [FAIL][109] ([i915#31])
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-snb2/igt@[email protected]

* igt@kms_vblank@pipe-d-wait-idle:
- shard-apl: NOTRUN -> [SKIP][110] ([fdo#109271] / [i915#533]) +2 similar issues
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl7/igt@[email protected]

* igt@kms_writeback@writeback-fb-id:
- shard-apl: NOTRUN -> [SKIP][111] ([fdo#109271] / [i915#2437])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]

* igt@nouveau_crc@pipe-b-ctx-flip-detection:
- shard-tglb: NOTRUN -> [SKIP][112] ([i915#2530]) +1 similar issue
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb6/igt@[email protected]

* igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame:
- shard-apl: NOTRUN -> [SKIP][113] ([fdo#109271]) +255 similar issues
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl2/igt@[email protected]

* igt@nouveau_crc@pipe-d-source-outp-complete:
- shard-skl: NOTRUN -> [SKIP][114] ([fdo#109271]) +17 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl6/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][115] ([fdo#109278] / [i915#2530])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@[email protected]

* igt@perf@polling:
- shard-skl: [PASS][116] -> [FAIL][117] ([i915#1542])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl4/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl5/igt@[email protected]

* igt@prime_nv_api@i915_nv_import_twice:
- shard-iclb: NOTRUN -> [SKIP][118] ([fdo#109291]) +2 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb3/igt@prime_nv_api@i915_nv_import_twice.html

* igt@prime_nv_api@i915_self_import_to_different_fd:
- shard-tglb: NOTRUN -> [SKIP][119] ([fdo#109291]) +2 similar issues
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-tglb5/igt@prime_nv_api@i915_self_import_to_different_fd.html

* igt@sysfs_clients@recycle-many:
- shard-apl: NOTRUN -> [SKIP][120] ([fdo#109271] / [i915#2994]) +1 similar issue
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-apl3/igt@[email protected]

* igt@sysfs_heartbeat_interval@mixed@bcs0:
- shard-skl: [PASS][121] -> [WARN][122] ([i915#4055])
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@sysfs_heartbeat_interval@[email protected]

* igt@sysfs_heartbeat_interval@mixed@vcs0:
- shard-skl: [PASS][123] -> [FAIL][124] ([i915#1731])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-skl3/igt@sysfs_heartbeat_interval@[email protected]

#### Possible fixes ####

* igt@gem_eio@unwedge-stress:
- shard-iclb: [TIMEOUT][125] ([i915#2369] / [i915#2481] / [i915#3070]) -> [PASS][126]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb6/igt@[email protected]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb6/igt@[email protected]

* igt@gem_exec_fair@basic-none@vecs0:
- shard-kbl: [FAIL][127] ([i915#2842]) -> [PASS][128]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@gem_exec_fair@[email protected]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl1/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace@bcs0:
- shard-iclb: [FAIL][129] ([i915#2842]) -> [PASS][130]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-iclb5/igt@gem_exec_fair@[email protected]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-iclb2/igt@gem_exec_fair@[email protected]

* igt@gem_sync@basic-many-each:
- shard-kbl: [INCOMPLETE][131] ([i915#4274]) -> [PASS][132]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl4/igt@[email protected]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl4/igt@[email protected]

* igt@gem_workarounds@suspend-resume:
- shard-kbl: [DMESG-WARN][133] ([i915#180]) -> [PASS][134] +1 similar issue
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10688/shard-kbl6/igt@[email protected]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-kbl7/igt@[email protected]

* igt@i915_pm_dc@d

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.html

#18 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

In reply to Tvrtko Ursulin

-----Original Message-----
From: Tvrtko Ursulin <[email protected]>
Sent: Thursday, October 7, 2021 6:41 AM
To: Christian König <[email protected]>; [email protected]
Cc: Vudum, Lakshminarayana <[email protected]>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Quoted 119 lines · Christian König

Am 07.10.21 um 12:51 schrieb Tvrtko Ursulin:

Quoted 110 lines · Christian König
Quoted 53 lines

Am 07.10.21 um 11:15 schrieb Tvrtko Ursulin:

Quoted 52 lines

Hi,

Quoted 49 lines · Patchwork

*Patch Details*
*Series:*    series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:*    https://patchwork.freedesktop.org/series/95501/
<https://patchwork.freedesktop.org/series/95501/>
*State:*    failure
*Details:*
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.htm
l
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.ht
ml>

  CI Bug Log - changes from CI_DRM_10688_full ->
Patchwork_21264_full

    Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

    Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

      IGT changes

        Possible regressions

  *

    igt@gem_sync@basic-many-each:

      o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-ap
l7/igt@[email protected]>

Quoted 52 lines
Quoted 2 lines

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

Probably the later. I'm going to take a look.

Thanks for the notice,
Christian.

Quoted 44 lines

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each <1> [188.935462] BUG: kernel NULL pointer dereference, address:
0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode <1>

[188.935495] #PF: error_code(0x0002) - not-present page <6> 
[188.935504] PGD 0 P4D 0 <4> [188.935512] Oops: 0002 [#1] PREEMPT 

SMP NOPTI <4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1 <4> [188.935535] Hardware name:  /NUC6CAYB, BIOS
AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018 <4> [188.935546] RIP:
0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01
41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS:
00010202 <4> [188.935593] RAX: 0000000000000000 RBX:
00000000ffffffff RCX:
0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI:
ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09:
00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12:
ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15:
0000000000000000
<4> [188.935643] FS:  00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000 <4> [188.935655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4> [188.935665]
CR2: 0000000000000010 CR3: 000000012d0a4000 CR4:
00000000003506e0
<4> [188.935676] Call Trace:
<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915] <4>

[188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915] <4> 
[188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915] <4> 
[188.936533]  drm_ioctl_kernel+0xae/0x140 <4> [188.936546]  
drm_ioctl+0x201/0x3d0 <4> [188.936555]  ? 
i915_gem_object_wait+0x410/0x410 [i915] <4> [188.936820]  ? 
__fget_files+0xc2/0x1c0 <4> [188.936830]  ? __fget_files+0xda/0x1c0 
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0 <4> [188.936848]  
do_syscall_64+0x3a/0xb0 <4> [188.936859] 
entry_SYSCALL_64_after_hwframe+0x44/0xae

FWIW if you disassemble the code it seems to be crashing in:

Quoted 7 lines

  (*shared)[(*shared_count)++] = fence; // mov %r14, (%rdx, %rax, 8)

RDX is *shared, RAX is *shared_count, RCX is *shared_count++ (for the next iteration. R13 is share and R12 shared_count.

That *shared can contain 0000000000000010 makes no sense to me. At least yet. :)

Quoted 7 lines

Yeah, me neither. I've gone over the whole code multiple time now and absolutely don't get what's happening here.

Adding some more selftests didn't helped either. As far as I can see the code works as intended.

Do we have any other reports of crashes?

Yes, sporadic but present across different platforms since the change went it:
https://intel-gfx-ci.01.org/tree/drm-tip/igt@[email protected].
So issue is probably real.

Did not find any other tests failing with the same signature. Lakshmi are you perhaps able to search for the same or similar signature across the whole set of recent results?

[Lakshmi] Both the regressions failures are new. I filed below issues and reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/4275
igt@i915_pm_dc@dc9-dpms - fail - Failed assertion: dc9_wait_entry(data->debugfs_fd, dc_target, prev_dc, 3000), DC9 state is not achieved

https://gitlab.freedesktop.org/drm/intel/-/issues/4274
igt@gem_sync@basic-many-each - incomplete - RIP: 0010:dma_resv_get_fences

Regards,

Tvrtko

#19 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Quoted 136 lines · Lakshminarayana

-----Original Message-----
From: Tvrtko Ursulin <[email protected]>
Sent: Thursday, October 7, 2021 6:41 AM
To: Christian König <[email protected]>; [email protected]
Cc: Vudum, Lakshminarayana <[email protected]>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Quoted 119 lines · Christian König

Am 07.10.21 um 12:51 schrieb Tvrtko Ursulin:

Quoted 110 lines · Christian König
Quoted 53 lines

Am 07.10.21 um 11:15 schrieb Tvrtko Ursulin:

Quoted 52 lines

Hi,

Quoted 49 lines · Patchwork

*Patch Details*
*Series:*    series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:*    https://patchwork.freedesktop.org/series/95501/
<https://patchwork.freedesktop.org/series/95501/>
*State:*    failure
*Details:*
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.htm
l
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.ht
ml>

  CI Bug Log - changes from CI_DRM_10688_full ->
Patchwork_21264_full

    Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

    Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

      IGT changes

        Possible regressions

  *

    igt@gem_sync@basic-many-each:

      o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-ap
l7/igt@[email protected]>

Quoted 52 lines
Quoted 2 lines

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

Probably the later. I'm going to take a look.

Thanks for the notice,
Christian.

Quoted 44 lines

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each <1> [188.935462] BUG: kernel NULL pointer dereference, address:
0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode <1>

[188.935495] #PF: error_code(0x0002) - not-present page <6>
[188.935504] PGD 0 P4D 0 <4> [188.935512] Oops: 0002 [#1] PREEMPT

SMP NOPTI <4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1 <4> [188.935535] Hardware name:  /NUC6CAYB, BIOS
AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018 <4> [188.935546] RIP:
0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01
41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS:
00010202 <4> [188.935593] RAX: 0000000000000000 RBX:
00000000ffffffff RCX:
0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI:
ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09:
00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12:
ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15:
0000000000000000
<4> [188.935643] FS:  00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000 <4> [188.935655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4> [188.935665]
CR2: 0000000000000010 CR3: 000000012d0a4000 CR4:
00000000003506e0
<4> [188.935676] Call Trace:
<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915] <4>

[188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915] <4>
[188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915] <4>
[188.936533]  drm_ioctl_kernel+0xae/0x140 <4> [188.936546]
drm_ioctl+0x201/0x3d0 <4> [188.936555]  ?
i915_gem_object_wait+0x410/0x410 [i915] <4> [188.936820]  ?
__fget_files+0xc2/0x1c0 <4> [188.936830]  ? __fget_files+0xda/0x1c0
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0 <4> [188.936848]
do_syscall_64+0x3a/0xb0 <4> [188.936859]
entry_SYSCALL_64_after_hwframe+0x44/0xae

FWIW if you disassemble the code it seems to be crashing in:

Quoted 7 lines

  (*shared)[(*shared_count)++] = fence; // mov %r14, (%rdx, %rax, 8)

RDX is *shared, RAX is *shared_count, RCX is *shared_count++ (for the next iteration. R13 is share and R12 shared_count.

That *shared can contain 0000000000000010 makes no sense to me. At least yet. :)

Quoted 7 lines

Yeah, me neither. I've gone over the whole code multiple time now and absolutely don't get what's happening here.

Adding some more selftests didn't helped either. As far as I can see the code works as intended.

Do we have any other reports of crashes?

Quoted 7 lines

Yes, sporadic but present across different platforms since the change went it:
https://intel-gfx-ci.01.org/tree/drm-tip/igt@[email protected].
So issue is probably real.

Did not find any other tests failing with the same signature. Lakshmi are you perhaps able to search for the same or similar signature across the whole set of recent results?

[Lakshmi] Both the regressions failures are new. I filed below issues and reported.

Thanks Lakshmi!

Christian, maybe revert for now since it looks tricky to figure out? I at least couldn't spent much time looking at it today. Or try to find a third set of eyes to look at it quickly in case we are not seeing something.

Looks like a good selftest will be needed here for robustness. Including threads to trigger restarts and external manipulation to hit the refcount zero.

Regards,

Tvrtko

Quoted 10 lines

https://gitlab.freedesktop.org/drm/intel/-/issues/4275
igt@i915_pm_dc@dc9-dpms - fail - Failed assertion: dc9_wait_entry(data->debugfs_fd, dc_target, prev_dc, 3000), DC9 state is not achieved

https://gitlab.freedesktop.org/drm/intel/-/issues/4274
igt@gem_sync@basic-many-each - incomplete - RIP: 0010:dma_resv_get_fences

Regards,

Tvrtko

#20 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Am 07.10.21 um 17:53 schrieb Tvrtko Ursulin:

Quoted 145 lines · Lakshminarayana
Quoted 143 lines

-----Original Message-----
From: Tvrtko Ursulin <[email protected]>
Sent: Thursday, October 7, 2021 6:41 AM
To: Christian König <[email protected]>; [email protected]
Cc: Vudum, Lakshminarayana <[email protected]>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Quoted 119 lines · Christian König

Am 07.10.21 um 12:51 schrieb Tvrtko Ursulin:

Quoted 110 lines · Christian König
Quoted 53 lines

Am 07.10.21 um 11:15 schrieb Tvrtko Ursulin:

Quoted 52 lines

Hi,

Quoted 49 lines · Patchwork

*Patch Details*
*Series:*    series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:* https://patchwork.freedesktop.org/series/95501/
<https://patchwork.freedesktop.org/series/95501/>
*State:*    failure
*Details:*
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.htm
l
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.ht
ml>

   CI Bug Log - changes from CI_DRM_10688_full ->
Patchwork_21264_full

     Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

     Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

       IGT changes

         Possible regressions

   *

     igt@gem_sync@basic-many-each:

       o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-ap
l7/igt@[email protected]>

Quoted 52 lines
Quoted 2 lines

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

Probably the later. I'm going to take a look.

Thanks for the notice,
Christian.

Quoted 44 lines

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each <1> [188.935462] BUG: kernel NULL pointer dereference, address:
0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode <1>

[188.935495] #PF: error_code(0x0002) - not-present page <6>
[188.935504] PGD 0 P4D 0 <4> [188.935512] Oops: 0002 [#1] PREEMPT

SMP NOPTI <4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1 <4> [188.935535] Hardware name:  /NUC6CAYB, BIOS
AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018 <4> [188.935546] RIP:
0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01
41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS:
00010202 <4> [188.935593] RAX: 0000000000000000 RBX:
00000000ffffffff RCX:
0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI:
ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09:
00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12:
ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15:
0000000000000000
<4> [188.935643] FS:  00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000 <4> [188.935655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4> [188.935665]
CR2: 0000000000000010 CR3: 000000012d0a4000 CR4:
00000000003506e0
<4> [188.935676] Call Trace:
<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915] <4>

[188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915] <4>
[188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915] <4>
[188.936533]  drm_ioctl_kernel+0xae/0x140 <4> [188.936546]
drm_ioctl+0x201/0x3d0 <4> [188.936555]  ?
i915_gem_object_wait+0x410/0x410 [i915] <4> [188.936820]  ?
__fget_files+0xc2/0x1c0 <4> [188.936830]  ? __fget_files+0xda/0x1c0
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0 <4> [188.936848]
do_syscall_64+0x3a/0xb0 <4> [188.936859]
entry_SYSCALL_64_after_hwframe+0x44/0xae

FWIW if you disassemble the code it seems to be crashing in:

Quoted 7 lines

   (*shared)[(*shared_count)++] = fence; // mov %r14, (%rdx, %rax, 8)

RDX is *shared, RAX is *shared_count, RCX is *shared_count++ (for the next iteration. R13 is share and R12 shared_count.

That *shared can contain 0000000000000010 makes no sense to me. At least yet. :)

Quoted 7 lines

Yeah, me neither. I've gone over the whole code multiple time now and absolutely don't get what's happening here.

Adding some more selftests didn't helped either. As far as I can see the code works as intended.

Do we have any other reports of crashes?

Yes, sporadic but present across different platforms since the change went it:
https://intel-gfx-ci.01.org/tree/drm-tip/igt@[email protected].

So issue is probably real.

Did not find any other tests failing with the same signature. Lakshmi are you perhaps able to search for the same or similar signature across the whole set of recent results?

Quoted 8 lines
Quoted 1 line

[Lakshmi] Both the regressions failures are new. I filed below issues and reported.

Thanks Lakshmi!

Christian, maybe revert for now since it looks tricky to figure out? I at least couldn't spent much time looking at it today. Or try to find a third set of eyes to look at it quickly in case we are not seeing something.

Looks like a good selftest will be needed here for robustness. Including threads to trigger restarts and external manipulation to hit the refcount zero.

Yeah, agree. Already working on that.

Going to send out the revert for dma_resv_get_fences() tomorrow.

Christian.

Quoted 15 lines

Regards,

Tvrtko

Quoted 10 lines

https://gitlab.freedesktop.org/drm/intel/-/issues/4275
igt@i915_pm_dc@dc9-dpms - fail - Failed assertion: dc9_wait_entry(data->debugfs_fd, dc_target, prev_dc, 3000), DC9 state is not achieved

https://gitlab.freedesktop.org/drm/intel/-/issues/4274
igt@gem_sync@basic-many-each - incomplete - RIP: 0010:dma_resv_get_fences

Regards,

Tvrtko

#21 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Quoted 151 lines · Christian König

Am 07.10.21 um 17:53 schrieb Tvrtko Ursulin:

Quoted 150 lines · Lakshminarayana
Quoted 136 lines

-----Original Message-----
From: Tvrtko Ursulin <[email protected]>
Sent: Thursday, October 7, 2021 6:41 AM
To: Christian König <[email protected]>; [email protected]
Cc: Vudum, Lakshminarayana <[email protected]>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Quoted 119 lines · Christian König

Am 07.10.21 um 12:51 schrieb Tvrtko Ursulin:

Quoted 110 lines · Christian König
Quoted 53 lines

Am 07.10.21 um 11:15 schrieb Tvrtko Ursulin:

Quoted 52 lines

Hi,

Quoted 49 lines · Patchwork

*Patch Details*
*Series:*    series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:* https://patchwork.freedesktop.org/series/95501/
<https://patchwork.freedesktop.org/series/95501/>
*State:*    failure
*Details:*
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.htm
l
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.ht
ml>

   CI Bug Log - changes from CI_DRM_10688_full ->
Patchwork_21264_full

     Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

     Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

       IGT changes

         Possible regressions

   *

     igt@gem_sync@basic-many-each:

       o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-ap
l7/igt@[email protected]>

Quoted 52 lines
Quoted 2 lines

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

Probably the later. I'm going to take a look.

Thanks for the notice,
Christian.

Quoted 44 lines

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each <1> [188.935462] BUG: kernel NULL pointer dereference, address:
0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode <1>

[188.935495] #PF: error_code(0x0002) - not-present page <6>
[188.935504] PGD 0 P4D 0 <4> [188.935512] Oops: 0002 [#1] PREEMPT

SMP NOPTI <4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1 <4> [188.935535] Hardware name:  /NUC6CAYB, BIOS
AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018 <4> [188.935546] RIP:
0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01
41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS:
00010202 <4> [188.935593] RAX: 0000000000000000 RBX:
00000000ffffffff RCX:
0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI:
ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09:
00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12:
ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15:
0000000000000000
<4> [188.935643] FS:  00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000 <4> [188.935655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4> [188.935665]
CR2: 0000000000000010 CR3: 000000012d0a4000 CR4:
00000000003506e0
<4> [188.935676] Call Trace:
<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915] <4>

[188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915] <4>
[188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915] <4>
[188.936533]  drm_ioctl_kernel+0xae/0x140 <4> [188.936546]
drm_ioctl+0x201/0x3d0 <4> [188.936555]  ?
i915_gem_object_wait+0x410/0x410 [i915] <4> [188.936820]  ?
__fget_files+0xc2/0x1c0 <4> [188.936830]  ? __fget_files+0xda/0x1c0
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0 <4> [188.936848]
do_syscall_64+0x3a/0xb0 <4> [188.936859]
entry_SYSCALL_64_after_hwframe+0x44/0xae

FWIW if you disassemble the code it seems to be crashing in:

Quoted 7 lines

   (*shared)[(*shared_count)++] = fence; // mov %r14, (%rdx, %rax, 8)

RDX is *shared, RAX is *shared_count, RCX is *shared_count++ (for the next iteration. R13 is share and R12 shared_count.

That *shared can contain 0000000000000010 makes no sense to me. At least yet. :)

Quoted 7 lines

Yeah, me neither. I've gone over the whole code multiple time now and absolutely don't get what's happening here.

Adding some more selftests didn't helped either. As far as I can see the code works as intended.

Do we have any other reports of crashes?

Quoted 8 lines

Yes, sporadic but present across different platforms since the change went it:
https://intel-gfx-ci.01.org/tree/drm-tip/igt@[email protected].

So issue is probably real.

Did not find any other tests failing with the same signature. Lakshmi are you perhaps able to search for the same or similar signature across the whole set of recent results?

[Lakshmi] Both the regressions failures are new. I filed below issues and reported.

Thanks Lakshmi!

Quoted 7 lines
Quoted 3 lines

Christian, maybe revert for now since it looks tricky to figure out? I at least couldn't spent much time looking at it today. Or try to find a third set of eyes to look at it quickly in case we are not seeing something.

Looks like a good selftest will be needed here for robustness. Including threads to trigger restarts and external manipulation to hit the refcount zero.

Yeah, agree. Already working on that.

Going to send out the revert for dma_resv_get_fences() tomorrow.

Looks like the issue is actually in the unlocked iterator.

What happens in practice when it crashes is that the fence count in the shared fences object is zero, which means no space gets allocated in dma_resv_get_fences. But clearly shared_count was not zero in dma_resv_iter_walk_unlocked, otherwise the loop in dma_resv_get_fences wouldn't run.

I suspect it is not safe to drop the RCU lock having peeking at the dma_resv_shared_list.

Regards,

Tvrtko

#22 lore raw

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Quoted 159 lines · Tvrtko Ursulin
Quoted 157 lines · Christian König

Am 07.10.21 um 17:53 schrieb Tvrtko Ursulin:

Quoted 145 lines · Lakshminarayana
Quoted 143 lines

-----Original Message-----
From: Tvrtko Ursulin <[email protected]>
Sent: Thursday, October 7, 2021 6:41 AM
To: Christian König <[email protected]>; [email protected]
Cc: Vudum, Lakshminarayana <[email protected]>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils

Quoted 119 lines · Christian König

Am 07.10.21 um 12:51 schrieb Tvrtko Ursulin:

Quoted 110 lines · Christian König
Quoted 53 lines

Am 07.10.21 um 11:15 schrieb Tvrtko Ursulin:

Quoted 52 lines

Hi,

Quoted 49 lines · Patchwork

*Patch Details*
*Series:*    series starting with [v7,1/8] drm/i915/gem: Break out some shmem backend utils
*URL:* https://patchwork.freedesktop.org/series/95501/
<https://patchwork.freedesktop.org/series/95501/>
*State:*    failure
*Details:*
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.htm
l
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/index.ht
ml>

   CI Bug Log - changes from CI_DRM_10688_full ->
Patchwork_21264_full

     Summary

*FAILURE*

Serious unknown changes coming with Patchwork_21264_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_21264_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

     Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21264_full:

       IGT changes

         Possible regressions

   *

     igt@gem_sync@basic-many-each:

       o shard-apl: NOTRUN -> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21264/shard-ap
l7/igt@[email protected]>

Quoted 52 lines
Quoted 2 lines

Something still fishy in the unlocked iterator? Or dma_resv_get_fences using it?

Probably the later. I'm going to take a look.

Thanks for the notice,
Christian.

Quoted 44 lines

<6> [187.551235] [IGT] gem_sync: starting subtest basic-many-each <1> [188.935462] BUG: kernel NULL pointer dereference, address:
0000000000000010
<1> [188.935485] #PF: supervisor write access in kernel mode <1>

[188.935495] #PF: error_code(0x0002) - not-present page <6>
[188.935504] PGD 0 P4D 0 <4> [188.935512] Oops: 0002 [#1] PREEMPT

SMP NOPTI <4> [188.935521] CPU: 2 PID: 1467 Comm: gem_sync Not tainted 5.15.0-rc4-CI-Patchwork_21264+ #1 <4> [188.935535] Hardware name:  /NUC6CAYB, BIOS
AYAPLCEL.86A.0049.2018.0508.1356 05/08/2018 <4> [188.935546] RIP:
0010:dma_resv_get_fences+0x116/0x2d0
<4> [188.935560] Code: 10 85 c0 7f c9 be 03 00 00 00 e8 15 8b df ff eb bd e8 8e c6 ff ff eb b6 41 8b 04 24 49 8b 55 00 48 89 e7 8d 48 01
41 89 0c 24 <4c> 89 34 c2 e8 41 f2 ff ff 49 89 c6 48 85 c0 75 8c 48 8b 44 24 10 <4> [188.935583] RSP: 0018:ffffc900011dbcc8 EFLAGS:
00010202 <4> [188.935593] RAX: 0000000000000000 RBX:
00000000ffffffff RCX:
0000000000000001
<4> [188.935603] RDX: 0000000000000010 RSI: ffffffff822e343c RDI:
ffffc900011dbcc8
<4> [188.935613] RBP: ffffc900011dbd48 R08: ffff88812d255bb8 R09:
00000000fffffffe
<4> [188.935623] R10: 0000000000000001 R11: 0000000000000000 R12:
ffffc900011dbd44
<4> [188.935633] R13: ffffc900011dbd50 R14: ffff888113d29cc0 R15:
0000000000000000
<4> [188.935643] FS:  00007f68d17e9700(0000) GS:ffff888277900000(0000) knlGS:0000000000000000 <4> [188.935655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4> [188.935665]
CR2: 0000000000000010 CR3: 000000012d0a4000 CR4:
00000000003506e0
<4> [188.935676] Call Trace:
<4> [188.935685]  i915_gem_object_wait+0x1ff/0x410 [i915] <4>

[188.935988]  i915_gem_wait_ioctl+0xf2/0x2a0 [i915] <4>
[188.936272]  ? i915_gem_object_wait+0x410/0x410 [i915] <4>
[188.936533]  drm_ioctl_kernel+0xae/0x140 <4> [188.936546]
drm_ioctl+0x201/0x3d0 <4> [188.936555]  ?
i915_gem_object_wait+0x410/0x410 [i915] <4> [188.936820]  ?
__fget_files+0xc2/0x1c0 <4> [188.936830]  ? __fget_files+0xda/0x1c0
<4> [188.936839]  __x64_sys_ioctl+0x6d/0xa0 <4> [188.936848]
do_syscall_64+0x3a/0xb0 <4> [188.936859]
entry_SYSCALL_64_after_hwframe+0x44/0xae

FWIW if you disassemble the code it seems to be crashing in:

Quoted 7 lines

   (*shared)[(*shared_count)++] = fence; // mov %r14, (%rdx, %rax, 8)

RDX is *shared, RAX is *shared_count, RCX is *shared_count++ (for the next iteration. R13 is share and R12 shared_count.

That *shared can contain 0000000000000010 makes no sense to me. At least yet. :)

Quoted 7 lines

Yeah, me neither. I've gone over the whole code multiple time now and absolutely don't get what's happening here.

Adding some more selftests didn't helped either. As far as I can see the code works as intended.

Do we have any other reports of crashes?

Yes, sporadic but present across different platforms since the change went it:
https://intel-gfx-ci.01.org/tree/drm-tip/igt@[email protected].

So issue is probably real.

Did not find any other tests failing with the same signature. Lakshmi are you perhaps able to search for the same or similar signature across the whole set of recent results?

Quoted 8 lines
Quoted 1 line

[Lakshmi] Both the regressions failures are new. I filed below issues and reported.

Thanks Lakshmi!

Christian, maybe revert for now since it looks tricky to figure out? I at least couldn't spent much time looking at it today. Or try to find a third set of eyes to look at it quickly in case we are not seeing something.

Looks like a good selftest will be needed here for robustness. Including threads to trigger restarts and external manipulation to hit the refcount zero.

Yeah, agree. Already working on that.

Quoted 7 lines
Quoted 1 line

Going to send out the revert for dma_resv_get_fences() tomorrow.

Looks like the issue is actually in the unlocked iterator.

What happens in practice when it crashes is that the fence count in the shared fences object is zero, which means no space gets allocated in dma_resv_get_fences. But clearly shared_count was not zero in dma_resv_iter_walk_unlocked, otherwise the loop in dma_resv_get_fences wouldn't run.

I suspect it is not safe to drop the RCU lock having peeking at the dma_resv_shared_list.

It may work to cache cursor.fences->shared_count into cursor.shared_count at restart time, so dma_resv_get_fences could use it to guarantee consistent view and allocated space correctly. Then dma_resv_iter_next_unlocked would notice restart and cause unwind.

Regards,

Tvrtko