Skip to contentSkip to conversation

msm: recovery and mapping updates

PATCH In review Rob Clark 4 participants 28 messages Jun 30, 2025 – Jul 2, 2025 Arm Qualcomm mailing list

lore
Share & tools
lore

Rob Clark

author
#0 lore raw

cover msm: recovery and mapping updates

From: Rob Clark <[email protected]>

Mostly updates to address flakes, and updates related to newer kernels. Plus a few additional sub-tests.

Rob Clark (9):
drm/recovery: Wait for devcore to become available drm/recovery: add iova-fault-stress test msm/mapping: update for sparse msm/mapping: Handle BO names with spaces msm/mapping: Add additional subtests msm/mapping: Wait for devcore to become available msm/mapping: Handle larger gmem file size msm/mapping: Add wait for stall-on-fault to re-arm msm/mapping: Free devcore

 tests/msm/msm_mapping.c  | 90 +++++++++++++++++++++++++++++++++++-----
 tests/msm/msm_recovery.c | 39 ++++++++++++-----
 2 files changed, 109 insertions(+), 20 deletions(-)
Signature · 1 line
2.50.0
author
#1 lore raw

PATCH 1/9 drm/recovery: Wait for devcore to become available

From: Rob Clark <[email protected]>

The devcore could take some time to show up, so add a igt_wait() with timeout so we don't fail the test if the devcore is not immediately available.

This addresses a source of flakeyness.

---
 tests/msm/msm_recovery.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
tests/msm/msm_recovery.c +6 -2
index fbe26e687ed3..433392079bd4 100644
@@ -44,8 +44,12 @@ read_and_clear_devcore(void)
 	glob_t glob_buf = {0};
 	int ret, fd;
 
-	ret = glob("/sys/class/devcoredump/devcd*/data", GLOB_NOSORT, NULL, &glob_buf);
-	if ((ret == GLOB_NOMATCH) || !glob_buf.gl_pathc)
+	/* The devcore shows up asynchronously, so it might not be
+	 * immediately available:
+	 */
+	if (!igt_wait(glob("/sys/class/devcoredump/devcd*/data",
+			   GLOB_NOSORT, NULL, &glob_buf) != GLOB_NOMATCH,
+		      1000, 100))
 		return;
 
 	fd = open(glob_buf.gl_pathv[0], O_RDWR);
Signature · 1 line
2.50.0
#2 lore raw

Re: [PATCH igt 1/9] drm/recovery: Wait for devcore to become available

Hi Rob,

Quoted 1 line · Rob Clark

From: Rob Clark <[email protected]>

Please change subject, it is now:
[PATCH igt 1/9] drm/recovery: Wait for devcore to become available

and it should be:
[PATCH igt 1/9] tests/msm/msm_recovery: Wait for devcore to become available

or little shorter:
[PATCH igt 1/9] tests/msm/msm_recovery: Wait for devcore

After a resend I will ack it, I have also few nits for other patches.

Regards,
Kamil

Quoted 34 lines

The devcore could take some time to show up, so add a igt_wait() with timeout so we don't fail the test if the devcore is not immediately available.

This addresses a source of flakeyness.

---
 tests/msm/msm_recovery.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
tests/msm/msm_recovery.c +6 -2
index fbe26e687ed3..433392079bd4 100644
@@ -44,8 +44,12 @@ read_and_clear_devcore(void)
 	glob_t glob_buf = {0};
 	int ret, fd;
 
-	ret = glob("/sys/class/devcoredump/devcd*/data", GLOB_NOSORT, NULL, &glob_buf);
-	if ((ret == GLOB_NOMATCH) || !glob_buf.gl_pathc)
+	/* The devcore shows up asynchronously, so it might not be
+	 * immediately available:
+	 */
+	if (!igt_wait(glob("/sys/class/devcoredump/devcd*/data",
+			   GLOB_NOSORT, NULL, &glob_buf) != GLOB_NOMATCH,
+		      1000, 100))
 		return;
 
 	fd = open(glob_buf.gl_pathv[0], O_RDWR);
Signature · 1 line
2.50.0
author
#3 lore raw

PATCH 2/9 drm/recovery: add iova-fault-stress test

In reply to Rob Clark

From: Rob Clark <[email protected]>

Add a test which triggers many faults to test robustness.

---
 tests/msm/msm_recovery.c | 31 +++++++++++++++++++++++--------
 1 file changed, 23 insertions(+), 8 deletions(-)
tests/msm/msm_recovery.c +23 -8
index 433392079bd4..8a83a6f24c41 100644
@@ -195,6 +195,23 @@ do_parallel_test(struct msm_pipe *pipe, int child)
 	igt_msm_cmd_free(cmd);
 }
 
+static void
+do_fault_test(struct msm_pipe *pipe, bool stress)
+{
+	struct msm_cmd *cmd =
+		igt_msm_cmd_new(pipe, 0x10000);
+	unsigned cnt = stress ? 0x10000/16 : 1;
+
+	for (unsigned i = 0; i < cnt; i++) {
+		msm_cmd_pkt7(cmd, CP_MEM_WRITE, 3);
+		msm_cmd_emit(cmd, 0xdeaddead);           /* ADDR_LO */
+		msm_cmd_emit(cmd, 0x1);                  /* ADDR_HI */
+		msm_cmd_emit(cmd, 0x123);                /* VAL */
+	}
+
+	igt_wait_and_close(igt_msm_cmd_submit(cmd));
+}
+
 /*
  * Tests for drm/msm hangcheck, recovery, and fault handling
  */
@@ -242,18 +259,16 @@ igt_main
 
 	igt_describe("Test iova fault handling");
 	igt_subtest("iova-fault") {
-		struct msm_cmd *cmd;
-
 		igt_require(dev->gen >= 6);
 
-		cmd = igt_msm_cmd_new(pipe, 0x1000);
+		do_fault_test(pipe, false);
+	}
 
-		msm_cmd_pkt7(cmd, CP_MEM_WRITE, 3);
-		msm_cmd_emit(cmd, 0xdeaddead);           /* ADDR_LO */
-		msm_cmd_emit(cmd, 0x1);                  /* ADDR_HI */
-		msm_cmd_emit(cmd, 0x123);                /* VAL */
+	igt_describe("Test iova fault handling (stress)");
+	igt_subtest("iova-fault-stress") {
+		igt_require(dev->gen >= 6);
 
-		igt_wait_and_close(igt_msm_cmd_submit(cmd));
+		do_fault_test(pipe, true);
 	}
 
 	igt_fixture {
Signature · 1 line
2.50.0
#4 lore raw

Re: [PATCH igt 2/9] drm/recovery: add iova-fault-stress test

Hi Rob,

Quoted 1 line · Rob Clark

From: Rob Clark <[email protected]>

This 'From: ' do no match your s-o-b below, please fix it.

Please run checkpatch.pl from Linux kernel on your patches. Few helpfull options could be found in CONTRIBUTING.md

Also improve subject to:
[PATCH igt 2/9] tests/msm/msm_recovery: add iova-fault-stress test

Quoted 13 lines

Add a test which triggers many faults to test robustness.

---
 tests/msm/msm_recovery.c | 31 +++++++++++++++++++++++--------
 1 file changed, 23 insertions(+), 8 deletions(-)
tests/msm/msm_recovery.c +0 -0
index 433392079bd4..8a83a6f24c41 100644

tests/msm/msm_recovery.c do_parallel_test(struct msm_pipe *pipe, int child) · line 202

Quoted 8 lines
tests/msm/msm_recovery.c +5 -0
@@ -195,6 +195,23 @@ do_parallel_test(struct msm_pipe *pipe, int child)
 	igt_msm_cmd_free(cmd);
 }
 
