[PATCH i-g-t] tests/intel/xe_configfs: Check ctx_restore_post_bb

[PATCH i-g-t] tests/intel/xe_configfs: Check ctx_restore_post_bb

[Lucas De Marchi]

Add sanity checks for the values possibly written to
ctx_restore_post_bb, according to pending patch series:
https://lore.kernel.org/intel-xe/20250905-wa-bb-cmds-v3-0-3da2b7bdc73e@intel.com/

Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
 tests/intel/xe_configfs.c | 113 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 113 insertions(+)

diff --git a/tests/intel/xe_configfs.c b/tests/intel/xe_configfs.c
index 086f99ba5..d778065f3 100644
--- a/tests/intel/xe_configfs.c
+++ b/tests/intel/xe_configfs.c
@@ -122,6 +122,111 @@ static void test_engines_allowed(int configfs_device_fd)
 	}
 }
 
+/**
+ * SUBTEST: ctx-restore-post-bb-invalid
+ * Description: Validate ctx_restore_post_bb attribute for invalid values
+ */
+static void test_ctx_restore_post_bb_invalid(int configfs_device_fd)
+{
+	static const struct value {
+		const char *test;
+		const char *in;
+		const char *out;
+	} values[] = {
+		{ .test = "invalid-engine",
+		  .in = "foobar cmd 11000001 4F100 DEADBEEF",
+		},
+		{ .test = "invalid-type",
+		  .in = "rcs 11000001 4F100 DEADBEEF",
+		},
+		{ .test = "invalid-number",
+		  .in = "rcs cmd 1100000g 4F100 DEADBEEF",
+		},
+		{ .test = "invalid-number",
+		  .in = "rcs cmd 1100000g 4F100 DEADBEEF",
+		},
+		{ .test = "invalid-reg-addr-only",
+		  .in = "rcs reg 4F100",
+		},
+	};
+
+	/*
+	 * These only test if command parsing is correct,
+	 * so just make sure there's no device bound
+	 */
+	igt_kmod_unbind("xe", bus_addr);
+
+	for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
+		const struct value *v = &values[i];
+
+		igt_info("%s\n", v->test);
+		igt_debug("Test '%s' to ctx_restore_post_bb\n", v->in);
+		igt_assert(!igt_sysfs_set(configfs_device_fd,
+					  "ctx_restore_post_bb", v->in));
+	}
+}
+
+/**
+ * SUBTEST: ctx-restore-post-bb
+ * Description: Validate ctx_restore_post_bb attribute
+ */
+static void test_ctx_restore_post_bb(int configfs_device_fd)
+{
+	static const struct value {
+		const char *test;
+		const char *in;
+		const char *out;
+	} values[] = {
+		{ .test = "cmd-single",
+		  .in = "rcs cmd 11000001 4F100 DEADBEEF",
+		  .out = "rcs: 11000001 0004f100 deadbeef\n",
+		},
+		{ .test = "cmd-single-multi-values",
+		  .in = "rcs cmd 11000003 4F100 DEADBEEF 4F104 DEADBEEF",
+		  .out = "rcs: 11000003 0004f100 deadbeef 0004f104 deadbeef\n",
+		},
+		{ .test = "cmd-multi",
+		  .in = "rcs cmd 11000001 4F100 DEADBEEF\n"
+			"rcs cmd 11000001 4F104 FFFFFFFF",
+		  .out = "rcs: 11000001 0004f100 deadbeef 11000001 0004f104 ffffffff\n",
+		},
+		{ .test = "reg-single",
+		  .in = "rcs reg 4F100 DEADBEEF",
+		  .out = "rcs: 11000001 0004f100 deadbeef\n",
+		},
+		{ .test = "reg-multi",
+		  .in = "rcs reg 4F100 DEADBEEF\n"
+			"rcs reg 4F104 FFFFFFFF",
+		  .out = "rcs: 11000001 0004f100 deadbeef 11000001 0004f104 ffffffff\n",
+		},
+	};
+	char buf[4096] = { };
+
+	/*
+	 * These only test if command parsing is correct,
+	 * so just make sure there's no device bound
+	 */
+	igt_kmod_unbind("xe", bus_addr);
+
+	for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
+		const struct value *v = &values[i];
+
+		igt_info("%s\n", v->test);
+		igt_debug("Test '%s' to ctx_restore_post_bb\n", v->in);
+		igt_assert(igt_sysfs_set(configfs_device_fd,
+					 "ctx_restore_post_bb", v->in));
+
+		if (v->out) {
+			igt_assert(igt_sysfs_read(configfs_device_fd, "ctx_restore_post_bb", buf,
+						  sizeof(buf) - 1));
+			if (strcmp(v->out, buf)) {
+				igt_debug("Expecting '%s' but found '%s'", v->out, buf);
+				igt_fail(IGT_EXIT_FAILURE);
+			}
+		}
+	}
+}
+
 static void set_bus_addr(int fd)
 {
 	struct pci_device *pci_dev;
@@ -173,6 +278,14 @@ igt_main
 	igt_subtest("engines-allowed")
 		test_engines_allowed(configfs_device_fd);
 
+	igt_describe("Validate ctx_restore_post_bb with invalid options");
+	igt_subtest("ctx-restore-post-bb-invalid")
+		test_ctx_restore_post_bb_invalid(configfs_device_fd);
+
+	igt_describe("Validate ctx_restore_post_bb");
+	igt_subtest("ctx-restore-post-bb")
+		test_ctx_restore_post_bb(configfs_device_fd);
+
 	igt_fixture {
 		close(configfs_device_fd);
 		close(configfs_fd);
-- 
2.50.1

Re: [PATCH i-g-t] tests/intel/xe_configfs: Check ctx_restore_post_bb

[Rodrigo Vivi]

On Fri, Sep 05, 2025 at 10:52:21PM -0700, Lucas De Marchi wrote:
> Add sanity checks for the values possibly written to
> ctx_restore_post_bb, according to pending patch series:
> https://lore.kernel.org/intel-xe/20250905-wa-bb-cmds-v3-0-3da2b7bdc73e@intel.com/
> 
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
>  tests/intel/xe_configfs.c | 113 ++++++++++++++++++++++++++++++++++++++
>  1 file changed, 113 insertions(+)
> 
> diff --git a/tests/intel/xe_configfs.c b/tests/intel/xe_configfs.c
> index 086f99ba5..d778065f3 100644
> --- a/tests/intel/xe_configfs.c
> +++ b/tests/intel/xe_configfs.c
> @@ -122,6 +122,111 @@ static void test_engines_allowed(int configfs_device_fd)
>  	}
>  }
>  
> +/**
> + * SUBTEST: ctx-restore-post-bb-invalid
> + * Description: Validate ctx_restore_post_bb attribute for invalid values
> + */
> +static void test_ctx_restore_post_bb_invalid(int configfs_device_fd)
> +{
> +	static const struct value {
> +		const char *test;
> +		const char *in;
> +		const char *out;

you don't need the out here right?
or do you have plans to move the declaration out of the function?

> +	} values[] = {
> +		{ .test = "invalid-engine",
> +		  .in = "foobar cmd 11000001 4F100 DEADBEEF",
> +		},
> +		{ .test = "invalid-type",
> +		  .in = "rcs 11000001 4F100 DEADBEEF",
> +		},
> +		{ .test = "invalid-number",
> +		  .in = "rcs cmd 1100000g 4F100 DEADBEEF",
> +		},
> +		{ .test = "invalid-number",
> +		  .in = "rcs cmd 1100000g 4F100 DEADBEEF",
> +		},
> +		{ .test = "invalid-reg-addr-only",
> +		  .in = "rcs reg 4F100",
> +		},
> +	};
> +
> +	/*
> +	 * These only test if command parsing is correct,
> +	 * so just make sure there's no device bound
> +	 */
> +	igt_kmod_unbind("xe", bus_addr);
> +
> +	for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
> +		const struct value *v = &values[i];
> +
> +		igt_info("%s\n", v->test);
> +		igt_debug("Test '%s' to ctx_restore_post_bb\n", v->in);
> +		igt_assert(!igt_sysfs_set(configfs_device_fd,
> +					  "ctx_restore_post_bb", v->in));

worth binding the driver and reading the mmio register with intel_reg
and comparing with set value?

> +	}
> +}
> +
> +/**
> + * SUBTEST: ctx-restore-post-bb
> + * Description: Validate ctx_restore_post_bb attribute
> + */
> +static void test_ctx_restore_post_bb(int configfs_device_fd)
> +{
> +	static const struct value {
> +		const char *test;
> +		const char *in;
> +		const char *out;
> +	} values[] = {
> +		{ .test = "cmd-single",
> +		  .in = "rcs cmd 11000001 4F100 DEADBEEF",
> +		  .out = "rcs: 11000001 0004f100 deadbeef\n",
> +		},
> +		{ .test = "cmd-single-multi-values",
> +		  .in = "rcs cmd 11000003 4F100 DEADBEEF 4F104 DEADBEEF",
> +		  .out = "rcs: 11000003 0004f100 deadbeef 0004f104 deadbeef\n",
> +		},
> +		{ .test = "cmd-multi",
> +		  .in = "rcs cmd 11000001 4F100 DEADBEEF\n"
> +			"rcs cmd 11000001 4F104 FFFFFFFF",
> +		  .out = "rcs: 11000001 0004f100 deadbeef 11000001 0004f104 ffffffff\n",
> +		},
> +		{ .test = "reg-single",
> +		  .in = "rcs reg 4F100 DEADBEEF",
> +		  .out = "rcs: 11000001 0004f100 deadbeef\n",
> +		},
> +		{ .test = "reg-multi",
> +		  .in = "rcs reg 4F100 DEADBEEF\n"
> +			"rcs reg 4F104 FFFFFFFF",
> +		  .out = "rcs: 11000001 0004f100 deadbeef 11000001 0004f104 ffffffff\n",
> +		},
> +	};
> +	char buf[4096] = { };
> +
> +	/*
> +	 * These only test if command parsing is correct,
> +	 * so just make sure there's no device bound
> +	 */
> +	igt_kmod_unbind("xe", bus_addr);
> +
> +	for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
> +		const struct value *v = &values[i];
> +
> +		igt_info("%s\n", v->test);
> +		igt_debug("Test '%s' to ctx_restore_post_bb\n", v->in);
> +		igt_assert(igt_sysfs_set(configfs_device_fd,
> +					 "ctx_restore_post_bb", v->in));
> +
> +		if (v->out) {
> +			igt_assert(igt_sysfs_read(configfs_device_fd, "ctx_restore_post_bb", buf,
> +						  sizeof(buf) - 1));
> +			if (strcmp(v->out, buf)) {
> +				igt_debug("Expecting '%s' but found '%s'", v->out, buf);
> +				igt_fail(IGT_EXIT_FAILURE);
> +			}
> +		}
> +	}
> +}
> +
>  static void set_bus_addr(int fd)
>  {
>  	struct pci_device *pci_dev;
> @@ -173,6 +278,14 @@ igt_main
>  	igt_subtest("engines-allowed")
>  		test_engines_allowed(configfs_device_fd);
>  
> +	igt_describe("Validate ctx_restore_post_bb with invalid options");
> +	igt_subtest("ctx-restore-post-bb-invalid")
> +		test_ctx_restore_post_bb_invalid(configfs_device_fd);
> +
> +	igt_describe("Validate ctx_restore_post_bb");
> +	igt_subtest("ctx-restore-post-bb")
> +		test_ctx_restore_post_bb(configfs_device_fd);
> +
>  	igt_fixture {
>  		close(configfs_device_fd);
>  		close(configfs_fd);
> -- 
> 2.50.1
> 

Re: [PATCH i-g-t] tests/intel/xe_configfs: Check ctx_restore_post_bb

[Lucas De Marchi]

On Thu, Sep 18, 2025 at 03:17:41PM -0400, Rodrigo Vivi wrote:
>On Fri, Sep 05, 2025 at 10:52:21PM -0700, Lucas De Marchi wrote:
>> Add sanity checks for the values possibly written to
>> ctx_restore_post_bb, according to pending patch series:
>> https://lore.kernel.org/intel-xe/20250905-wa-bb-cmds-v3-0-3da2b7bdc73e@intel.com/
>>
>> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
>> ---
>>  tests/intel/xe_configfs.c | 113 ++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 113 insertions(+)
>>
>> diff --git a/tests/intel/xe_configfs.c b/tests/intel/xe_configfs.c
>> index 086f99ba5..d778065f3 100644
>> --- a/tests/intel/xe_configfs.c
>> +++ b/tests/intel/xe_configfs.c
>> @@ -122,6 +122,111 @@ static void test_engines_allowed(int configfs_device_fd)
>>  	}
>>  }
>>
>> +/**
>> + * SUBTEST: ctx-restore-post-bb-invalid
>> + * Description: Validate ctx_restore_post_bb attribute for invalid values
>> + */
>> +static void test_ctx_restore_post_bb_invalid(int configfs_device_fd)
>> +{
>> +	static const struct value {
>> +		const char *test;
>> +		const char *in;
>> +		const char *out;
>
>you don't need the out here right?

right, because in all of the invalid ones, it should be "".
It would be a good idea to read it first and then compare that none of
the writes go through and for that I don't need the variable here.

>or do you have plans to move the declaration out of the function?
>
>> +	} values[] = {
>> +		{ .test = "invalid-engine",
>> +		  .in = "foobar cmd 11000001 4F100 DEADBEEF",
>> +		},
>> +		{ .test = "invalid-type",
>> +		  .in = "rcs 11000001 4F100 DEADBEEF",
>> +		},
>> +		{ .test = "invalid-number",
>> +		  .in = "rcs cmd 1100000g 4F100 DEADBEEF",
>> +		},
>> +		{ .test = "invalid-number",
>> +		  .in = "rcs cmd 1100000g 4F100 DEADBEEF",
>> +		},
>> +		{ .test = "invalid-reg-addr-only",
>> +		  .in = "rcs reg 4F100",
>> +		},
>> +	};
>> +
>> +	/*
>> +	 * These only test if command parsing is correct,
>> +	 * so just make sure there's no device bound
>> +	 */
>> +	igt_kmod_unbind("xe", bus_addr);
>> +
>> +	for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
>> +		const struct value *v = &values[i];
>> +
>> +		igt_info("%s\n", v->test);
>> +		igt_debug("Test '%s' to ctx_restore_post_bb\n", v->in);
>> +		igt_assert(!igt_sysfs_set(configfs_device_fd,
>> +					  "ctx_restore_post_bb", v->in));
>
>worth binding the driver and reading the mmio register with intel_reg
>and comparing with set value?

for the valid ones (function below), yes. I was planning to do this
additional step on top, but I guess I can do it here. The problem will
be how to use intel_reg from here and make sure to choose a register
that can be used across platforms.

I will rework this test and resubmit.

thanks
Lucas De Marchi

>
>> +	}
>> +}
>> +
>> +/**
>> + * SUBTEST: ctx-restore-post-bb
>> + * Description: Validate ctx_restore_post_bb attribute
>> + */
>> +static void test_ctx_restore_post_bb(int configfs_device_fd)
>> +{
>> +	static const struct value {
>> +		const char *test;
>> +		const char *in;
>> +		const char *out;
>> +	} values[] = {
>> +		{ .test = "cmd-single",
>> +		  .in = "rcs cmd 11000001 4F100 DEADBEEF",
>> +		  .out = "rcs: 11000001 0004f100 deadbeef\n",
>> +		},
>> +		{ .test = "cmd-single-multi-values",
>> +		  .in = "rcs cmd 11000003 4F100 DEADBEEF 4F104 DEADBEEF",
>> +		  .out = "rcs: 11000003 0004f100 deadbeef 0004f104 deadbeef\n",
>> +		},
>> +		{ .test = "cmd-multi",
>> +		  .in = "rcs cmd 11000001 4F100 DEADBEEF\n"
>> +			"rcs cmd 11000001 4F104 FFFFFFFF",
>> +		  .out = "rcs: 11000001 0004f100 deadbeef 11000001 0004f104 ffffffff\n",
>> +		},
>> +		{ .test = "reg-single",
>> +		  .in = "rcs reg 4F100 DEADBEEF",
>> +		  .out = "rcs: 11000001 0004f100 deadbeef\n",
>> +		},
>> +		{ .test = "reg-multi",
>> +		  .in = "rcs reg 4F100 DEADBEEF\n"
>> +			"rcs reg 4F104 FFFFFFFF",
>> +		  .out = "rcs: 11000001 0004f100 deadbeef 11000001 0004f104 ffffffff\n",
>> +		},
>> +	};
>> +	char buf[4096] = { };
>> +
>> +	/*
>> +	 * These only test if command parsing is correct,
>> +	 * so just make sure there's no device bound
>> +	 */
>> +	igt_kmod_unbind("xe", bus_addr);
>> +
>> +	for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
>> +		const struct value *v = &values[i];
>> +
>> +		igt_info("%s\n", v->test);
>> +		igt_debug("Test '%s' to ctx_restore_post_bb\n", v->in);
>> +		igt_assert(igt_sysfs_set(configfs_device_fd,
>> +					 "ctx_restore_post_bb", v->in));
>> +
>> +		if (v->out) {
>> +			igt_assert(igt_sysfs_read(configfs_device_fd, "ctx_restore_post_bb", buf,
>> +						  sizeof(buf) - 1));
>> +			if (strcmp(v->out, buf)) {
>> +				igt_debug("Expecting '%s' but found '%s'", v->out, buf);
>> +				igt_fail(IGT_EXIT_FAILURE);
>> +			}
>> +		}
>> +	}
>> +}
>> +
>>  static void set_bus_addr(int fd)
>>  {
>>  	struct pci_device *pci_dev;
>> @@ -173,6 +278,14 @@ igt_main
>>  	igt_subtest("engines-allowed")
>>  		test_engines_allowed(configfs_device_fd);
>>
>> +	igt_describe("Validate ctx_restore_post_bb with invalid options");
>> +	igt_subtest("ctx-restore-post-bb-invalid")
>> +		test_ctx_restore_post_bb_invalid(configfs_device_fd);
>> +
>> +	igt_describe("Validate ctx_restore_post_bb");
>> +	igt_subtest("ctx-restore-post-bb")
>> +		test_ctx_restore_post_bb(configfs_device_fd);
>> +
>>  	igt_fixture {
>>  		close(configfs_device_fd);
>>  		close(configfs_fd);
>> --
>> 2.50.1
>>

✓ Xe.CI.BAT: success for tests/intel/xe_configfs: Check ctx_restore_post_bb (rev2)

[Patchwork]

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

== Series Details ==

Series: tests/intel/xe_configfs: Check ctx_restore_post_bb (rev2)
URL   : https://patchwork.freedesktop.org/series/154120/
State : success

== Summary ==

CI Bug Log - changes from XEIGT_8543_BAT -> XEIGTPW_13781_BAT
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  

Participating hosts (11 -> 11)
------------------------------

  No changes in participating hosts

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

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

### IGT changes ###

#### Possible fixes ####

  * igt@kms_flip@basic-plain-flip@a-edp1:
    - bat-adlp-7:         [DMESG-WARN][1] ([Intel XE#4543]) -> [PASS][2] +1 other test pass
   [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8543/bat-adlp-7/igt@kms_flip@basic-plain-flip@a-edp1.html
   [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13781/bat-adlp-7/igt@kms_flip@basic-plain-flip@a-edp1.html

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


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

  * IGT: IGT_8543 -> IGTPW_13781
  * Linux: xe-3784-d84b3514a845885db8cf928cc246c8efbd80a00e -> xe-3795-3e79699fa1b216e9246e406a8649235e894772d2

  IGTPW_13781: 13781
  IGT_8543: 8543
  xe-3784-d84b3514a845885db8cf928cc246c8efbd80a00e: d84b3514a845885db8cf928cc246c8efbd80a00e
  xe-3795-3e79699fa1b216e9246e406a8649235e894772d2: 3e79699fa1b216e9246e406a8649235e894772d2

== Logs ==

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

[-- Attachment #2: Type: text/html, Size: 2126 bytes --]

✗ i915.CI.BAT: failure for tests/intel/xe_configfs: Check ctx_restore_post_bb (rev2)

[Patchwork]

[-- Attachment #1: Type: text/plain, Size: 7966 bytes --]

== Series Details ==

Series: tests/intel/xe_configfs: Check ctx_restore_post_bb (rev2)
URL   : https://patchwork.freedesktop.org/series/154120/
State : failure

== Summary ==

CI Bug Log - changes from IGT_8543 -> IGTPW_13781
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with IGTPW_13781 absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in IGTPW_13781, please notify your bug team (I915-ci-infra@lists.freedesktop.org) 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_13781/index.html

Participating hosts (43 -> 42)
------------------------------

  Missing    (1): fi-snb-2520m 

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

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

### IGT changes ###

#### Possible regressions ####

  * igt@i915_selftest@live:
    - fi-skl-6600u:       [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/fi-skl-6600u/igt@i915_selftest@live.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/fi-skl-6600u/igt@i915_selftest@live.html

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

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

### IGT changes ###

#### Issues hit ####

  * igt@dmabuf@all-tests@dma_fence_chain:
    - fi-bsw-n3050:       [PASS][3] -> [ABORT][4] ([i915#12904]) +1 other test abort
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/fi-bsw-n3050/igt@dmabuf@all-tests@dma_fence_chain.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/fi-bsw-n3050/igt@dmabuf@all-tests@dma_fence_chain.html

  * igt@i915_selftest@live:
    - bat-rpls-4:         [PASS][5] -> [INCOMPLETE][6] ([i915#14838]) +1 other test incomplete
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-rpls-4/igt@i915_selftest@live.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-rpls-4/igt@i915_selftest@live.html

  * igt@i915_selftest@live@sanitycheck:
    - fi-kbl-7567u:       [PASS][7] -> [DMESG-WARN][8] ([i915#13735]) +79 other tests dmesg-warn
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/fi-kbl-7567u/igt@i915_selftest@live@sanitycheck.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/fi-kbl-7567u/igt@i915_selftest@live@sanitycheck.html
    - bat-apl-1:          [PASS][9] -> [DMESG-WARN][10] ([i915#13735]) +77 other tests dmesg-warn
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-apl-1/igt@i915_selftest@live@sanitycheck.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-apl-1/igt@i915_selftest@live@sanitycheck.html

  * igt@i915_selftest@live@workarounds:
    - bat-dg2-14:         [PASS][11] -> [DMESG-FAIL][12] ([i915#12061]) +1 other test dmesg-fail
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-dg2-14/igt@i915_selftest@live@workarounds.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-dg2-14/igt@i915_selftest@live@workarounds.html

  * igt@kms_busy@basic@flip:
    - fi-kbl-7567u:       [PASS][13] -> [DMESG-WARN][14] ([i915#13735] / [i915#180])
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/fi-kbl-7567u/igt@kms_busy@basic@flip.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/fi-kbl-7567u/igt@kms_busy@basic@flip.html

  * igt@kms_pm_rpm@basic-pci-d3-state:
    - fi-kbl-7567u:       [PASS][15] -> [DMESG-WARN][16] ([i915#13735] / [i915#13890] / [i915#180]) +52 other tests dmesg-warn
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/fi-kbl-7567u/igt@kms_pm_rpm@basic-pci-d3-state.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/fi-kbl-7567u/igt@kms_pm_rpm@basic-pci-d3-state.html
    - bat-apl-1:          [PASS][17] -> [DMESG-WARN][18] ([i915#13735] / [i915#180]) +49 other tests dmesg-warn
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-apl-1/igt@kms_pm_rpm@basic-pci-d3-state.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-apl-1/igt@kms_pm_rpm@basic-pci-d3-state.html

  * igt@kms_pm_rpm@basic-rte:
    - bat-rpls-4:         [PASS][19] -> [DMESG-WARN][20] ([i915#13400])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-rpls-4/igt@kms_pm_rpm@basic-rte.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-rpls-4/igt@kms_pm_rpm@basic-rte.html

  
#### Possible fixes ####

  * igt@dmabuf@all-tests:
    - bat-apl-1:          [ABORT][21] ([i915#12904]) -> [PASS][22] +1 other test pass
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-apl-1/igt@dmabuf@all-tests.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-apl-1/igt@dmabuf@all-tests.html

  * igt@i915_module_load@load:
    - bat-mtlp-9:         [DMESG-WARN][23] ([i915#13494]) -> [PASS][24]
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-mtlp-9/igt@i915_module_load@load.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-mtlp-9/igt@i915_module_load@load.html

  * igt@i915_selftest@live:
    - bat-mtlp-8:         [DMESG-FAIL][25] ([i915#12061]) -> [PASS][26] +1 other test pass
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-mtlp-8/igt@i915_selftest@live.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-mtlp-8/igt@i915_selftest@live.html

  * igt@kms_cursor_legacy@basic-flip-after-cursor-atomic:
    - fi-skl-6600u:       [DMESG-WARN][27] ([i915#13736]) -> [PASS][28]
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/fi-skl-6600u/igt@kms_cursor_legacy@basic-flip-after-cursor-atomic.html
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/fi-skl-6600u/igt@kms_cursor_legacy@basic-flip-after-cursor-atomic.html

  
#### Warnings ####

  * igt@i915_selftest@live:
    - bat-atsm-1:         [DMESG-FAIL][29] ([i915#12061] / [i915#14204]) -> [DMESG-FAIL][30] ([i915#12061] / [i915#13929])
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-atsm-1/igt@i915_selftest@live.html
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-atsm-1/igt@i915_selftest@live.html

  * igt@i915_selftest@live@mman:
    - bat-atsm-1:         [DMESG-FAIL][31] ([i915#14204]) -> [DMESG-FAIL][32] ([i915#13929])
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8543/bat-atsm-1/igt@i915_selftest@live@mman.html
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13781/bat-atsm-1/igt@i915_selftest@live@mman.html

  
  [i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
  [i915#12904]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12904
  [i915#13400]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13400
  [i915#13494]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13494
  [i915#13735]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13735
  [i915#13736]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13736
  [i915#13890]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13890
  [i915#13929]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13929
  [i915#14204]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14204
  [i915#14838]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14838
  [i915#180]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/180


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

  * CI: CI-20190529 -> None
  * IGT: IGT_8543 -> IGTPW_13781
  * Linux: CI_DRM_17227 -> CI_DRM_17237

  CI-20190529: 20190529
  CI_DRM_17227: 9fab6e66b0f21d7175cd687e62dedd1b2d5d2781 @ git://anongit.freedesktop.org/gfx-ci/linux
  CI_DRM_17237: 3e79699fa1b216e9246e406a8649235e894772d2 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_13781: 13781
  IGT_8543: 8543

== Logs ==

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

[-- Attachment #2: Type: text/html, Size: 9828 bytes --]