+static void
+do_fault_test(struct msm_pipe *pipe, bool stress)
+{
+	struct msm_cmd *cmd =
+		igt_msm_cmd_new(pipe, 0x10000);

Why not in one line? Imho this is better:

	struct msm_cmd *cmd = igt_msm_cmd_new(pipe, 0x10000);

tests/msm/msm_recovery.c do_parallel_test(struct msm_pipe *pipe, int child) · line 203

Quoted 1 line
tests/msm/msm_recovery.c +1 -0
+	unsigned cnt = stress ? 0x10000/16 : 1;

Use 'unsigned int' here, also

Place space around '/', also make 0x10000 a const or define it.

For example:

	const unsigned int f_cnt = 0x10000;
	struct msm_cmd *cmd = igt_msm_cmd_new(pipe, f_cnt);
	unsigned int cnt = stress ? f_cnt / 16 : 1;

tests/msm/msm_recovery.c do_parallel_test(struct msm_pipe *pipe, int child) · line 205

Quoted 2 lines
tests/msm/msm_recovery.c +2 -0
+
+	for (unsigned i = 0; i < cnt; i++) {

Use 'unsigned int' here:

	for (unsigned int i = 0; i < cnt; i++) {

Regards,
Kamil

Quoted 40 lines
tests/msm/msm_recovery.c +15 -8
+		msm_cmd_pkt7(cmd, CP_MEM_WRITE, 3);
+		msm_cmd_emit(cmd, 0xdeaddead);           /* ADDR_LO */
+		msm_cmd_emit(cmd, 0x1);                  /* ADDR_HI */
+		msm_cmd_emit(cmd, 0x123);                /* VAL */
+	}
+
+	igt_wait_and_close(igt_msm_cmd_submit(cmd));
+}
+
 /*
  * Tests for drm/msm hangcheck, recovery, and fault handling
  */
@@ -242,18 +259,16 @@ igt_main
 
 	igt_describe("Test iova fault handling");
 	igt_subtest("iova-fault") {
-		struct msm_cmd *cmd;
-
 		igt_require(dev->gen >= 6);
 
-		cmd = igt_msm_cmd_new(pipe, 0x1000);
+		do_fault_test(pipe, false);
+	}
 
-		msm_cmd_pkt7(cmd, CP_MEM_WRITE, 3);
-		msm_cmd_emit(cmd, 0xdeaddead);           /* ADDR_LO */
-		msm_cmd_emit(cmd, 0x1);                  /* ADDR_HI */
-		msm_cmd_emit(cmd, 0x123);                /* VAL */
+	igt_describe("Test iova fault handling (stress)");
+	igt_subtest("iova-fault-stress") {
+		igt_require(dev->gen >= 6);
 
-		igt_wait_and_close(igt_msm_cmd_submit(cmd));
+		do_fault_test(pipe, true);
 	}
 
 	igt_fixture {
Signature · 1 line
2.50.0
author
#5 lore raw

PATCH 3/9 msm/mapping: update for sparse

In reply to Rob Clark

From: Rob Clark <[email protected]>

The debugfs format changes a bit. Update the igt test to handle both cases.

---
 tests/msm/msm_mapping.c | 4 ++++
 1 file changed, 4 insertions(+)
tests/msm/msm_mapping.c +4 -0
index ac20ca91d613..f536db82aba2 100644
@@ -148,6 +148,10 @@ get_bo_addr(int drm_fd, const char *name)
 
 			ret = sscanf(line, "      vmas: [gpu: aspace=%"PRIx64", %"PRIx64",mapped,inuse=1]",
 					&dummy, &addr);
+			if (ret != 2) {
+				ret = sscanf(line, "      vmas: [gpu: vm=%"PRIx64", %"PRIx64", mapped]",
+						&dummy, &addr);
+			}
 			igt_fail_on(ret != 2);
 
 			return addr;
Signature · 1 line
2.50.0
#6 lore raw

Re: [PATCH igt 3/9] msm/mapping: update for sparse

Hi Rob,

Quoted 1 line · Rob Clark

From: Rob Clark <[email protected]>

Fix 'From: ' e-mail address to match s-o-b.
Also add 'tests/' prefix:

[PATCH igt 3/9] tests/msm/msm_mapping: update for sparse

Quoted 14 lines

The debugfs format changes a bit. Update the igt test to handle both cases.

---
 tests/msm/msm_mapping.c | 4 ++++
 1 file changed, 4 insertions(+)
tests/msm/msm_mapping.c +0 -0
index ac20ca91d613..f536db82aba2 100644

tests/msm/msm_mapping.c get_bo_addr(int drm_fd, const char *name) · line 153

Quoted 6 lines
tests/msm/msm_mapping.c +3 -0
@@ -148,6 +148,10 @@ get_bo_addr(int drm_fd, const char *name)
 
 			ret = sscanf(line, "      vmas: [gpu: aspace=%"PRIx64", %"PRIx64",mapped,inuse=1]",
 					&dummy, &addr);
+			if (ret != 2) {
+				ret = sscanf(line, "      vmas: [gpu: vm=%"PRIx64", %"PRIx64", mapped]",
+						&dummy, &addr);

Align to 'line'.

Regards,
Kamil

Quoted 7 lines
tests/msm/msm_mapping.c +1 -0
+			}
 			igt_fail_on(ret != 2);
 
 			return addr;
Signature · 1 line
2.50.0
author
#7 lore raw

PATCH 4/9 msm/mapping: Handle BO names with spaces

In reply to Rob Clark

From: Rob Clark <[email protected]>

Instead of trimming at the first space, scan from the end of the string until we reach the first non-space char.

---
 tests/msm/msm_mapping.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)
tests/msm/msm_mapping.c +4 -3
index f536db82aba2..5afbcd081fc7 100644
@@ -101,13 +101,14 @@ endswith(const char *str, const char *end)
 
 	/* Trim trailing whitespace: */
 	if (p) {
-		char *c = p;
-		while (c) {
+		char *c = p + strlen(p) - 1;
+		while (c > p ) {
 			if (isspace(*c)) {
 				*c = '\0';
+			} else {
 				break;
 			}
-			c++;
+			c--;
 		}
 	}
 
Signature · 1 line
2.50.0
#8 lore raw

Re: [PATCH igt 4/9] msm/mapping: Handle BO names with spaces

Hi Rob,

Quoted 15 lines · Rob Clark

From: Rob Clark <[email protected]>

Instead of trimming at the first space, scan from the end of the string until we reach the first non-space char.

---
 tests/msm/msm_mapping.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)
tests/msm/msm_mapping.c +0 -0
index f536db82aba2..5afbcd081fc7 100644

tests/msm/msm_mapping.c endswith(const char *str, const char *end) · line 104

Quoted 6 lines
tests/msm/msm_mapping.c +1 -2
@@ -101,13 +101,14 @@ endswith(const char *str, const char *end)
 
 	/* Trim trailing whitespace: */
 	if (p) {
-		char *c = p;
-		while (c) {
+		char *c = p + strlen(p) - 1;

Add empty line here.

tests/msm/msm_mapping.c endswith(const char *str, const char *end) · line 105

Quoted 1 line
tests/msm/msm_mapping.c +1 -0
+		while (c > p ) {

Remove space after 'p':

		while (c > p) {

Regards,
Kamil

Quoted 13 lines
tests/msm/msm_mapping.c +2 -1
 			if (isspace(*c)) {
 				*c = '\0';
+			} else {
 				break;
 			}
-			c++;
+			c--;
 		}
 	}
 
Signature · 1 line
2.50.0
author
#9 lore raw

PATCH 5/9 msm/mapping: Add additional subtests

In reply to Rob Clark

From: Rob Clark <[email protected]>

Test a few additional buffers that userspace should not have access to.

---
 tests/msm/msm_mapping.c | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
tests/msm/msm_mapping.c +30 -0
index 5afbcd081fc7..846385bb5206 100644
@@ -253,6 +253,36 @@ igt_main
 		do_mapping_test(pipe, "shadow", false);
 	}
 
+	igt_describe("Test pwrup_reglist mapping, should be inaccessible");
+	igt_subtest("pwrup_reglist") {
+		do_mapping_test(pipe, "pwrup_reglist", true);
+		do_mapping_test(pipe, "pwrup_reglist", false);
+	}
+
+	igt_describe("Test memptrs mapping, should be inaccessible");
+	igt_subtest("memptrs") {
+		/*
+		 * This test will fail on older GPUs without HW_APRIV, but
+		 * there isn't a good way to test that from userspace, short
+		 * of maintaining a giant table.  Probably just easier to
+		 * list it in xfails or skips for those GPUs.
+		 */
+		do_mapping_test(pipe, "memptrs", true);
+		do_mapping_test(pipe, "memptrs", false);
+	}
+
+	igt_describe("Test 'preempt_record ring0' mapping, should be inaccessible");
+	igt_subtest("preempt_record_ring0") {
+		do_mapping_test(pipe, "preempt_record ring0", true);
+		do_mapping_test(pipe, "preempt_record ring0", false);
+	}
+
+	igt_describe("Test 'preempt_smmu_info ring0' mapping, should be inaccessible");
+	igt_subtest("preempt_smmu_info_ring0") {
+		do_mapping_test(pipe, "preempt_smmu_info ring0", true);
+		do_mapping_test(pipe, "preempt_smmu_info ring0", false);
+	}
+
 	igt_fixture {
 		igt_msm_pipe_close(pipe);
 		igt_msm_dev_close(dev);
Signature · 1 line
2.50.0
#10 lore raw

Re: [PATCH igt 5/9] msm/mapping: Add additional subtests

Hi Rob,

Quoted 1 line · Rob Clark

From: Rob Clark <[email protected]>

Fix 'From: ' e-mail, also please add to all subjects 'tests/' prefix:

[PATCH igt 5/9] tests/msm/msm_mapping: Add additional subtests

Please apply that also to other tests in series.

Btw, why not a little more desciription in subject?

[PATCH igt 5/9] tests/msm/msm_mapping: Test inaccessible buffers

Regards,
Kamil

Quoted 52 lines

Test a few additional buffers that userspace should not have access to.

---
 tests/msm/msm_mapping.c | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
tests/msm/msm_mapping.c +30 -0
index 5afbcd081fc7..846385bb5206 100644
@@ -253,6 +253,36 @@ igt_main
 		do_mapping_test(pipe, "shadow", false);
 	}
 
+	igt_describe("Test pwrup_reglist mapping, should be inaccessible");
+	igt_subtest("pwrup_reglist") {
+		do_mapping_test(pipe, "pwrup_reglist", true);
+		do_mapping_test(pipe, "pwrup_reglist", false);
+	}
+
+	igt_describe("Test memptrs mapping, should be inaccessible");
+	igt_subtest("memptrs") {
+		/*
+		 * This test will fail on older GPUs without HW_APRIV, but
+		 * there isn't a good way to test that from userspace, short
+		 * of maintaining a giant table.  Probably just easier to
+		 * list it in xfails or skips for those GPUs.
+		 */
+		do_mapping_test(pipe, "memptrs", true);
+		do_mapping_test(pipe, "memptrs", false);
+	}
+
+	igt_describe("Test 'preempt_record ring0' mapping, should be inaccessible");
+	igt_subtest("preempt_record_ring0") {
+		do_mapping_test(pipe, "preempt_record ring0", true);
+		do_mapping_test(pipe, "preempt_record ring0", false);
+	}
+
+	igt_describe("Test 'preempt_smmu_info ring0' mapping, should be inaccessible");
+	igt_subtest("preempt_smmu_info_ring0") {
+		do_mapping_test(pipe, "preempt_smmu_info ring0", true);
+		do_mapping_test(pipe, "preempt_smmu_info ring0", false);
+	}
+
 	igt_fixture {
 		igt_msm_pipe_close(pipe);
 		igt_msm_dev_close(dev);
Signature · 1 line
2.50.0
author
#11 lore raw

PATCH 6/9 msm/mapping: Wait for devcore to become available

In reply to Rob Clark

From: Rob Clark <[email protected]>

The devcore could take some time to show up, so add a igt_wait() with timeout so we don't fail the test if the devcore is not immediately available.

This addresses a source of flakeyness.

---
 tests/msm/msm_mapping.c | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)
tests/msm/msm_mapping.c +10 -6
index 846385bb5206..03a9e814c931 100644
@@ -42,14 +42,18 @@
  */
 
 static char *
-get_and_clear_devcore(void)
+get_and_clear_devcore(int timeout_ms)
 {
 	glob_t glob_buf = {0};
 	char *buf = NULL;
-	int ret, fd;
+	int fd;
 
-	ret = glob("/sys/class/devcoredump/devcd*/data", GLOB_NOSORT, NULL, &glob_buf);
-	if ((ret == GLOB_NOMATCH) || !glob_buf.gl_pathc)
+	/* The devcore shows up asynchronously, so it might not be
+	 * immediately available:
+	 */
+	if (!igt_wait(glob("/sys/class/devcoredump/devcd*/data",
+			   GLOB_NOSORT, NULL, &glob_buf) != GLOB_NOMATCH,
+		      timeout_ms, 100))
 		return NULL;
 
 	fd = open(glob_buf.gl_pathv[0], O_RDWR);
@@ -175,7 +179,7 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
 	int fence_fd, ret;
 
 	/* Clear any existing devcore's: */
-	while ((devcore = get_and_clear_devcore())) {
+	while ((devcore = get_and_clear_devcore(0))) {
 		free(devcore);
 	}
 
@@ -208,7 +212,7 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
 	/* And now we should have gotten a devcore from the iova fault
 	 * triggered by the read or write:
 	 */
-	devcore = get_and_clear_devcore();
+	devcore = get_and_clear_devcore(1000);
 	igt_fail_on(!devcore);
 
 	/* Make sure the devcore is from iova fault: */
Signature · 1 line
2.50.0
#12 lore raw

Re: [PATCH igt 6/9] msm/mapping: Wait for devcore to become available

Hi Rob,

Quoted 1 line · Rob Clark

From: Rob Clark <[email protected]>

Is this the same as 1/9 patch?

One more nit just spotted, it is useally 'i-g-t' after PATCH:

[PATCH i-g-t 6/9] tests/msm/msm_mapping: Wait for devcore to become available

Regards,
Kamil

Quoted 60 lines

The devcore could take some time to show up, so add a igt_wait() with timeout so we don't fail the test if the devcore is not immediately available.

This addresses a source of flakeyness.

---
 tests/msm/msm_mapping.c | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)
tests/msm/msm_mapping.c +10 -6
index 846385bb5206..03a9e814c931 100644
@@ -42,14 +42,18 @@
  */
 
 static char *
-get_and_clear_devcore(void)
+get_and_clear_devcore(int timeout_ms)
 {
 	glob_t glob_buf = {0};
 	char *buf = NULL;
-	int ret, fd;
+	int fd;
 
-	ret = glob("/sys/class/devcoredump/devcd*/data", GLOB_NOSORT, NULL, &glob_buf);
-	if ((ret == GLOB_NOMATCH) || !glob_buf.gl_pathc)
+	/* The devcore shows up asynchronously, so it might not be
+	 * immediately available:
+	 */
+	if (!igt_wait(glob("/sys/class/devcoredump/devcd*/data",
+			   GLOB_NOSORT, NULL, &glob_buf) != GLOB_NOMATCH,
+		      timeout_ms, 100))
 		return NULL;
 
 	fd = open(glob_buf.gl_pathv[0], O_RDWR);
@@ -175,7 +179,7 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
 	int fence_fd, ret;
 
 	/* Clear any existing devcore's: */
-	while ((devcore = get_and_clear_devcore())) {
+	while ((devcore = get_and_clear_devcore(0))) {
 		free(devcore);
 	}
 
@@ -208,7 +212,7 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
 	/* And now we should have gotten a devcore from the iova fault
 	 * triggered by the read or write:
 	 */
-	devcore = get_and_clear_devcore();
+	devcore = get_and_clear_devcore(1000);
 	igt_fail_on(!devcore);
 
 	/* Make sure the devcore is from iova fault: */
Signature · 1 line
2.50.0
#13 lore raw

Re: [PATCH igt 6/9] msm/mapping: Wait for devcore to become available

Quoted 6 lines · Kamil Konieczny

Hi Rob,

Quoted 1 line · Rob Clark

From: Rob Clark <[email protected]>

Is this the same as 1/9 patch?

No, but similar. Both tests have a similar, but subtly different, function to read the devcore. (In the mapping test, we don't have to read the whole file, but we want to return the first part so the test can parse it.. in the recovery test we don't need to parse it, but want to explicitly read the entire devcore.)

BR,
-R

Quoted 68 lines

One more nit just spotted, it is useally 'i-g-t' after PATCH:

[PATCH i-g-t 6/9] tests/msm/msm_mapping: Wait for devcore to become available

Regards,
Kamil

Quoted 60 lines

The devcore could take some time to show up, so add a igt_wait() with timeout so we don't fail the test if the devcore is not immediately available.

This addresses a source of flakeyness.

---
 tests/msm/msm_mapping.c | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)
tests/msm/msm_mapping.c +10 -7
index 846385bb5206..03a9e814c931 100644
@@ -42,14 +42,18 @@
  */
 
 static char *
-get_and_clear_devcore(void)
+get_and_clear_devcore(int timeout_ms)
 {
      glob_t glob_buf = {0};
      char *buf = NULL;
-     int ret, fd;
+     int fd;
 
-     ret = glob("/sys/class/devcoredump/devcd*/data", GLOB_NOSORT, NULL, &glob_buf);
-     if ((ret == GLOB_NOMATCH) || !glob_buf.gl_pathc)
+     /* The devcore shows up asynchronously, so it might not be
+      * immediately available:
+      */
+     if (!igt_wait(glob("/sys/class/devcoredump/devcd*/data",
+                        GLOB_NOSORT, NULL, &glob_buf) != GLOB_NOMATCH,
+                   timeout_ms, 100))
              return NULL;
 
      fd = open(glob_buf.gl_pathv[0], O_RDWR);
@@ -175,7 +179,7 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
      int fence_fd, ret;
 
      /* Clear any existing devcore's: */
-     while ((devcore = get_and_clear_devcore())) {
+     while ((devcore = get_and_clear_devcore(0))) {
              free(devcore);
      }
 
@@ -208,7 +212,7 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
      /* And now we should have gotten a devcore from the iova fault
       * triggered by the read or write:
       */
-     devcore = get_and_clear_devcore();
+     devcore = get_and_clear_devcore(1000);
      igt_fail_on(!devcore);
 
      /* Make sure the devcore is from iova fault: */
--

2.50.0

author
#14 lore raw

PATCH 7/9 msm/mapping: Handle larger gmem file size

In reply to Rob Clark

From: Rob Clark <[email protected]>

If running on a system with full desktop environment, the file will be much larger than 0x4000 bytes.

---
 tests/msm/msm_mapping.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tests/msm/msm_mapping.c +1 -1
index 03a9e814c931..978ea18375dd 100644
@@ -122,7 +122,7 @@ endswith(const char *str, const char *end)
 static uint64_t
 get_bo_addr(int drm_fd, const char *name)
 {
-	char buf[0x4000];
+	char buf[0x80000];
 	char *p = buf;
 
 	igt_debugfs_read(drm_fd, "gem", buf);
Signature · 1 line
2.50.0
#15 lore raw

Re: [PATCH igt 7/9] msm/mapping: Handle larger gmem file size

Hi Rob,

Quoted 15 lines · Rob Clark

From: Rob Clark <[email protected]>

If running on a system with full desktop environment, the file will be much larger than 0x4000 bytes.

---
 tests/msm/msm_mapping.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tests/msm/msm_mapping.c +0 -0
index 03a9e814c931..978ea18375dd 100644

tests/msm/msm_mapping.c endswith(const char *str, const char *end) · line 125

Quoted 5 lines
tests/msm/msm_mapping.c +1 -1
@@ -122,7 +122,7 @@ endswith(const char *str, const char *end)
 static uint64_t
 get_bo_addr(int drm_fd, const char *name)
 {
-	char buf[0x4000];
+	char buf[0x80000];

If it is that big why not malloc() it?

Regards,
Kamil

Quoted 6 lines
tests/msm/msm_mapping.c +0 -0
 	char *p = buf;
 
 	igt_debugfs_read(drm_fd, "gem", buf);
Signature · 1 line
2.50.0
#16 lore raw

Re: [PATCH igt 7/9] msm/mapping: Handle larger gmem file size

Quoted 13 lines · Kamil Konieczny

Hi Rob,

Quoted 10 lines · Rob Clark

From: Rob Clark <[email protected]>

If running on a system with full desktop environment, the file will be much larger than 0x4000 bytes.

---
 tests/msm/msm_mapping.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 12 lines

tests/msm/msm_mapping.c endswith(const char *str, const char *end) · line 125

Quoted 10 lines
tests/msm/msm_mapping.c +1 -1
index 03a9e814c931..978ea18375dd 100644
@@ -122,7 +122,7 @@ endswith(const char *str, const char *end)
 static uint64_t
 get_bo_addr(int drm_fd, const char *name)
 {
-     char buf[0x4000];
+     char buf[0x80000];

If it is that big why not malloc() it?

in kernel, for sure. But userspace stack size is multiple MB at least

BR,
-R

Quoted 9 lines

Regards,
Kamil

Quoted 6 lines
tests/msm/msm_mapping.c +0 -1
      char *p = buf;
 
      igt_debugfs_read(drm_fd, "gem", buf);
--

2.50.0

#17 lore raw

Re: [PATCH igt 7/9] msm/mapping: Handle larger gmem file size

Hi Rob,

Quoted 28 lines · Rob Clark
Quoted 13 lines · Kamil Konieczny

Hi Rob,

Quoted 10 lines · Rob Clark

From: Rob Clark <[email protected]>

If running on a system with full desktop environment, the file will be much larger than 0x4000 bytes.

---
 tests/msm/msm_mapping.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 12 lines

tests/msm/msm_mapping.c endswith(const char *str, const char *end) · line 125

Quoted 10 lines
tests/msm/msm_mapping.c +1 -1
index 03a9e814c931..978ea18375dd 100644
@@ -122,7 +122,7 @@ endswith(const char *str, const char *end)
 static uint64_t
 get_bo_addr(int drm_fd, const char *name)
 {
-     char buf[0x4000];
+     char buf[0x80000];

If it is that big why not malloc() it?

Quoted 4 lines

in kernel, for sure. But userspace stack size is multiple MB at least

BR,
-R

You are reading "gem" debugfs below, so this buffer in igt is in userspace, no need for it to be on stack. Btw you just discovered a bug in igt, imho this function should give sizeof(buf) to caller here to igt_debugfs_read():

igt_debugfs_read(drm_fd, "gem", buf, sizeof(buf));

Also imho it should be calloc() to avoid garbage later on in buf. Or if it should read all of debugfs node, make it like:

int igt_debugfs_read_all(int drm_fd, char *, char **buf);

and let it alloc *buf, and later realloc this *buf if needed.

Regards,
Kamil

Quoted 10 lines
Quoted 10 lines

Regards,
Kamil

Quoted 6 lines
tests/msm/msm_mapping.c +0 -1
      char *p = buf;
 
      igt_debugfs_read(drm_fd, "gem", buf);
--

2.50.0

#18 lore raw

Re: [PATCH igt 7/9] msm/mapping: Handle larger gmem file size

Quoted 36 lines · Kamil Konieczny

Hi Rob,

Quoted 28 lines · Rob Clark
Quoted 13 lines · Kamil Konieczny

Hi Rob,

Quoted 10 lines · Rob Clark

From: Rob Clark <[email protected]>

If running on a system with full desktop environment, the file will be much larger than 0x4000 bytes.

---
 tests/msm/msm_mapping.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 12 lines

tests/msm/msm_mapping.c endswith(const char *str, const char *end) · line 125

Quoted 10 lines
tests/msm/msm_mapping.c +1 -1
index 03a9e814c931..978ea18375dd 100644
@@ -122,7 +122,7 @@ endswith(const char *str, const char *end)
 static uint64_t
 get_bo_addr(int drm_fd, const char *name)
 {
-     char buf[0x4000];
+     char buf[0x80000];

If it is that big why not malloc() it?

Quoted 4 lines

in kernel, for sure. But userspace stack size is multiple MB at least

BR,
-R

Quoted 6 lines

You are reading "gem" debugfs below, so this buffer in igt is in userspace, no need for it to be on stack. Btw you just discovered a bug in igt, imho this function should give sizeof(buf) to caller here to igt_debugfs_read():

igt_debugfs_read(drm_fd, "gem", buf, sizeof(buf));

Actually igt_debugfs_read() is a convenience wrapper macro for __igt_debugfs_read() which does just this. But makes igt_debugfs_read() more convenient for stack allocated buffers.

BR,
-R

Quoted 21 lines

Also imho it should be calloc() to avoid garbage later on in buf. Or if it should read all of debugfs node, make it like:

int igt_debugfs_read_all(int drm_fd, char *, char **buf);

and let it alloc *buf, and later realloc this *buf if needed.

Regards,
Kamil

Quoted 10 lines
Quoted 10 lines

Regards,
Kamil

Quoted 6 lines
tests/msm/msm_mapping.c +0 -1
      char *p = buf;
 
      igt_debugfs_read(drm_fd, "gem", buf);
--

2.50.0

author
#19 lore raw

PATCH 8/9 msm/mapping: Add wait for stall-on-fault to re-arm

In reply to Rob Clark

From: Rob Clark <[email protected]>

Newer kernels disable stall-on-fault for a grace period, to avoid a flood of faults causing instability with memory translations that the hw attempts with the translation stalled. Fortunately it adds a debugfs file so we can know how long we need to wait for stall-on- fault to be re-enabled.

---
 tests/msm/msm_mapping.c | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
tests/msm/msm_mapping.c +29 -0
index 978ea18375dd..7e2f5c7eadc8 100644
@@ -74,6 +74,30 @@ get_and_clear_devcore(int timeout_ms)
 	return buf;
 }
 
+static void
+wait_for_stall_on_fault(int drm_fd)
+{
+	char buf[64] = "\0";
+
+	do {
+		int us;
+
+		igt_debugfs_read(drm_fd, "stall_reenable_time_us", buf);
+		if (!strlen(buf)) {
+			/* Not supported on older kernels: */
+			return;
+		}
+
+		us = atoi(buf);
+		if (!us) {
+			/* Done waiting: */
+			return;
+		}
+
+		usleep(us);
+	} while (true);
+}
+
 /*
  * Helper to find named buffer address
  */
@@ -224,6 +248,11 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
 	ret = sscanf(s, "  - iova=%"PRIx64, &fault_addr);
 	igt_fail_on(ret != 1);
 	igt_fail_on(addr != fault_addr);
+
+	/* Wait for stall-on-fault to re-enable, otherwise the next sub-test
+	 * would not generate a devcore:
+	 */
+	wait_for_stall_on_fault(pipe->dev->fd);
 }
 
 /*
Signature · 1 line
2.50.0
#20 lore raw

Re: [PATCH igt 8/9] msm/mapping: Add wait for stall-on-fault to re-arm

Hi Rob,

Quoted 5 lines · Rob Clark

From: Rob Clark <[email protected]>

Newer kernels disable stall-on-fault for a grace period, to avoid a flood of faults causing instability with memory translations that the hw attempts with the translation stalled. Fortunately it adds a

Is it system-wide or only for msm driver?

Please improve subject:

[PATCH igt 8/9] tests/msm/msm_mapping: Add wait for stall-on-fault to re-arm

imho it could be shorter:

[PATCH igt 8/9] tests/msm/msm_mapping: Wait for stall-on-fault

Regards,
Kamil

Quoted 58 lines

debugfs file so we can know how long we need to wait for stall-on- fault to be re-enabled.

---
 tests/msm/msm_mapping.c | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
tests/msm/msm_mapping.c +29 -0
index 978ea18375dd..7e2f5c7eadc8 100644
@@ -74,6 +74,30 @@ get_and_clear_devcore(int timeout_ms)
 	return buf;
 }
 
+static void
+wait_for_stall_on_fault(int drm_fd)
+{
+	char buf[64] = "\0";
+
+	do {
+		int us;
+
+		igt_debugfs_read(drm_fd, "stall_reenable_time_us", buf);
+		if (!strlen(buf)) {
+			/* Not supported on older kernels: */
+			return;
+		}
+
+		us = atoi(buf);
+		if (!us) {
+			/* Done waiting: */
+			return;
+		}
+
+		usleep(us);
+	} while (true);
+}
+
 /*
  * Helper to find named buffer address
  */
@@ -224,6 +248,11 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
 	ret = sscanf(s, "  - iova=%"PRIx64, &fault_addr);
 	igt_fail_on(ret != 1);
 	igt_fail_on(addr != fault_addr);
+
+	/* Wait for stall-on-fault to re-enable, otherwise the next sub-test
+	 * would not generate a devcore:
+	 */
+	wait_for_stall_on_fault(pipe->dev->fd);
 }
 
 /*
Signature · 1 line
2.50.0
#21 lore raw

Re: [PATCH igt 8/9] msm/mapping: Add wait for stall-on-fault to re-arm

Quoted 10 lines · Kamil Konieczny

Hi Rob,

Quoted 5 lines · Rob Clark

From: Rob Clark <[email protected]>

Newer kernels disable stall-on-fault for a grace period, to avoid a flood of faults causing instability with memory translations that the hw attempts with the translation stalled. Fortunately it adds a

Is it system-wide or only for msm driver?

specific to msm

BR,
-R

Quoted 69 lines

Please improve subject:

[PATCH igt 8/9] tests/msm/msm_mapping: Add wait for stall-on-fault to re-arm

imho it could be shorter:

[PATCH igt 8/9] tests/msm/msm_mapping: Wait for stall-on-fault

Regards,
Kamil

Quoted 58 lines

debugfs file so we can know how long we need to wait for stall-on- fault to be re-enabled.

---
 tests/msm/msm_mapping.c | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
tests/msm/msm_mapping.c +29 -1
index 978ea18375dd..7e2f5c7eadc8 100644
@@ -74,6 +74,30 @@ get_and_clear_devcore(int timeout_ms)
      return buf;
 }
 
+static void
+wait_for_stall_on_fault(int drm_fd)
+{
+     char buf[64] = "\0";
+
+     do {
+             int us;
+
+             igt_debugfs_read(drm_fd, "stall_reenable_time_us", buf);
+             if (!strlen(buf)) {
+                     /* Not supported on older kernels: */
+                     return;
+             }
+
+             us = atoi(buf);
+             if (!us) {
+                     /* Done waiting: */
+                     return;
+             }
+
+             usleep(us);
+     } while (true);
+}
+
 /*
  * Helper to find named buffer address
  */
@@ -224,6 +248,11 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
      ret = sscanf(s, "  - iova=%"PRIx64, &fault_addr);
      igt_fail_on(ret != 1);
      igt_fail_on(addr != fault_addr);
+
+     /* Wait for stall-on-fault to re-enable, otherwise the next sub-test
+      * would not generate a devcore:
+      */
+     wait_for_stall_on_fault(pipe->dev->fd);
 }
 
 /*
--

2.50.0

#22 lore raw

Re: [PATCH igt 8/9] msm/mapping: Add wait for stall-on-fault to re-arm

Hi Rob,

Quoted 11 lines · Rob Clark
Quoted 9 lines · Kamil Konieczny

Hi Rob,

Quoted 5 lines · Rob Clark

From: Rob Clark <[email protected]>

Newer kernels disable stall-on-fault for a grace period, to avoid a flood of faults causing instability with memory translations that the hw attempts with the translation stalled. Fortunately it adds a

Quoted 6 lines
Quoted 1 line

Is it system-wide or only for msm driver?

specific to msm

BR,
-R

Ok, so please write it explicitly, like for example:

Newer msm driver disables stall-on-fault for a grace period, [...rest...]

Please also give a link to lore with a change in msm driver.

Regards,
Kamil

Quoted 70 lines
Quoted 70 lines

Please improve subject:

[PATCH igt 8/9] tests/msm/msm_mapping: Add wait for stall-on-fault to re-arm

imho it could be shorter:

[PATCH igt 8/9] tests/msm/msm_mapping: Wait for stall-on-fault

Regards,
Kamil

Quoted 58 lines

debugfs file so we can know how long we need to wait for stall-on- fault to be re-enabled.

---
 tests/msm/msm_mapping.c | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
tests/msm/msm_mapping.c +29 -1
index 978ea18375dd..7e2f5c7eadc8 100644
@@ -74,6 +74,30 @@ get_and_clear_devcore(int timeout_ms)
      return buf;
 }
 
+static void
+wait_for_stall_on_fault(int drm_fd)
+{
+     char buf[64] = "\0";
+
+     do {
+             int us;
+
+             igt_debugfs_read(drm_fd, "stall_reenable_time_us", buf);
+             if (!strlen(buf)) {
+                     /* Not supported on older kernels: */
+                     return;
+             }
+
+             us = atoi(buf);
+             if (!us) {
+                     /* Done waiting: */
+                     return;
+             }
+
+             usleep(us);
+     } while (true);
+}
+
 /*
  * Helper to find named buffer address
  */
@@ -224,6 +248,11 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
      ret = sscanf(s, "  - iova=%"PRIx64, &fault_addr);
      igt_fail_on(ret != 1);
      igt_fail_on(addr != fault_addr);
+
+     /* Wait for stall-on-fault to re-enable, otherwise the next sub-test
+      * would not generate a devcore:
+      */
+     wait_for_stall_on_fault(pipe->dev->fd);
 }
 
 /*
--

2.50.0

author
#23 lore raw

PATCH 9/9 msm/mapping: Free devcore

In reply to Rob Clark

From: Rob Clark <[email protected]>

We shouldn't leak the devcore.

---
 tests/msm/msm_mapping.c | 2 ++
 1 file changed, 2 insertions(+)
tests/msm/msm_mapping.c +2 -0
index 7e2f5c7eadc8..b735d5f014c3 100644
@@ -249,6 +249,8 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
 	igt_fail_on(ret != 1);
 	igt_fail_on(addr != fault_addr);
 
+	free(devcore);
+
 	/* Wait for stall-on-fault to re-enable, otherwise the next sub-test
 	 * would not generate a devcore:
 	 */
Signature · 1 line
2.50.0
#24 lore raw

Re: [PATCH igt 9/9] msm/mapping: Free devcore

Hi Rob,

Quoted 1 line · Rob Clark

From: Rob Clark <[email protected]>

imho:

[PATCH i-g-t 9/9] tests/msm/msm_mapping: Fix memory leak

Also imho this should be your first patch, so fixes first, but it is up to you.

Regards,
Kamil

Quoted 24 lines

We shouldn't leak the devcore.

---
 tests/msm/msm_mapping.c | 2 ++
 1 file changed, 2 insertions(+)
tests/msm/msm_mapping.c +2 -0
index 7e2f5c7eadc8..b735d5f014c3 100644
@@ -249,6 +249,8 @@ do_mapping_test(struct msm_pipe *pipe, const char *buffername, bool write)
 	igt_fail_on(ret != 1);
 	igt_fail_on(addr != fault_addr);
 
+	free(devcore);
+
 	/* Wait for stall-on-fault to re-enable, otherwise the next sub-test
 	 * would not generate a devcore:
 	 */
Signature · 1 line
2.50.0
#25 lore raw

✓ Xe.CI.BAT: success for msm: recovery and mapping updates

In reply to Rob Clark
== Series Details ==

== Series Details ==

Series: msm: recovery and mapping updates
URL : https://patchwork.freedesktop.org/series/150977/
State : success

== Summary ==

CI Bug Log - changes from XEIGT_8432_BAT -> XEIGTPW_13374_BAT
====================================================

Summary
-------

**SUCCESS**

No regressions found.

Participating hosts (8 -> 8)
------------------------------

No changes in participating hosts

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

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

### IGT changes ###

#### Issues hit ####

* igt@kms_flip@basic-plain-flip@b-edp1:
- bat-adlp-7: [PASS][1] -> [DMESG-WARN][2] ([Intel XE#4543]) +1 other test dmesg-warn
[1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/bat-adlp-7/igt@kms_flip@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/bat-adlp-7/igt@kms_flip@[email protected]

#### Possible fixes ####

* igt@kms_flip@basic-flip-vs-dpms:
- bat-adlp-7: [DMESG-WARN][3] ([Intel XE#4543]) -> [PASS][4] +1 other test pass
[3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/bat-adlp-7/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/bat-adlp-7/igt@[email protected]

[Intel XE#4543]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4543

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

* IGT: IGT_8432 -> IGTPW_13374

IGTPW_13374: 13374
IGT_8432: 4871829d8b7117553eb2dc1bdb9a0d18de428a98 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
xe-3325-d9007d535ea106181346f9988c97aa73a9cdfb86: d9007d535ea106181346f9988c97aa73a9cdfb86

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/index.html

#26 lore raw

✗ i915.CI.BAT: failure for msm: recovery and mapping updates

In reply to Rob Clark
== Series Details ==

== Series Details ==

Series: msm: recovery and mapping updates
URL : https://patchwork.freedesktop.org/series/150977/
State : failure

== Summary ==

CI Bug Log - changes from IGT_8432 -> IGTPW_13374
====================================================

Summary
-------

**FAILURE**

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

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

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

Participating hosts (45 -> 43)
------------------------------

Missing (2): fi-snb-2520m fi-elk-e7500

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

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

### IGT changes ###

#### Possible regressions ####

* igt@i915_selftest@live@requests:
- bat-atsm-1: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8432/bat-atsm-1/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13374/bat-atsm-1/igt@i915_selftest@[email protected]

#### Warnings ####

* igt@i915_selftest@live:
- bat-atsm-1: [DMESG-FAIL][3] ([i915#12061] / [i915#14204]) -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8432/bat-atsm-1/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13374/bat-atsm-1/igt@[email protected]

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

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

### IGT changes ###

#### Issues hit ####

* igt@i915_selftest@live:
- bat-jsl-1: [PASS][5] -> [DMESG-WARN][6] ([i915#13827]) +1 other test dmesg-warn
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8432/bat-jsl-1/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13374/bat-jsl-1/igt@[email protected]
- bat-dg2-11: [PASS][7] -> [DMESG-FAIL][8] ([i915#12061] / [i915#14556])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8432/bat-dg2-11/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13374/bat-dg2-11/igt@[email protected]

* igt@i915_selftest@live@workarounds:
- bat-dg2-11: [PASS][9] -> [DMESG-FAIL][10] ([i915#12061])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8432/bat-dg2-11/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13374/bat-dg2-11/igt@i915_selftest@[email protected]
- bat-arls-6: [PASS][11] -> [DMESG-FAIL][12] ([i915#12061]) +1 other test dmesg-fail
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8432/bat-arls-6/igt@i915_selftest@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13374/bat-arls-6/igt@i915_selftest@[email protected]

#### Possible fixes ####

* igt@i915_selftest@live@execlists:
- bat-dg2-14: [ABORT][13] ([i915#14201]) -> [PASS][14] +1 other test pass
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8432/bat-dg2-14/igt@i915_selftest@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13374/bat-dg2-14/igt@i915_selftest@[email protected]

[i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
[i915#13827]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13827
[i915#14201]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14201
[i915#14204]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14204
[i915#14556]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14556

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

* CI: CI-20190529 -> None
* IGT: IGT_8432 -> IGTPW_13374

CI-20190529: 20190529
CI_DRM_16777: d9007d535ea106181346f9988c97aa73a9cdfb86 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_13374: 13374
IGT_8432: 4871829d8b7117553eb2dc1bdb9a0d18de428a98 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git

== Logs ==

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

#27 lore raw

✓ Xe.CI.Full: success for msm: recovery and mapping updates

In reply to Rob Clark
== Series Details ==

== Series Details ==

Series: msm: recovery and mapping updates
URL : https://patchwork.freedesktop.org/series/150977/
State : success

== Summary ==

CI Bug Log - changes from XEIGT_8432_FULL -> XEIGTPW_13374_FULL
====================================================

Summary
-------

**SUCCESS**

No regressions found.

Participating hosts (4 -> 3)
------------------------------

Missing (1): shard-adlp

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

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

### IGT changes ###

#### Issues hit ####

* igt@intel_hwmon@hwmon-write:
- shard-bmg: [PASS][1] -> [FAIL][2] ([Intel XE#4665])
[1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-4/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@[email protected]

* igt@kms_addfb_basic@addfb25-y-tiled-small-legacy:
- shard-bmg: NOTRUN -> [SKIP][3] ([Intel XE#2233])
[3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@[email protected]
- shard-dg2-set2: NOTRUN -> [SKIP][4] ([Intel XE#623])
[4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][5] ([Intel XE#1466])
[5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-5/igt@[email protected]

* igt@kms_async_flips@async-flip-suspend-resume:
- shard-dg2-set2: [PASS][6] -> [ABORT][7] ([Intel XE#4847]) +1 other test abort
[6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-433/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]

* igt@kms_async_flips@async-flip-suspend-resume@pipe-a-edp-1:
- shard-lnl: [PASS][8] -> [ABORT][9] ([Intel XE#4847]) +1 other test abort
[8]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-lnl-2/igt@kms_async_flips@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-1/igt@kms_async_flips@[email protected]

* igt@kms_async_flips@invalid-async-flip-atomic:
- shard-dg2-set2: NOTRUN -> [SKIP][10] ([Intel XE#3768])
[10]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]
- shard-bmg: NOTRUN -> [SKIP][11] ([Intel XE#3768])
[11]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]

* igt@kms_big_fb@linear-64bpp-rotate-270:
- shard-bmg: NOTRUN -> [SKIP][12] ([Intel XE#2327])
[12]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][13] ([Intel XE#1407])
[13]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-7/igt@[email protected]

* igt@kms_big_fb@y-tiled-16bpp-rotate-0:
- shard-bmg: NOTRUN -> [SKIP][14] ([Intel XE#1124]) +2 other tests skip
[14]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@[email protected]

* igt@kms_big_fb@y-tiled-32bpp-rotate-270:
- shard-lnl: NOTRUN -> [SKIP][15] ([Intel XE#1124])
[15]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-4/igt@[email protected]

* igt@kms_big_fb@yf-tiled-64bpp-rotate-180:
- shard-dg2-set2: NOTRUN -> [SKIP][16] ([Intel XE#1124]) +6 other tests skip
[16]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]

* igt@kms_bw@connected-linear-tiling-4-displays-2160x1440p:
- shard-bmg: NOTRUN -> [SKIP][17] ([Intel XE#2314] / [Intel XE#2894])
[17]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@[email protected]
- shard-dg2-set2: NOTRUN -> [SKIP][18] ([Intel XE#2191])
[18]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]

* igt@kms_ccs@ccs-on-another-bo-4-tiled-mtl-rc-ccs-cc:
- shard-lnl: NOTRUN -> [SKIP][19] ([Intel XE#2887]) +1 other test skip
[19]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-2/igt@[email protected]

* igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-mc-ccs@pipe-d-dp-4:
- shard-dg2-set2: [PASS][20] -> [INCOMPLETE][21] ([Intel XE#3862]) +1 other test incomplete
[20]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-464/igt@kms_ccs@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@kms_ccs@[email protected]

* igt@kms_ccs@crc-primary-suspend-4-tiled-mtl-mc-ccs:
- shard-bmg: NOTRUN -> [SKIP][22] ([Intel XE#3432]) +1 other test skip
[22]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][23] ([Intel XE#3432])
[23]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-6/igt@[email protected]

* igt@kms_ccs@crc-primary-suspend-4-tiled-mtl-rc-ccs@pipe-a-hdmi-a-2:
- shard-dg2-set2: NOTRUN -> [SKIP][24] ([Intel XE#787]) +209 other tests skip
[24]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@kms_ccs@[email protected]

* igt@kms_ccs@missing-ccs-buffer-4-tiled-mtl-mc-ccs@pipe-d-dp-4:
- shard-dg2-set2: NOTRUN -> [SKIP][25] ([Intel XE#455] / [Intel XE#787]) +33 other tests skip
[25]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@kms_ccs@[email protected]

* igt@kms_ccs@random-ccs-data-4-tiled-dg2-mc-ccs:
- shard-bmg: NOTRUN -> [SKIP][26] ([Intel XE#2887]) +4 other tests skip
[26]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-4/igt@[email protected]

* igt@kms_ccs@random-ccs-data-4-tiled-dg2-mc-ccs@pipe-a-dp-4:
- shard-dg2-set2: NOTRUN -> [INCOMPLETE][27] ([Intel XE#2705] / [Intel XE#4212]) +2 other tests incomplete
[27]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@kms_ccs@[email protected]

* igt@kms_cdclk@mode-transition-all-outputs:
- shard-bmg: NOTRUN -> [SKIP][28] ([Intel XE#2724])
[28]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-7/igt@[email protected]
- shard-dg2-set2: NOTRUN -> [SKIP][29] ([Intel XE#4418])
[29]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-466/igt@[email protected]

* igt@kms_cdclk@mode-transition@pipe-a-dp-2:
- shard-dg2-set2: NOTRUN -> [SKIP][30] ([Intel XE#4417]) +3 other tests skip
[30]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@kms_cdclk@[email protected]

* igt@kms_chamelium_edid@dp-edid-stress-resolution-4k:
- shard-bmg: NOTRUN -> [SKIP][31] ([Intel XE#2252]) +5 other tests skip
[31]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][32] ([Intel XE#373]) +1 other test skip
[32]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-2/igt@[email protected]

* igt@kms_chamelium_frames@hdmi-crc-nonplanar-formats:
- shard-dg2-set2: NOTRUN -> [SKIP][33] ([Intel XE#373]) +5 other tests skip
[33]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]

* igt@kms_content_protection@atomic:
- shard-bmg: NOTRUN -> [FAIL][34] ([Intel XE#1178]) +3 other tests fail
[34]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][35] ([Intel XE#3278])
[35]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-2/igt@[email protected]

* igt@kms_content_protection@lic-type-0:
- shard-dg2-set2: NOTRUN -> [FAIL][36] ([Intel XE#1178]) +4 other tests fail
[36]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]
- shard-bmg: NOTRUN -> [SKIP][37] ([Intel XE#2341])
[37]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]

* igt@kms_content_protection@lic-type-0@pipe-a-dp-4:
- shard-dg2-set2: NOTRUN -> [FAIL][38] ([Intel XE#3304])
[38]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@kms_content_protection@[email protected]

* igt@kms_cursor_crc@cursor-offscreen-512x512:
- shard-dg2-set2: NOTRUN -> [SKIP][39] ([Intel XE#308])
[39]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][40] ([Intel XE#2321])
[40]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-8/igt@[email protected]
- shard-bmg: NOTRUN -> [SKIP][41] ([Intel XE#2321])
[41]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-4/igt@[email protected]

* igt@kms_cursor_crc@cursor-rapid-movement-256x85:
- shard-lnl: NOTRUN -> [SKIP][42] ([Intel XE#1424]) +1 other test skip
[42]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-8/igt@[email protected]

* igt@kms_cursor_crc@cursor-sliding-64x21:
- shard-bmg: NOTRUN -> [SKIP][43] ([Intel XE#2320]) +2 other tests skip
[43]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@[email protected]

* igt@kms_cursor_legacy@2x-cursor-vs-flip-legacy:
- shard-lnl: NOTRUN -> [SKIP][44] ([Intel XE#309])
[44]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-5/igt@[email protected]

* igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size:
- shard-bmg: [PASS][45] -> [DMESG-WARN][46] ([Intel XE#5354])
[45]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-4/igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size.html
[46]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size.html

* igt@kms_cursor_legacy@cursorb-vs-flipa-legacy:
- shard-bmg: [PASS][47] -> [SKIP][48] ([Intel XE#2291]) +3 other tests skip
[47]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-7/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]

* igt@kms_dither@fb-8bpc-vs-panel-6bpc@pipe-a-hdmi-a-6:
- shard-dg2-set2: NOTRUN -> [SKIP][49] ([Intel XE#4494] / [i915#3804])
[49]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@kms_dither@[email protected]

* igt@kms_dp_link_training@uhbr-sst:
- shard-dg2-set2: NOTRUN -> [SKIP][50] ([Intel XE#4356])
[50]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][51] ([Intel XE#4354])
[51]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-2/igt@[email protected]

* igt@kms_dsc@dsc-with-bpc:
- shard-dg2-set2: NOTRUN -> [SKIP][52] ([Intel XE#455]) +7 other tests skip
[52]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-466/igt@[email protected]
- shard-bmg: NOTRUN -> [SKIP][53] ([Intel XE#2244])
[53]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-7/igt@[email protected]

* igt@kms_fbcon_fbt@psr:
- shard-bmg: NOTRUN -> [SKIP][54] ([Intel XE#776])
[54]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-4/igt@[email protected]

* igt@kms_flip@2x-plain-flip-fb-recreate:
- shard-bmg: [PASS][55] -> [SKIP][56] ([Intel XE#2316]) +4 other tests skip
[55]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-2/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]

* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-lnl: [PASS][57] -> [FAIL][58] ([Intel XE#301]) +2 other tests fail
[57]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-lnl-5/igt@kms_flip@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-2/igt@kms_flip@[email protected]

* igt@kms_flip@flip-vs-suspend:
- shard-dg2-set2: NOTRUN -> [INCOMPLETE][59] ([Intel XE#2049] / [Intel XE#2597]) +1 other test incomplete
[59]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]

* igt@kms_flip@plain-flip-fb-recreate:
- shard-bmg: [PASS][60] -> [FAIL][61] ([Intel XE#2882]) +2 other tests fail
[60]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-7/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-8/igt@[email protected]

* igt@kms_flip@plain-flip-fb-recreate@a-edp1:
- shard-lnl: [PASS][62] -> [FAIL][63] ([Intel XE#886]) +1 other test fail
[62]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-lnl-6/igt@kms_flip@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-7/igt@kms_flip@[email protected]

* igt@kms_flip@wf_vblank-ts-check-interruptible@a-hdmi-a2:
- shard-dg2-set2: [PASS][64] -> [FAIL][65] ([Intel XE#2882] / [Intel XE#886]) +1 other test fail
[64]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-432/igt@kms_flip@[email protected]
[65]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@kms_flip@[email protected]

* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode:
- shard-bmg: NOTRUN -> [SKIP][66] ([Intel XE#2293]) +1 other test skip
[66]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-4/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode.html

* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling:
- shard-lnl: NOTRUN -> [SKIP][67] ([Intel XE#1397] / [Intel XE#1745])
[67]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-5/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling.html

* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling@pipe-a-default-mode:
- shard-lnl: NOTRUN -> [SKIP][68] ([Intel XE#1397])
[68]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-5/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling@pipe-a-default-mode.html

* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-upscaling:
- shard-bmg: NOTRUN -> [SKIP][69] ([Intel XE#2293] / [Intel XE#2380]) +1 other test skip
[69]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-7/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-upscaling.html
- shard-lnl: NOTRUN -> [SKIP][70] ([Intel XE#1401] / [Intel XE#1745])
[70]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-1/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-upscaling.html

* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-upscaling@pipe-a-default-mode:
- shard-lnl: NOTRUN -> [SKIP][71] ([Intel XE#1401])
[71]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-1/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-upscaling@pipe-a-default-mode.html

* igt@kms_frontbuffer_tracking@drrs-rgb101010-draw-mmap-wc:
- shard-dg2-set2: NOTRUN -> [SKIP][72] ([Intel XE#651]) +23 other tests skip
[72]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]

* igt@kms_frontbuffer_tracking@drrs-rgb101010-draw-render:
- shard-bmg: NOTRUN -> [SKIP][73] ([Intel XE#2311]) +17 other tests skip
[73]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-7/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-pgflip-blt:
- shard-bmg: NOTRUN -> [SKIP][74] ([Intel XE#4141]) +5 other tests skip
[74]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-render:
- shard-lnl: NOTRUN -> [SKIP][75] ([Intel XE#656]) +8 other tests skip
[75]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-5/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-render.html

* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-fullscreen:
- shard-bmg: NOTRUN -> [SKIP][76] ([Intel XE#2312]) +2 other tests skip
[76]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-fullscreen.html

* igt@kms_frontbuffer_tracking@fbcdrrs-slowdraw:
- shard-lnl: NOTRUN -> [SKIP][77] ([Intel XE#651]) +5 other tests skip
[77]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-7/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbcdrrs-tiling-y:
- shard-dg2-set2: NOTRUN -> [SKIP][78] ([Intel XE#658])
[78]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbcpsr-indfb-scaledprimary:
- shard-bmg: NOTRUN -> [SKIP][79] ([Intel XE#2313]) +10 other tests skip
[79]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-7/igt@[email protected]

* igt@kms_frontbuffer_tracking@psr-2p-primscrn-spr-indfb-move:
- shard-dg2-set2: NOTRUN -> [SKIP][80] ([Intel XE#653]) +12 other tests skip
[80]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]

* igt@kms_hdr@static-swap:
- shard-bmg: [PASS][81] -> [SKIP][82] ([Intel XE#1503])
[81]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-3/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]

* igt@kms_joiner@invalid-modeset-big-joiner:
- shard-bmg: NOTRUN -> [SKIP][83] ([Intel XE#346])
[83]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-8/igt@[email protected]
- shard-dg2-set2: NOTRUN -> [SKIP][84] ([Intel XE#346])
[84]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][85] ([Intel XE#346])
[85]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-7/igt@[email protected]

* igt@kms_panel_fitting@legacy:
- shard-bmg: NOTRUN -> [SKIP][86] ([Intel XE#2486])
[86]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]

* igt@kms_plane_scaling@planes-downscale-factor-0-5:
- shard-lnl: NOTRUN -> [SKIP][87] ([Intel XE#2763]) +3 other tests skip
[87]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-7/igt@[email protected]

* igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-c:
- shard-bmg: NOTRUN -> [SKIP][88] ([Intel XE#2763]) +4 other tests skip
[88]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@kms_plane_scaling@[email protected]

* igt@kms_pm_dc@dc5-dpms-negative:
- shard-lnl: NOTRUN -> [SKIP][89] ([Intel XE#1131])
[89]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-2/igt@[email protected]

* igt@kms_pm_dc@dc6-psr:
- shard-lnl: [PASS][90] -> [FAIL][91] ([Intel XE#718])
[90]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-lnl-1/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-4/igt@[email protected]

* igt@kms_psr2_sf@fbc-pr-overlay-plane-move-continuous-exceed-fully-sf:
- shard-dg2-set2: NOTRUN -> [SKIP][92] ([Intel XE#1489]) +6 other tests skip
[92]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@kms_psr2_sf@fbc-pr-overlay-plane-move-continuous-exceed-fully-sf.html
- shard-lnl: NOTRUN -> [SKIP][93] ([Intel XE#2893])
[93]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-4/igt@kms_psr2_sf@fbc-pr-overlay-plane-move-continuous-exceed-fully-sf.html

* igt@kms_psr2_sf@fbc-psr2-plane-move-sf-dmg-area:
- shard-lnl: NOTRUN -> [SKIP][94] ([Intel XE#2893] / [Intel XE#4608])
[94]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-1/igt@[email protected]

* igt@kms_psr2_sf@fbc-psr2-plane-move-sf-dmg-area@pipe-b-edp-1:
- shard-lnl: NOTRUN -> [SKIP][95] ([Intel XE#4608]) +2 other tests skip
[95]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-1/igt@kms_psr2_sf@[email protected]

* igt@kms_psr2_sf@psr2-overlay-plane-move-continuous-exceed-fully-sf:
- shard-bmg: NOTRUN -> [SKIP][96] ([Intel XE#1489]) +7 other tests skip
[96]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@kms_psr2_sf@psr2-overlay-plane-move-continuous-exceed-fully-sf.html

* igt@kms_psr@fbc-pr-primary-page-flip:
- shard-lnl: NOTRUN -> [SKIP][97] ([Intel XE#1406])
[97]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-4/igt@[email protected]

* igt@kms_psr@psr2-primary-blt:
- shard-bmg: NOTRUN -> [SKIP][98] ([Intel XE#2234] / [Intel XE#2850]) +4 other tests skip
[98]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@[email protected]

* igt@kms_psr@psr2-sprite-blt:
- shard-dg2-set2: NOTRUN -> [SKIP][99] ([Intel XE#2850] / [Intel XE#929]) +4 other tests skip
[99]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]

* igt@kms_rotation_crc@primary-x-tiled-reflect-x-0:
- shard-lnl: NOTRUN -> [FAIL][100] ([Intel XE#4689])
[100]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-1/igt@[email protected]

* igt@kms_rotation_crc@primary-y-tiled-reflect-x-90:
- shard-dg2-set2: NOTRUN -> [SKIP][101] ([Intel XE#3414]) +2 other tests skip
[101]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]

* igt@kms_rotation_crc@sprite-rotation-90-pos-100-0:
- shard-bmg: NOTRUN -> [SKIP][102] ([Intel XE#3414] / [Intel XE#3904]) +1 other test skip
[102]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-8/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][103] ([Intel XE#3414] / [Intel XE#3904])
[103]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-6/igt@[email protected]

* igt@kms_setmode@invalid-clone-single-crtc:
- shard-bmg: [PASS][104] -> [SKIP][105] ([Intel XE#1435])
[104]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-3/igt@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]

* igt@kms_tiled_display@basic-test-pattern:
- shard-bmg: NOTRUN -> [SKIP][106] ([Intel XE#2426])
[106]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@[email protected]
- shard-dg2-set2: NOTRUN -> [FAIL][107] ([Intel XE#1729])
[107]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-466/igt@[email protected]

* igt@kms_vrr@max-min:
- shard-bmg: NOTRUN -> [SKIP][108] ([Intel XE#1499])
[108]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@[email protected]

* igt@xe_create@multigpu-create-massive-size:
- shard-bmg: NOTRUN -> [SKIP][109] ([Intel XE#2504])
[109]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@[email protected]
- shard-lnl: NOTRUN -> [SKIP][110] ([Intel XE#944])
[110]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-4/igt@[email protected]

* igt@xe_eu_stall@invalid-gt-id:
- shard-dg2-set2: NOTRUN -> [SKIP][111] ([Intel XE#5308])
[111]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]

* igt@xe_eudebug@basic-read-event:
- shard-bmg: NOTRUN -> [SKIP][112] ([Intel XE#4837]) +8 other tests skip
[112]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-8/igt@[email protected]

* igt@xe_eudebug@basic-vm-bind-ufence-delay-ack:
- shard-dg2-set2: NOTRUN -> [SKIP][113] ([Intel XE#4837]) +12 other tests skip
[113]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]

* igt@xe_eudebug_online@basic-breakpoint:
- shard-lnl: NOTRUN -> [SKIP][114] ([Intel XE#4837]) +3 other tests skip
[114]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-3/igt@[email protected]

* igt@xe_evict_ccs@evict-overcommit-parallel-nofree-reopen:
- shard-lnl: NOTRUN -> [SKIP][115] ([Intel XE#688])
[115]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-1/igt@[email protected]

* igt@xe_exec_basic@multigpu-many-execqueues-many-vm-basic-defer-mmap:
- shard-bmg: NOTRUN -> [SKIP][116] ([Intel XE#2322]) +6 other tests skip
[116]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@xe_exec_basic@multigpu-many-execqueues-many-vm-basic-defer-mmap.html
- shard-dg2-set2: NOTRUN -> [SKIP][117] ([Intel XE#1392]) +2 other tests skip
[117]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@xe_exec_basic@multigpu-many-execqueues-many-vm-basic-defer-mmap.html
- shard-lnl: NOTRUN -> [SKIP][118] ([Intel XE#1392]) +3 other tests skip
[118]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-2/igt@xe_exec_basic@multigpu-many-execqueues-many-vm-basic-defer-mmap.html

* igt@xe_exec_basic@multigpu-once-basic-defer-mmap:
- shard-dg2-set2: [PASS][119] -> [SKIP][120] ([Intel XE#1392]) +8 other tests skip
[119]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-435/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]

* igt@xe_exec_fault_mode@once-bindexecqueue-imm:
- shard-dg2-set2: NOTRUN -> [SKIP][121] ([Intel XE#288]) +13 other tests skip
[121]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]

* igt@xe_exec_mix_modes@exec-simple-batch-store-dma-fence:
- shard-dg2-set2: NOTRUN -> [SKIP][122] ([Intel XE#2360])
[122]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@[email protected]

* igt@xe_exec_system_allocator@many-large-malloc-nomemset:
- shard-dg2-set2: NOTRUN -> [SKIP][123] ([Intel XE#4915]) +134 other tests skip
[123]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-466/igt@[email protected]

* igt@xe_exec_system_allocator@threads-many-mmap-new-huge-nomemset:
- shard-bmg: NOTRUN -> [SKIP][124] ([Intel XE#4943]) +14 other tests skip
[124]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@xe_exec_system_allocator@threads-many-mmap-new-huge-nomemset.html

* igt@xe_exec_system_allocator@threads-shared-vm-many-stride-mmap-huge:
- shard-lnl: NOTRUN -> [SKIP][125] ([Intel XE#4943]) +8 other tests skip
[125]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-6/igt@xe_exec_system_allocator@threads-shared-vm-many-stride-mmap-huge.html

* igt@xe_exec_threads@threads-hang-rebind-err:
- shard-dg2-set2: [PASS][126] -> [DMESG-WARN][127] ([Intel XE#3876])
[126]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-435/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]

* igt@xe_huc_copy@huc_copy:
- shard-dg2-set2: NOTRUN -> [SKIP][128] ([Intel XE#255])
[128]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-466/igt@xe_huc_copy@huc_copy.html

* igt@xe_live_ktest@xe_eudebug:
- shard-bmg: NOTRUN -> [SKIP][129] ([Intel XE#2833])
[129]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@xe_live_ktest@xe_eudebug.html

* igt@xe_oa@non-privileged-access-vaddr:
- shard-dg2-set2: NOTRUN -> [SKIP][130] ([Intel XE#2541] / [Intel XE#3573]) +2 other tests skip
[130]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]

* igt@xe_oa@syncs-ufence-wait-cfg:
- shard-dg2-set2: NOTRUN -> [SKIP][131] ([Intel XE#2541] / [Intel XE#3573] / [Intel XE#4501])
[131]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]

* igt@xe_pm@d3cold-basic-exec:
- shard-dg2-set2: NOTRUN -> [SKIP][132] ([Intel XE#2284] / [Intel XE#366]) +1 other test skip
[132]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]

* igt@xe_pm@s2idle-d3cold-basic-exec:
- shard-bmg: NOTRUN -> [SKIP][133] ([Intel XE#2284]) +2 other tests skip
[133]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-4/igt@[email protected]

* igt@xe_pm@s4-d3cold-basic-exec:
- shard-lnl: NOTRUN -> [SKIP][134] ([Intel XE#2284] / [Intel XE#366])
[134]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-7/igt@[email protected]

* igt@xe_pm_residency@cpg-basic:
- shard-lnl: NOTRUN -> [SKIP][135] ([Intel XE#584])
[135]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-2/igt@[email protected]

* igt@xe_pxp@pxp-termination-key-update-post-suspend:
- shard-bmg: NOTRUN -> [SKIP][136] ([Intel XE#4733]) +2 other tests skip
[136]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@[email protected]
- shard-dg2-set2: NOTRUN -> [SKIP][137] ([Intel XE#4733]) +2 other tests skip
[137]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]

* igt@xe_query@multigpu-query-uc-fw-version-guc:
- shard-dg2-set2: NOTRUN -> [SKIP][138] ([Intel XE#944]) +2 other tests skip
[138]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]
- shard-bmg: NOTRUN -> [SKIP][139] ([Intel XE#944])
[139]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]

* igt@xe_sriov_auto_provisioning@resources-released-on-vfs-disabling:
- shard-bmg: NOTRUN -> [SKIP][140] ([Intel XE#4130])
[140]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@xe_sriov_auto_provisioning@resources-released-on-vfs-disabling.html
- shard-dg2-set2: NOTRUN -> [SKIP][141] ([Intel XE#4130])
[141]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@xe_sriov_auto_provisioning@resources-released-on-vfs-disabling.html

* igt@xe_wedged@wedged-mode-toggle:
- shard-dg2-set2: [PASS][142] -> [DMESG-WARN][143] ([Intel XE#4792])
[142]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-463/igt@[email protected]
[143]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]
- shard-lnl: [PASS][144] -> [DMESG-WARN][145] ([Intel XE#4792])
[144]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-lnl-6/igt@[email protected]
[145]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-1/igt@[email protected]

#### Possible fixes ####

* igt@kms_async_flips@async-flip-with-page-flip-events-linear-atomic@pipe-c-edp-1:
- shard-lnl: [FAIL][146] ([Intel XE#911]) -> [PASS][147] +3 other tests pass
[146]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-lnl-2/igt@kms_async_flips@[email protected]
[147]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-5/igt@kms_async_flips@[email protected]

* igt@kms_ccs@crc-sprite-planes-basic-4-tiled-bmg-ccs@pipe-a-dp-2:
- shard-bmg: [FAIL][148] ([Intel XE#5376]) -> [PASS][149] +1 other test pass
[148]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-1/igt@kms_ccs@[email protected]
[149]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-8/igt@kms_ccs@[email protected]

* igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc:
- shard-dg2-set2: [INCOMPLETE][150] ([Intel XE#1727] / [Intel XE#3113] / [Intel XE#3124]) -> [PASS][151] +1 other test pass
[150]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-433/igt@[email protected]
[151]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@[email protected]

* igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc@pipe-c-dp-4:
- shard-dg2-set2: [INCOMPLETE][152] ([Intel XE#3124]) -> [PASS][153]
[152]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-433/igt@kms_ccs@[email protected]
[153]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@kms_ccs@[email protected]

* igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc@pipe-c-hdmi-a-6:
- shard-dg2-set2: [DMESG-WARN][154] ([Intel XE#1727] / [Intel XE#3113]) -> [PASS][155]
[154]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-433/igt@kms_ccs@[email protected]
[155]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@kms_ccs@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor-atomic:
- shard-bmg: [FAIL][156] ([Intel XE#4633]) -> [PASS][157]
[156]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-6/igt@[email protected]
[157]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-1/igt@[email protected]

* igt@kms_dither@fb-8bpc-vs-panel-6bpc:
- shard-bmg: [SKIP][158] ([Intel XE#1340]) -> [PASS][159]
[158]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-6/igt@[email protected]
[159]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-2/igt@[email protected]

* igt@kms_flip@2x-single-buffer-flip-vs-dpms-off-vs-modeset:
- shard-bmg: [SKIP][160] ([Intel XE#2316]) -> [PASS][161] +1 other test pass
[160]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-6/igt@[email protected]
[161]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-1/igt@[email protected]

* igt@kms_joiner@basic-force-big-joiner:
- shard-bmg: [SKIP][162] ([Intel XE#3012]) -> [PASS][163]
[162]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-6/igt@[email protected]
[163]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-4/igt@[email protected]

* igt@kms_setmode@basic@pipe-b-edp-1:
- shard-lnl: [FAIL][164] ([Intel XE#2883]) -> [PASS][165] +2 other tests pass
[164]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-lnl-1/igt@kms_setmode@[email protected]
[165]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-6/igt@kms_setmode@[email protected]

* igt@kms_setmode@invalid-clone-single-crtc-stealing:
- shard-bmg: [SKIP][166] ([Intel XE#1435]) -> [PASS][167]
[166]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-6/igt@[email protected]
[167]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-4/igt@[email protected]

* igt@xe_exec_basic@multigpu-many-execqueues-many-vm-bindexecqueue-userptr:
- shard-dg2-set2: [SKIP][168] ([Intel XE#1392]) -> [PASS][169] +4 other tests pass
[168]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-432/igt@xe_exec_basic@multigpu-many-execqueues-many-vm-bindexecqueue-userptr.html
[169]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@xe_exec_basic@multigpu-many-execqueues-many-vm-bindexecqueue-userptr.html

* igt@xe_exec_reset@parallel-gt-reset:
- shard-bmg: [DMESG-WARN][170] ([Intel XE#3876]) -> [PASS][171]
[170]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-1/igt@[email protected]
[171]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-7/igt@[email protected]
- shard-dg2-set2: [DMESG-WARN][172] ([Intel XE#3876]) -> [PASS][173]
[172]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-435/igt@[email protected]
[173]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]

* igt@xe_exec_system_allocator@threads-shared-vm-many-execqueues-new-bo-map-nomemset:
- shard-lnl: [FAIL][174] ([Intel XE#5165]) -> [PASS][175]
[174]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-lnl-6/igt@xe_exec_system_allocator@threads-shared-vm-many-execqueues-new-bo-map-nomemset.html
[175]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-1/igt@xe_exec_system_allocator@threads-shared-vm-many-execqueues-new-bo-map-nomemset.html

* igt@xe_module_load@load:
- shard-dg2-set2: ([PASS][176], [PASS][177], [PASS][178], [PASS][179], [PASS][180], [PASS][181], [PASS][182], [PASS][183], [PASS][184], [PASS][185], [PASS][186], [PASS][187], [PASS][188], [SKIP][189], [PASS][190], [PASS][191], [PASS][192], [PASS][193], [PASS][194], [PASS][195], [PASS][196], [PASS][197], [PASS][198], [PASS][199], [PASS][200], [PASS][201]) ([Intel XE#378]) -> ([PASS][202], [PASS][203], [PASS][204], [PASS][205], [PASS][206], [PASS][207], [PASS][208], [PASS][209], [PASS][210], [PASS][211], [PASS][212], [PASS][213], [PASS][214], [PASS][215], [PASS][216], [PASS][217], [PASS][218], [PASS][219], [PASS][220], [PASS][221], [PASS][222], [PASS][223], [PASS][224], [PASS][225], [PASS][226])
[176]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-435/igt@[email protected]
[177]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-466/igt@[email protected]
[178]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-464/igt@[email protected]
[179]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-466/igt@[email protected]
[180]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-466/igt@[email protected]
[181]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-466/igt@[email protected]
[182]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-464/igt@[email protected]
[183]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-464/igt@[email protected]
[184]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-464/igt@[email protected]
[185]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-463/igt@[email protected]
[186]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-464/igt@[email protected]
[187]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-463/igt@[email protected]
[188]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-463/igt@[email protected]
[189]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-435/igt@[email protected]
[190]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-435/igt@[email protected]
[191]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-463/igt@[email protected]
[192]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-433/igt@[email protected]
[193]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-433/igt@[email protected]
[194]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-435/igt@[email protected]
[195]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-435/igt@[email protected]
[196]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-435/igt@[email protected]
[197]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-432/igt@[email protected]
[198]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-432/igt@[email protected]
[199]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-432/igt@[email protected]
[200]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-432/igt@[email protected]
[201]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-433/igt@[email protected]
[202]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@[email protected]
[203]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@[email protected]
[204]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@[email protected]
[205]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@[email protected]
[206]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-435/igt@[email protected]
[207]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-466/igt@[email protected]
[208]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-466/igt@[email protected]
[209]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-466/igt@[email protected]
[210]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-466/igt@[email protected]
[211]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]
[212]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]
[213]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]
[214]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]
[215]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]
[216]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]
[217]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]
[218]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]
[219]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]
[220]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]
[221]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-433/igt@[email protected]
[222]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]
[223]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]
[224]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]
[225]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-464/igt@[email protected]
[226]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]

* igt@xe_pm@s4-vm-bind-prefetch:
- shard-bmg: [ABORT][227] ([Intel XE#5255]) -> [PASS][228]
[227]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-6/igt@[email protected]
[228]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-8/igt@[email protected]

* igt@xe_pm_residency@cpg-basic:
- shard-dg2-set2: [TIMEOUT][229] ([Intel XE#5328]) -> [PASS][230]
[229]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-463/igt@[email protected]
[230]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]

* igt@xe_pmu@gt-frequency:
- shard-lnl: [FAIL][231] ([Intel XE#4835]) -> [PASS][232] +1 other test pass
[231]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-lnl-5/igt@[email protected]
[232]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-lnl-3/igt@[email protected]

#### Warnings ####

* igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs:
- shard-dg2-set2: [INCOMPLETE][233] ([Intel XE#1727] / [Intel XE#3113] / [Intel XE#3124]) -> [INCOMPLETE][234] ([Intel XE#2705] / [Intel XE#4212] / [Intel XE#4345])
[233]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-464/igt@[email protected]
[234]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-463/igt@[email protected]

* igt@kms_frontbuffer_tracking@drrs-2p-primscrn-pri-indfb-draw-mmap-wc:
- shard-bmg: [SKIP][235] ([Intel XE#2311]) -> [SKIP][236] ([Intel XE#2312]) +10 other tests skip
[235]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-2/igt@kms_frontbuffer_tracking@drrs-2p-primscrn-pri-indfb-draw-mmap-wc.html
[236]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@kms_frontbuffer_tracking@drrs-2p-primscrn-pri-indfb-draw-mmap-wc.html

* igt@kms_frontbuffer_tracking@drrs-2p-primscrn-pri-shrfb-draw-blt:
- shard-bmg: [SKIP][237] ([Intel XE#2312]) -> [SKIP][238] ([Intel XE#2311]) +1 other test skip
[237]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-6/igt@kms_frontbuffer_tracking@drrs-2p-primscrn-pri-shrfb-draw-blt.html
[238]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@kms_frontbuffer_tracking@drrs-2p-primscrn-pri-shrfb-draw-blt.html

* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-mmap-wc:
- shard-bmg: [SKIP][239] ([Intel XE#2312]) -> [SKIP][240] ([Intel XE#4141]) +3 other tests skip
[239]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-6/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-mmap-wc.html
[240]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-7/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-mmap-wc.html

* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-onoff:
- shard-bmg: [SKIP][241] ([Intel XE#4141]) -> [SKIP][242] ([Intel XE#2312]) +2 other tests skip
[241]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-2/igt@[email protected]
[242]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-blt:
- shard-bmg: [SKIP][243] ([Intel XE#2313]) -> [SKIP][244] ([Intel XE#2312]) +8 other tests skip
[243]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-8/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-blt.html
[244]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-6/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-blt.html

* igt@kms_frontbuffer_tracking@psr-2p-primscrn-cur-indfb-onoff:
- shard-bmg: [SKIP][245] ([Intel XE#2312]) -> [SKIP][246] ([Intel XE#2313]) +2 other tests skip
[245]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-6/igt@[email protected]
[246]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-3/igt@[email protected]

* igt@kms_tiled_display@basic-test-pattern-with-chamelium:
- shard-bmg: [SKIP][247] ([Intel XE#2509]) -> [SKIP][248] ([Intel XE#2426])
[247]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-bmg-1/igt@[email protected]
[248]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-bmg-7/igt@[email protected]

* igt@xe_peer2peer@write:
- shard-dg2-set2: [FAIL][249] ([Intel XE#1173]) -> [SKIP][250] ([Intel XE#1061])
[249]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8432/shard-dg2-433/igt@[email protected]
[250]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/shard-dg2-432/igt@[email protected]

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

[Intel XE#1061]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1061
[Intel XE#1124]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1124
[Intel XE#1131]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1131
[Intel XE#1173]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1173
[Intel XE#1178]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1178
[Intel XE#1340]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1340
[Intel XE#1392]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1392
[Intel XE#1397]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1397
[Intel XE#1401]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1401
[Intel XE#1406]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1406
[Intel XE#1407]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1407
[Intel XE#1424]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1424
[Intel XE#1435]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1435
[Intel XE#1466]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1466
[Intel XE#1489]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1489
[Intel XE#1499]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1499
[Intel XE#1503]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1503
[Intel XE#1727]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1727
[Intel XE#1729]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1729
[Intel XE#1745]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1745
[Intel XE#2049]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2049
[Intel XE#2191]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2191
[Intel XE#2233]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2233
[Intel XE#2234]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2234
[Intel XE#2244]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2244
[Intel XE#2252]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2252
[Intel XE#2284]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2284
[Intel XE#2291]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2291
[Intel XE#2293]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2293
[Intel XE#2311]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2311
[Intel XE#2312]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2312
[Intel XE#2313]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2313
[Intel XE#2314]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2314
[Intel XE#2316]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2316
[Intel XE#2320]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2320
[Intel XE#2321]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2321
[Intel XE#2322]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2322
[Intel XE#2327]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2327
[Intel XE#2341]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2341
[Intel XE#2360]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2360
[Intel XE#2380]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2380
[Intel XE#2426]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2426
[Intel XE#2486]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2486
[Intel XE#2504]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2504
[Intel XE#2509]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2509
[Intel XE#2541]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2541
[Intel XE#255]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/255
[Intel XE#2597]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2597
[Intel XE#2705]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2705
[Intel XE#2724]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2724
[Intel XE#2763]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2763
[Intel XE#2833]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2833
[Intel XE#2850]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2850
[Intel XE#288]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/288
[Intel XE#2882]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2882
[Intel XE#2883]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2883
[Intel XE#2887]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2887
[Intel XE#2893]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2893
[Intel XE#2894]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2894
[Intel XE#301]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/301
[Intel XE#3012]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3012
[Intel XE#308]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/308
[Intel XE#309]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/309
[Intel XE#3113]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3113
[Intel XE#3124]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3124
[Intel XE#3278]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3278
[Intel XE#3304]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3304
[Intel XE#3414]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3414
[Intel XE#3432]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3432
[Intel XE#346]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/346
[Intel XE#3573]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3573
[Intel XE#366]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/366
[Intel XE#373]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/373
[Intel XE#3768]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3768
[Intel XE#378]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/378
[Intel XE#3862]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3862
[Intel XE#3876]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3876
[Intel XE#3904]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3904
[Intel XE#4130]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4130
[Intel XE#4141]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4141
[Intel XE#4212]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4212
[Intel XE#4345]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4345
[Intel XE#4354]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4354
[Intel XE#4356]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4356
[Intel XE#4417]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4417
[Intel XE#4418]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4418
[Intel XE#4494]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4494
[Intel XE#4501]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4501
[Intel XE#455]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/455
[Intel XE#4608]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4608
[Intel XE#4633]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4633
[Intel XE#4665]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4665
[Intel XE#4689]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4689
[Intel XE#4733]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4733
[Intel XE#4792]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4792
[Intel XE#4835]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4835
[Intel XE#4837]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4837
[Intel XE#4847]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4847
[Intel XE#4915]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4915
[Intel XE#4943]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4943
[Intel XE#5165]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5165
[Intel XE#5255]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5255
[Intel XE#5300]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5300
[Intel XE#5308]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5308
[Intel XE#5328]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5328
[Intel XE#5354]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5354
[Intel XE#5376]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5376
[Intel XE#584]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/584
[Intel XE#623]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/623
[Intel XE#651]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/651
[Intel XE#653]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/653
[Intel XE#656]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/656
[Intel XE#658]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/658
[Intel XE#688]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/688
[Intel XE#718]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/718
[Intel XE#776]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/776
[Intel XE#787]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/787
[Intel XE#886]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/886
[Intel XE#911]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/911
[Intel XE#929]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/929
[Intel XE#944]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/944
[i915#3804]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3804

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

* IGT: IGT_8432 -> IGTPW_13374

IGTPW_13374: 13374
IGT_8432: 4871829d8b7117553eb2dc1bdb9a0d18de428a98 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
xe-3325-d9007d535ea106181346f9988c97aa73a9cdfb86: d9007d535ea106181346f9988c97aa73a9cdfb86

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13374/index.html