Skip to contentSkip to conversation

tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors

PATCH In review Imre Deak 3 participants 13 messages Oct 12, 2020 – Oct 15, 2020

lore
Share & tools
lore

Imre Deak

author
#0 lore raw

PATCH 1/1 tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors

The DPCD of an MST connector is read out with a REMOTE_DPCD_READ MST request. If the given connector is disconnected this read will result in an MST NAK reply and this will be reported as an EIO error to the initiator of the AUX read.

Handle this in the test that attempts to read the DPCD of any exposed connector, whether they are connected or not.

Signed-off-by Imre Deak <[email protected]>
---
 tests/kms_dp_aux_dev.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)
tests/kms_dp_aux_dev.c +13 -3
index 4f52434a..39fc2b92 100644
@@ -34,6 +34,14 @@
 
 IGT_TEST_DESCRIPTION("Test that /dev/drm_dp_aux reads work");
 
+static bool is_mst_connector(int drm_fd, uint32_t connector_id)
+{
+	return kmstest_get_property(drm_fd, connector_id,
+				    DRM_MODE_OBJECT_CONNECTOR,
+				    "PATH", NULL,
+				    NULL, NULL);
+}
+
 static bool test(int drm_fd, uint32_t connector_id)
 {
 	drmModeConnector *connector;

@@ -67,10 +75,12 @@ static bool test(int drm_fd, uint32_t connector_id)
 		igt_assert(fd >= 0);
 
 		ret = read(fd, buf, sizeof(buf));
-		igt_assert(ret == sizeof(buf) || errno == ETIMEDOUT);
-
 		igt_info("%s: %s\n", path,
-			 ret > 0 ? "success" : "timed out");
+			 ret > 0 ? "success" : strerror(errno));
+
+		igt_assert(ret == sizeof(buf) ||
+			   errno == ETIMEDOUT ||
+			   (errno == EIO && is_mst_connector(drm_fd, connector_id)));
 
 		close(fd);
Signature · 6 lines
2.20.1

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
CI
#1 lore raw

[igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors

== Series Details ==

== Series Details ==

Series: tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
URL : https://patchwork.freedesktop.org/series/82591/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_9130 -> IGTPW_5060
====================================================

Summary
-------

**FAILURE**

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

If you think the reported changes have nothing to do with the changes introduced in IGTPW_5060, please notify your bug team 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_5060/index.html

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

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

### IGT changes ###

#### Possible regressions ####

* igt@i915_selftest@live@blt:
- fi-snb-2520m: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-snb-2520m/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-snb-2520m/igt@i915_selftest@[email protected]

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

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

### IGT changes ###

#### Issues hit ####

* igt@i915_module_load@reload:
- fi-tgl-u2: [PASS][3] -> [DMESG-WARN][4] ([i915#1982] / [k.org#205379])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-tgl-u2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@[email protected]

* igt@kms_chamelium@hdmi-crc-fast:
- fi-kbl-7500u: [PASS][5] -> [DMESG-WARN][6] ([i915#2203])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-kbl-7500u/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-kbl-7500u/igt@[email protected]

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-bsw-kefka: [PASS][7] -> [DMESG-WARN][8] ([i915#1982])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-bsw-kefka/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-bsw-kefka/igt@[email protected]

* igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1:
- fi-icl-u2: [PASS][9] -> [DMESG-WARN][10] ([i915#1982])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-icl-u2/igt@kms_flip@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@[email protected]

* igt@vgem_basic@unload:
- fi-skl-guc: [PASS][11] -> [DMESG-WARN][12] ([i915#2203])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-skl-guc/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-skl-guc/igt@[email protected]

#### Possible fixes ####

* igt@debugfs_test@read_all_entries:
- {fi-kbl-7560u}: [INCOMPLETE][13] ([i915#2417]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-kbl-7560u/igt@debugfs_test@read_all_entries.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-kbl-7560u/igt@debugfs_test@read_all_entries.html

* igt@gem_exec_suspend@basic-s0:
- fi-tgl-u2: [FAIL][15] ([i915#1888]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-tgl-u2/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@[email protected]

* igt@i915_selftest@live@coherency:
- fi-gdg-551: [DMESG-FAIL][17] ([i915#1748]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-gdg-551/igt@i915_selftest@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-gdg-551/igt@i915_selftest@[email protected]

* igt@kms_flip@basic-flip-vs-dpms@a-dsi1:
- {fi-tgl-dsi}: [DMESG-WARN][19] ([i915#1982]) -> [PASS][20] +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-tgl-dsi/igt@kms_flip@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-dsi/igt@kms_flip@[email protected]

* igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1:
- fi-icl-u2: [DMESG-WARN][21] ([i915#1982]) -> [PASS][22] +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-icl-u2/igt@kms_flip@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@[email protected]

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

[i915#1748]: https://gitlab.freedesktop.org/drm/intel/issues/1748
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2203]: https://gitlab.freedesktop.org/drm/intel/issues/2203
[i915#2417]: https://gitlab.freedesktop.org/drm/intel/issues/2417
[k.org#205379]: https://bugzilla.kernel.org/show_bug.cgi?id=205379

Participating hosts (45 -> 41)
------------------------------

Additional (3): fi-kbl-soraka fi-tgl-y fi-kbl-r
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus

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

* CI: CI-20190529 -> None
* IGT: IGT_5810 -> IGTPW_5060

CI-20190529: 20190529
CI_DRM_9130: da13fb4f671901dbcf26437592f352579cc3b617 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5060: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/index.html
IGT_5810: f78ce760920efb5015725c749f411c5724114bda @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

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

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

author
#2 lore raw

Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors

Hi Lakshmi,

Quoted 30 lines · Patchwork

== Series Details ==

Series: tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
URL : https://patchwork.freedesktop.org/series/82591/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_9130 -> IGTPW_5060
====================================================

Summary
-------

**FAILURE**

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

If you think the reported changes have nothing to do with the changes introduced in IGTPW_5060, please notify your bug team 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_5060/index.html

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

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

Quoted 8 lines

### IGT changes ###

#### Possible regressions ####

* igt@i915_selftest@live@blt:
- fi-snb-2520m: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-snb-2520m/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-snb-2520m/igt@i915_selftest@[email protected]

An unrelated issue on a non-MST platform, and without any DP monitor attached or the test that this patch changes having been run.

Quoted 89 lines

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

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

### IGT changes ###

#### Issues hit ####

* igt@i915_module_load@reload:
- fi-tgl-u2: [PASS][3] -> [DMESG-WARN][4] ([i915#1982] / [k.org#205379])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-tgl-u2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@[email protected]

* igt@kms_chamelium@hdmi-crc-fast:
- fi-kbl-7500u: [PASS][5] -> [DMESG-WARN][6] ([i915#2203])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-kbl-7500u/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-kbl-7500u/igt@[email protected]

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-bsw-kefka: [PASS][7] -> [DMESG-WARN][8] ([i915#1982])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-bsw-kefka/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-bsw-kefka/igt@[email protected]

* igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1:
- fi-icl-u2: [PASS][9] -> [DMESG-WARN][10] ([i915#1982])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-icl-u2/igt@kms_flip@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@[email protected]

* igt@vgem_basic@unload:
- fi-skl-guc: [PASS][11] -> [DMESG-WARN][12] ([i915#2203])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-skl-guc/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-skl-guc/igt@[email protected]

#### Possible fixes ####

* igt@debugfs_test@read_all_entries:
- {fi-kbl-7560u}: [INCOMPLETE][13] ([i915#2417]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-kbl-7560u/igt@debugfs_test@read_all_entries.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-kbl-7560u/igt@debugfs_test@read_all_entries.html

* igt@gem_exec_suspend@basic-s0:
- fi-tgl-u2: [FAIL][15] ([i915#1888]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-tgl-u2/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@[email protected]

* igt@i915_selftest@live@coherency:
- fi-gdg-551: [DMESG-FAIL][17] ([i915#1748]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-gdg-551/igt@i915_selftest@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-gdg-551/igt@i915_selftest@[email protected]

* igt@kms_flip@basic-flip-vs-dpms@a-dsi1:
- {fi-tgl-dsi}: [DMESG-WARN][19] ([i915#1982]) -> [PASS][20] +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-tgl-dsi/igt@kms_flip@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-dsi/igt@kms_flip@[email protected]

* igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1:
- fi-icl-u2: [DMESG-WARN][21] ([i915#1982]) -> [PASS][22] +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-icl-u2/igt@kms_flip@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@[email protected]

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

[i915#1748]: https://gitlab.freedesktop.org/drm/intel/issues/1748
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2203]: https://gitlab.freedesktop.org/drm/intel/issues/2203
[i915#2417]: https://gitlab.freedesktop.org/drm/intel/issues/2417
[k.org#205379]: https://bugzilla.kernel.org/show_bug.cgi?id=205379

Participating hosts (45 -> 41)
------------------------------

Additional (3): fi-kbl-soraka fi-tgl-y fi-kbl-r
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus

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

* CI: CI-20190529 -> None
* IGT: IGT_5810 -> IGTPW_5060

Quoted 8 lines

CI-20190529: 20190529
CI_DRM_9130: da13fb4f671901dbcf26437592f352579cc3b617 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5060: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/index.html
IGT_5810: f78ce760920efb5015725c749f411c5724114bda @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

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

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

CI
#3 lore raw

[igt-dev] ✓ Fi.CI.BAT: success for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors

In reply to Imre Deak
== Series Details ==

== Series Details ==

Series: tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
URL : https://patchwork.freedesktop.org/series/82591/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_9130 -> IGTPW_5060
====================================================

Summary
-------

**SUCCESS**

No regressions found.

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

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

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

### IGT changes ###

#### Issues hit ####

* igt@i915_module_load@reload:
- fi-tgl-u2: [PASS][1] -> [DMESG-WARN][2] ([i915#1982] / [k.org#205379])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-tgl-u2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@[email protected]

* igt@i915_selftest@live@blt:
- fi-snb-2520m: [PASS][3] -> [DMESG-FAIL][4] ([i915#1409])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-snb-2520m/igt@i915_selftest@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-snb-2520m/igt@i915_selftest@[email protected]

* igt@kms_chamelium@hdmi-crc-fast:
- fi-kbl-7500u: [PASS][5] -> [DMESG-WARN][6] ([i915#2203])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-kbl-7500u/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-kbl-7500u/igt@[email protected]

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-bsw-kefka: [PASS][7] -> [DMESG-WARN][8] ([i915#1982])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-bsw-kefka/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-bsw-kefka/igt@[email protected]

* igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1:
- fi-icl-u2: [PASS][9] -> [DMESG-WARN][10] ([i915#1982])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-icl-u2/igt@kms_flip@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@[email protected]

* igt@vgem_basic@unload:
- fi-skl-guc: [PASS][11] -> [DMESG-WARN][12] ([i915#2203])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-skl-guc/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-skl-guc/igt@[email protected]

#### Possible fixes ####

* igt@debugfs_test@read_all_entries:
- {fi-kbl-7560u}: [INCOMPLETE][13] ([i915#2417]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-kbl-7560u/igt@debugfs_test@read_all_entries.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-kbl-7560u/igt@debugfs_test@read_all_entries.html

* igt@gem_exec_suspend@basic-s0:
- fi-tgl-u2: [FAIL][15] ([i915#1888]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-tgl-u2/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@[email protected]

* igt@i915_selftest@live@coherency:
- fi-gdg-551: [DMESG-FAIL][17] ([i915#1748]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-gdg-551/igt@i915_selftest@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-gdg-551/igt@i915_selftest@[email protected]

* igt@kms_flip@basic-flip-vs-dpms@a-dsi1:
- {fi-tgl-dsi}: [DMESG-WARN][19] ([i915#1982]) -> [PASS][20] +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-tgl-dsi/igt@kms_flip@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-dsi/igt@kms_flip@[email protected]

* igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1:
- fi-icl-u2: [DMESG-WARN][21] ([i915#1982]) -> [PASS][22] +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/fi-icl-u2/igt@kms_flip@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@[email protected]

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

[i915#1409]: https://gitlab.freedesktop.org/drm/intel/issues/1409
[i915#1748]: https://gitlab.freedesktop.org/drm/intel/issues/1748
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2203]: https://gitlab.freedesktop.org/drm/intel/issues/2203
[i915#2417]: https://gitlab.freedesktop.org/drm/intel/issues/2417
[k.org#205379]: https://bugzilla.kernel.org/show_bug.cgi?id=205379

Participating hosts (45 -> 41)
------------------------------

Additional (3): fi-kbl-soraka fi-tgl-y fi-kbl-r
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus

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

* CI: CI-20190529 -> None
* IGT: IGT_5810 -> IGTPW_5060

CI-20190529: 20190529
CI_DRM_9130: da13fb4f671901dbcf26437592f352579cc3b617 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5060: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/index.html
IGT_5810: f78ce760920efb5015725c749f411c5724114bda @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

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

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

CI
#4 lore raw

[igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors

In reply to Imre Deak
== Series Details ==

== Series Details ==

Series: tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
URL : https://patchwork.freedesktop.org/series/82591/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_9130_full -> IGTPW_5060_full
====================================================

Summary
-------

**FAILURE**

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

If you think the reported changes have nothing to do with the changes introduced in IGTPW_5060_full, please notify your bug team 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_5060/index.html

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

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

### IGT changes ###

#### Possible regressions ####

* igt@gem_exec_whisper@basic-fds-forked:
- shard-hsw: [PASS][1] -> [TIMEOUT][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@[email protected]

* igt@gem_linear_blits@interruptible:
- shard-snb: [PASS][3] -> [FAIL][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-snb5/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb2/igt@[email protected]

* igt@kms_flip@dpms-off-confusion@c-hdmi-a1:
- shard-hsw: [PASS][5] -> [INCOMPLETE][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw8/igt@kms_flip@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw7/igt@kms_flip@[email protected]

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

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

### IGT changes ###

#### Issues hit ####

* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-apl: [PASS][7] -> [FAIL][8] ([i915#1635] / [i915#2389])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl3/igt@gem_exec_reloc@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl3/igt@gem_exec_reloc@[email protected]

* igt@gem_exec_reloc@basic-many-active@vcs0:
- shard-glk: [PASS][9] -> [FAIL][10] ([i915#2389])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk4/igt@gem_exec_reloc@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk7/igt@gem_exec_reloc@[email protected]

* igt@gem_exec_whisper@basic-forked-all:
- shard-glk: [PASS][11] -> [DMESG-WARN][12] ([i915#118] / [i915#95])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk5/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk6/igt@[email protected]

* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][13] -> [SKIP][14] ([i915#2190])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb5/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb6/igt@[email protected]

* igt@gem_mmap_wc@copy:
- shard-iclb: [PASS][15] -> [DMESG-WARN][16] ([i915#1982])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb6/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@[email protected]

* igt@kms_big_fb@y-tiled-32bpp-rotate-0:
- shard-iclb: [PASS][17] -> [FAIL][18] ([i915#1119])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb7/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@[email protected]

* igt@kms_big_fb@yf-tiled-32bpp-rotate-0:
- shard-apl: [PASS][19] -> [DMESG-WARN][20] ([i915#1635] / [i915#1982])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl3/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl2/igt@[email protected]

* igt@kms_cursor_crc@pipe-c-cursor-256x256-onscreen:
- shard-glk: [PASS][21] -> [FAIL][22] ([i915#54]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk5/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk9/igt@[email protected]

* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][23] -> [FAIL][24] ([i915#54]) +2 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl4/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@[email protected]
- shard-apl: [PASS][25] -> [FAIL][26] ([i915#1635] / [i915#54]) +2 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl6/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl7/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt:
- shard-tglb: [PASS][27] -> [DMESG-WARN][28] ([i915#1982]) +6 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt.html

* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu:
- shard-kbl: [PASS][29] -> [DMESG-WARN][30] ([i915#1982]) +2 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu.html

* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [PASS][31] -> [SKIP][32] ([fdo#109441]) +4 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb5/igt@kms_psr@psr2_sprite_plane_move.html

* igt@tools_test@tools_test:
- shard-hsw: [PASS][33] -> [DMESG-WARN][34] ([i915#1436])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw4/igt@tools_test@tools_test.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@tools_test@tools_test.html

#### Possible fixes ####

* igt@feature_discovery@psr2:
- shard-iclb: [SKIP][35] ([i915#658]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb7/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@[email protected]

* {igt@gem_exec_capture@pi@rcs0}:
- shard-glk: [INCOMPLETE][37] ([i915#2553]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk2/igt@gem_exec_capture@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk9/igt@gem_exec_capture@[email protected]

* igt@gem_exec_schedule@smoketest-all:
- shard-glk: [DMESG-WARN][39] ([i915#118] / [i915#95]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk8/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk4/igt@[email protected]

* igt@gem_mmap_offset@blt-coherency:
- shard-glk: [FAIL][41] ([i915#2328]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk9/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk5/igt@[email protected]

* igt@gem_partial_pwrite_pread@writes-after-reads:
- shard-hsw: [FAIL][43] -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@[email protected]
- shard-snb: [INCOMPLETE][45] ([i915#82]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-snb7/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb5/igt@[email protected]

* igt@gem_render_copy@y-tiled:
- shard-glk: [FAIL][47] ([i915#2541]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk1/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk2/igt@[email protected]
- shard-apl: [FAIL][49] ([i915#1635] / [i915#2541]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl1/igt@[email protected]
- shard-kbl: [FAIL][51] ([i915#2541]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl4/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@[email protected]
- shard-hsw: [FAIL][53] ([i915#2541]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@[email protected]
- shard-iclb: [FAIL][55] ([i915#2541]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb1/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb6/igt@[email protected]

* igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled:
- shard-tglb: [FAIL][57] ([i915#2541]) -> [PASS][58] +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb7/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb5/igt@[email protected]

* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-kbl: [INCOMPLETE][59] ([i915#155] / [i915#794]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl2/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@[email protected]

* {igt@kms_async_flips@async-flip-with-page-flip-events}:
- shard-kbl: [FAIL][61] ([i915#2521]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl2/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@[email protected]

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- shard-apl: [DMESG-WARN][63] ([i915#1635] / [i915#1982]) -> [PASS][64] +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl2/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl6/igt@[email protected]

* igt@kms_hdmi_inject@inject-audio:
- shard-tglb: [SKIP][65] ([i915#433]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb7/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb5/igt@[email protected]

* igt@kms_plane_lowres@pipe-a-tiling-y:
- shard-iclb: [DMESG-FAIL][67] ([i915#1226]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb2/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb6/igt@[email protected]

* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [SKIP][69] ([fdo#109441]) -> [PASS][70] +2 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb8/igt@kms_psr@psr2_sprite_mmap_gtt.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html

* igt@kms_setmode@basic:
- shard-apl: [FAIL][71] ([i915#1635] / [i915#31]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl4/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl8/igt@[email protected]
- shard-hsw: [FAIL][73] ([i915#31]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw4/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@[email protected]

* igt@kms_universal_plane@universal-plane-gen9-features-pipe-b:
- shard-tglb: [DMESG-WARN][75] ([i915#1982]) -> [PASS][76] +3 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb5/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb2/igt@[email protected]

* igt@perf@invalid-oa-exponent:
- shard-hsw: [SKIP][77] ([fdo#109271]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw7/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw2/igt@[email protected]
- shard-iclb: [SKIP][79] ([i915#405]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb6/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb3/igt@[email protected]
- shard-glk: [SKIP][81] ([fdo#109271]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk5/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk2/igt@[email protected]
- shard-tglb: [SKIP][83] ([i915#405]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb6/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb8/igt@[email protected]
- shard-apl: [SKIP][85] ([fdo#109271] / [i915#1635]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl8/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl7/igt@[email protected]
- shard-kbl: [SKIP][87] ([fdo#109271]) -> [PASS][88]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl6/igt@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@[email protected]

* igt@perf@polling-parameterized:
- shard-glk: [FAIL][89] ([i915#1542]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk3/igt@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk1/igt@[email protected]

#### Warnings ####

* igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled:
- shard-hsw: [FAIL][91] ([i915#2541]) -> [SKIP][92] ([fdo#109271])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw1/igt@[email protected]
- shard-kbl: [FAIL][93] ([i915#2541]) -> [SKIP][94] ([fdo#109271])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl4/igt@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@[email protected]
- shard-snb: [FAIL][95] ([i915#2541]) -> [SKIP][96] ([fdo#109271])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-snb7/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb7/igt@[email protected]
- shard-apl: [FAIL][97] ([i915#1635] / [i915#2541]) -> [SKIP][98] ([fdo#109271] / [i915#1635])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl2/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl3/igt@[email protected]
- shard-iclb: [FAIL][99] ([i915#2541]) -> [SKIP][100] ([i915#768])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb1/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb7/igt@[email protected]
- shard-glk: [FAIL][101] ([i915#2541]) -> [SKIP][102] ([fdo#109271])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk1/igt@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk6/igt@[email protected]

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

[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1226]: https://gitlab.freedesktop.org/drm/intel/issues/1226
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2328]: https://gitlab.freedesktop.org/drm/intel/issues/2328
[i915#2389]: https://gitlab.freedesktop.org/drm/intel/issues/2389
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2541]: https://gitlab.freedesktop.org/drm/intel/issues/2541
[i915#2553]: https://gitlab.freedesktop.org/drm/intel/issues/2553
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#405]: https://gitlab.freedesktop.org/drm/intel/issues/405
[i915#433]: https://gitlab.freedesktop.org/drm/intel/issues/433
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#768]: https://gitlab.freedesktop.org/drm/intel/issues/768
[i915#794]: https://gitlab.freedesktop.org/drm/intel/issues/794
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95

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

Missing (3): pig-skl-6260u pig-glk-j5005 pig-icl-1065g7

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

* CI: CI-20190529 -> None
* IGT: IGT_5810 -> IGTPW_5060
* Piglit: piglit_4509 -> None

CI-20190529: 20190529
CI_DRM_9130: da13fb4f671901dbcf26437592f352579cc3b617 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5060: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/index.html
IGT_5810: f78ce760920efb5015725c749f411c5724114bda @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit

== Logs ==

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

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

CI
#5 lore raw

[igt-dev] ✓ Fi.CI.IGT: success for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors

In reply to Imre Deak
== Series Details ==

== Series Details ==

Series: tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
URL : https://patchwork.freedesktop.org/series/82591/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_9130_full -> IGTPW_5060_full
====================================================

Summary
-------

**SUCCESS**

No regressions found.

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

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

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

### IGT changes ###

#### Issues hit ####

* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-apl: [PASS][1] -> [FAIL][2] ([i915#1635] / [i915#2389])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl3/igt@gem_exec_reloc@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl3/igt@gem_exec_reloc@[email protected]

* igt@gem_exec_reloc@basic-many-active@vcs0:
- shard-glk: [PASS][3] -> [FAIL][4] ([i915#2389])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk4/igt@gem_exec_reloc@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk7/igt@gem_exec_reloc@[email protected]

* igt@gem_exec_whisper@basic-fds-forked:
- shard-hsw: [PASS][5] -> [TIMEOUT][6] ([i915#2570])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@[email protected]

* igt@gem_exec_whisper@basic-forked-all:
- shard-glk: [PASS][7] -> [DMESG-WARN][8] ([i915#118] / [i915#95])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk5/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk6/igt@[email protected]

* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][9] -> [SKIP][10] ([i915#2190])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb5/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb6/igt@[email protected]

* igt@gem_linear_blits@interruptible:
- shard-snb: [PASS][11] -> [FAIL][12] ([i915#1263])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-snb5/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb2/igt@[email protected]

* igt@gem_mmap_wc@copy:
- shard-iclb: [PASS][13] -> [DMESG-WARN][14] ([i915#1982])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb6/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@[email protected]

* igt@kms_big_fb@y-tiled-32bpp-rotate-0:
- shard-iclb: [PASS][15] -> [FAIL][16] ([i915#1119])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb7/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@[email protected]

* igt@kms_big_fb@yf-tiled-32bpp-rotate-0:
- shard-apl: [PASS][17] -> [DMESG-WARN][18] ([i915#1635] / [i915#1982])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl3/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl2/igt@[email protected]

* igt@kms_cursor_crc@pipe-c-cursor-256x256-onscreen:
- shard-glk: [PASS][19] -> [FAIL][20] ([i915#54]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk5/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk9/igt@[email protected]

* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][21] -> [FAIL][22] ([i915#54]) +2 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl4/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@[email protected]
- shard-apl: [PASS][23] -> [FAIL][24] ([i915#1635] / [i915#54]) +2 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl6/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl7/igt@[email protected]

* igt@kms_flip@dpms-off-confusion@c-hdmi-a1:
- shard-hsw: [PASS][25] -> [INCOMPLETE][26] ([CI#80])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw8/igt@kms_flip@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw7/igt@kms_flip@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt:
- shard-tglb: [PASS][27] -> [DMESG-WARN][28] ([i915#1982]) +6 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt.html

* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu:
- shard-kbl: [PASS][29] -> [DMESG-WARN][30] ([i915#1982]) +2 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu.html

* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [PASS][31] -> [SKIP][32] ([fdo#109441]) +4 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb5/igt@kms_psr@psr2_sprite_plane_move.html

* igt@tools_test@tools_test:
- shard-hsw: [PASS][33] -> [DMESG-WARN][34] ([i915#1436])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw4/igt@tools_test@tools_test.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@tools_test@tools_test.html

#### Possible fixes ####

* igt@feature_discovery@psr2:
- shard-iclb: [SKIP][35] ([i915#658]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb7/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@[email protected]

* {igt@gem_exec_capture@pi@rcs0}:
- shard-glk: [INCOMPLETE][37] ([i915#2553]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk2/igt@gem_exec_capture@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk9/igt@gem_exec_capture@[email protected]

* igt@gem_exec_schedule@smoketest-all:
- shard-glk: [DMESG-WARN][39] ([i915#118] / [i915#95]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk8/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk4/igt@[email protected]

* igt@gem_mmap_offset@blt-coherency:
- shard-glk: [FAIL][41] ([i915#2328]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk9/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk5/igt@[email protected]

* igt@gem_partial_pwrite_pread@writes-after-reads:
- shard-hsw: [FAIL][43] -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@[email protected]
- shard-snb: [INCOMPLETE][45] ([i915#82]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-snb7/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb5/igt@[email protected]

* igt@gem_render_copy@y-tiled:
- shard-glk: [FAIL][47] ([i915#2541]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk1/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk2/igt@[email protected]
- shard-apl: [FAIL][49] ([i915#1635] / [i915#2541]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl1/igt@[email protected]
- shard-kbl: [FAIL][51] ([i915#2541]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl4/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@[email protected]
- shard-hsw: [FAIL][53] ([i915#2541]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@[email protected]
- shard-iclb: [FAIL][55] ([i915#2541]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb1/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb6/igt@[email protected]

* igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled:
- shard-tglb: [FAIL][57] ([i915#2541]) -> [PASS][58] +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb7/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb5/igt@[email protected]

* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-kbl: [INCOMPLETE][59] ([i915#155] / [i915#794]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl2/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@[email protected]

* {igt@kms_async_flips@async-flip-with-page-flip-events}:
- shard-kbl: [FAIL][61] ([i915#2521]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl2/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@[email protected]

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- shard-apl: [DMESG-WARN][63] ([i915#1635] / [i915#1982]) -> [PASS][64] +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl2/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl6/igt@[email protected]

* igt@kms_hdmi_inject@inject-audio:
- shard-tglb: [SKIP][65] ([i915#433]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb7/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb5/igt@[email protected]

* igt@kms_plane_lowres@pipe-a-tiling-y:
- shard-iclb: [DMESG-FAIL][67] ([i915#1226]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb2/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb6/igt@[email protected]

* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [SKIP][69] ([fdo#109441]) -> [PASS][70] +2 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb8/igt@kms_psr@psr2_sprite_mmap_gtt.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html

* igt@kms_setmode@basic:
- shard-apl: [FAIL][71] ([i915#1635] / [i915#31]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl4/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl8/igt@[email protected]
- shard-hsw: [FAIL][73] ([i915#31]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw4/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@[email protected]

* igt@kms_universal_plane@universal-plane-gen9-features-pipe-b:
- shard-tglb: [DMESG-WARN][75] ([i915#1982]) -> [PASS][76] +3 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb5/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb2/igt@[email protected]

* igt@perf@invalid-oa-exponent:
- shard-hsw: [SKIP][77] ([fdo#109271]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw7/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw2/igt@[email protected]
- shard-iclb: [SKIP][79] ([i915#405]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb6/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb3/igt@[email protected]
- shard-glk: [SKIP][81] ([fdo#109271]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk5/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk2/igt@[email protected]
- shard-tglb: [SKIP][83] ([i915#405]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb6/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb8/igt@[email protected]
- shard-apl: [SKIP][85] ([fdo#109271] / [i915#1635]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl8/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl7/igt@[email protected]
- shard-kbl: [SKIP][87] ([fdo#109271]) -> [PASS][88]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl6/igt@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@[email protected]

* igt@perf@polling-parameterized:
- shard-glk: [FAIL][89] ([i915#1542]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk3/igt@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk1/igt@[email protected]

#### Warnings ####

* igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled:
- shard-hsw: [FAIL][91] ([i915#2541]) -> [SKIP][92] ([fdo#109271])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw1/igt@[email protected]
- shard-kbl: [FAIL][93] ([i915#2541]) -> [SKIP][94] ([fdo#109271])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl4/igt@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@[email protected]
- shard-snb: [FAIL][95] ([i915#2541]) -> [SKIP][96] ([fdo#109271])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-snb7/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb7/igt@[email protected]
- shard-apl: [FAIL][97] ([i915#1635] / [i915#2541]) -> [SKIP][98] ([fdo#109271] / [i915#1635])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-apl2/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl3/igt@[email protected]
- shard-iclb: [FAIL][99] ([i915#2541]) -> [SKIP][100] ([i915#768])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb1/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb7/igt@[email protected]
- shard-glk: [FAIL][101] ([i915#2541]) -> [SKIP][102] ([fdo#109271])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk1/igt@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk6/igt@[email protected]

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

[CI#80]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/80
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1226]: https://gitlab.freedesktop.org/drm/intel/issues/1226
[i915#1263]: https://gitlab.freedesktop.org/drm/intel/issues/1263
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2328]: https://gitlab.freedesktop.org/drm/intel/issues/2328
[i915#2389]: https://gitlab.freedesktop.org/drm/intel/issues/2389
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2541]: https://gitlab.freedesktop.org/drm/intel/issues/2541
[i915#2553]: https://gitlab.freedesktop.org/drm/intel/issues/2553
[i915#2570]: https://gitlab.freedesktop.org/drm/intel/issues/2570
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#405]: https://gitlab.freedesktop.org/drm/intel/issues/405
[i915#433]: https://gitlab.freedesktop.org/drm/intel/issues/433
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#768]: https://gitlab.freedesktop.org/drm/intel/issues/768
[i915#794]: https://gitlab.freedesktop.org/drm/intel/issues/794
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95

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

Missing (3): pig-skl-6260u pig-glk-j5005 pig-icl-1065g7

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

* CI: CI-20190529 -> None
* IGT: IGT_5810 -> IGTPW_5060
* Piglit: piglit_4509 -> None

CI-20190529: 20190529
CI_DRM_9130: da13fb4f671901dbcf26437592f352579cc3b617 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5060: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/index.html
IGT_5810: f78ce760920efb5015725c749f411c5724114bda @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit

== Logs ==

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

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#6 lore raw
In reply to Imre Deak
Quoted 7 lines · Imre Deak

The DPCD of an MST connector is read out with a REMOTE_DPCD_READ MST request. If the given connector is disconnected this read will result in an MST NAK reply and this will be reported as an EIO error to the initiator of the AUX read.

Handle this in the test that attempts to read the DPCD of any exposed connector, whether they are connected or not.

MST connectors get nuked once disconnected no? So is this just to avoid some race with the connector disappearing during the test?

Quoted 48 lines
Signed-off-by Imre Deak <[email protected]>
---
 tests/kms_dp_aux_dev.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)
tests/kms_dp_aux_dev.c +13 -3
index 4f52434a..39fc2b92 100644
@@ -34,6 +34,14 @@
 
 IGT_TEST_DESCRIPTION("Test that /dev/drm_dp_aux reads work");
 
+static bool is_mst_connector(int drm_fd, uint32_t connector_id)
+{
+	return kmstest_get_property(drm_fd, connector_id,
+				    DRM_MODE_OBJECT_CONNECTOR,
+				    "PATH", NULL,
+				    NULL, NULL);
+}
+
 static bool test(int drm_fd, uint32_t connector_id)
 {
 	drmModeConnector *connector;

@@ -67,10 +75,12 @@ static bool test(int drm_fd, uint32_t connector_id)
 		igt_assert(fd >= 0);
 
 		ret = read(fd, buf, sizeof(buf));
-		igt_assert(ret == sizeof(buf) || errno == ETIMEDOUT);
-
 		igt_info("%s: %s\n", path,
-			 ret > 0 ? "success" : "timed out");
+			 ret > 0 ? "success" : strerror(errno));
+
+		igt_assert(ret == sizeof(buf) ||
+			   errno == ETIMEDOUT ||
+			   (errno == EIO && is_mst_connector(drm_fd, connector_id)));
 
 		close(fd);
Signature · 6 lines
2.20.1

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Signature · 6 lines
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
author
#7 lore raw
Quoted 11 lines · Ville Syrjälä
Quoted 7 lines · Imre Deak

The DPCD of an MST connector is read out with a REMOTE_DPCD_READ MST request. If the given connector is disconnected this read will result in an MST NAK reply and this will be reported as an EIO error to the initiator of the AUX read.

Handle this in the test that attempts to read the DPCD of any exposed connector, whether they are connected or not.

MST connectors get nuked once disconnected no? So is this just to avoid some race with the connector disappearing during the test?

During enumeration of the ports of an MSTB (in response to a hotplug when at least one port is connected) a connector is added for all (output) ports, even if they are not connected. If a port gets unplugged the connector is removed yes, but a new connector for this port is added back since the parent MSTB is reprobed then.

Quoted 42 lines
Quoted 42 lines
Signed-off-by Imre Deak <[email protected]>
---
 tests/kms_dp_aux_dev.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)
tests/kms_dp_aux_dev.c +13 -3
index 4f52434a..39fc2b92 100644
@@ -34,6 +34,14 @@
 
 IGT_TEST_DESCRIPTION("Test that /dev/drm_dp_aux reads work");
 
+static bool is_mst_connector(int drm_fd, uint32_t connector_id)
+{
+	return kmstest_get_property(drm_fd, connector_id,
+				    DRM_MODE_OBJECT_CONNECTOR,
+				    "PATH", NULL,
+				    NULL, NULL);
+}
+
 static bool test(int drm_fd, uint32_t connector_id)
 {
 	drmModeConnector *connector;

@@ -67,10 +75,12 @@ static bool test(int drm_fd, uint32_t connector_id)
 		igt_assert(fd >= 0);
 
 		ret = read(fd, buf, sizeof(buf));
-		igt_assert(ret == sizeof(buf) || errno == ETIMEDOUT);
-
 		igt_info("%s: %s\n", path,
-			 ret > 0 ? "success" : "timed out");
+			 ret > 0 ? "success" : strerror(errno));
+
+		igt_assert(ret == sizeof(buf) ||
+			   errno == ETIMEDOUT ||
+			   (errno == EIO && is_mst_connector(drm_fd, connector_id)));
 
 		close(fd);
Quoted 11 lines
Quoted 7 lines
Signature · 6 lines
2.20.1

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Signature · 2 lines
Ville Syrjälä
Intel

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#8 lore raw
Quoted 10 lines · Imre Deak
Quoted 9 lines · Ville Syrjälä
Quoted 7 lines · Imre Deak

The DPCD of an MST connector is read out with a REMOTE_DPCD_READ MST request. If the given connector is disconnected this read will result in an MST NAK reply and this will be reported as an EIO error to the initiator of the AUX read.

Handle this in the test that attempts to read the DPCD of any exposed connector, whether they are connected or not.

Quoted 8 lines
Quoted 2 lines

MST connectors get nuked once disconnected no? So is this just to avoid some race with the connector disappearing during the test?

During enumeration of the ports of an MSTB (in response to a hotplug when at least one port is connected) a connector is added for all (output) ports, even if they are not connected. If a port gets unplugged the connector is removed yes, but a new connector for this port is added back since the parent MSTB is reprobed then.

That's quite confusing. Why are we trying to base the lifetime of the connector on two different things?

Also I don't remember seeing any extra connectors for disconnected ports on MST devices. So a bit confused.

Quoted 54 lines
Quoted 54 lines
Quoted 50 lines
Signed-off-by Imre Deak <[email protected]>
---
 tests/kms_dp_aux_dev.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)
tests/kms_dp_aux_dev.c +13 -3
index 4f52434a..39fc2b92 100644
@@ -34,6 +34,14 @@
 
 IGT_TEST_DESCRIPTION("Test that /dev/drm_dp_aux reads work");
 
+static bool is_mst_connector(int drm_fd, uint32_t connector_id)
+{
+	return kmstest_get_property(drm_fd, connector_id,
+				    DRM_MODE_OBJECT_CONNECTOR,
+				    "PATH", NULL,
+				    NULL, NULL);
+}
+
 static bool test(int drm_fd, uint32_t connector_id)
 {
 	drmModeConnector *connector;

@@ -67,10 +75,12 @@ static bool test(int drm_fd, uint32_t connector_id)
 		igt_assert(fd >= 0);
 
 		ret = read(fd, buf, sizeof(buf));
-		igt_assert(ret == sizeof(buf) || errno == ETIMEDOUT);
-
 		igt_info("%s: %s\n", path,
-			 ret > 0 ? "success" : "timed out");
+			 ret > 0 ? "success" : strerror(errno));
+
+		igt_assert(ret == sizeof(buf) ||
+			   errno == ETIMEDOUT ||
+			   (errno == EIO && is_mst_connector(drm_fd, connector_id)));
 
 		close(fd);
Signature · 6 lines
2.20.1

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Signature · 2 lines
Ville Syrjälä
Intel
Signature · 6 lines
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
author
#9 lore raw
Quoted 14 lines · Ville Syrjälä
Quoted 13 lines · Imre Deak
Quoted 11 lines · Ville Syrjälä
Quoted 7 lines · Imre Deak

The DPCD of an MST connector is read out with a REMOTE_DPCD_READ MST request. If the given connector is disconnected this read will result in an MST NAK reply and this will be reported as an EIO error to the initiator of the AUX read.

Handle this in the test that attempts to read the DPCD of any exposed connector, whether they are connected or not.

MST connectors get nuked once disconnected no? So is this just to avoid some race with the connector disappearing during the test?

Quoted 8 lines
Quoted 5 lines

During enumeration of the ports of an MSTB (in response to a hotplug when at least one port is connected) a connector is added for all (output) ports, even if they are not connected. If a port gets unplugged the connector is removed yes, but a new connector for this port is added back since the parent MSTB is reprobed then.

That's quite confusing. Why are we trying to base the lifetime of the connector on two different things?

That's how MST core currently works: if a branch device is present then all MST output ports on it will be also present along with the corresponding DRM connector for these output ports, whether or not there is anything plugged to these output ports.

Quoted 2 lines

Also I don't remember seeing any extra connectors for disconnected ports on MST devices. So a bit confused.

But that matches the code and also what I see. After a branch device (a TBT dock in MST mode) is plugged to the host with 1 monitor plugged to it (to port 2) I get:

[ 6451.971549] [drm:drm_dp_send_link_address [drm_kms_helper]] link address reply: 4
[ 6451.985722] [drm:drm_dp_send_link_address [drm_kms_helper]] port 0: input 1, pdt: 1, pn: 0, dpcd_rev: 00, mcs: 1, ddps: 1, ldps 0, sdp 0/0
[ 6451.985727] [drm:drm_dp_send_link_address [drm_kms_helper]] port 1: input 0, pdt: 0, pn: 1, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0
[ 6452.002362] [drm:drm_dp_send_link_address [drm_kms_helper]] port 2: input 0, pdt: 3, pn: 2, dpcd_rev: 11, mcs: 0, ddps: 1, ldps 0, sdp 1/1
[ 6452.002366] [drm:drm_dp_send_link_address [drm_kms_helper]] port 3: input 0, pdt: 0, pn: 3, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0
$ ls /sys/class/drm/

card0 card0-DP-1 card0-DP-2 card0-DP-3 card0-DP-4 card0-DP-5 card0-DP-6 card0-DP-7 card0-HDMI-A-1 renderD128 version

card0-DP-[567] being the 3 output ports on the branch device, card0-DP-6 in connected and the other 2 in disconnected state.

--Imre

Quoted 44 lines
Quoted 44 lines
Quoted 44 lines
Quoted 44 lines
Signed-off-by Imre Deak <[email protected]>
---
 tests/kms_dp_aux_dev.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)
tests/kms_dp_aux_dev.c +13 -3
index 4f52434a..39fc2b92 100644
@@ -34,6 +34,14 @@
 
 IGT_TEST_DESCRIPTION("Test that /dev/drm_dp_aux reads work");
 
+static bool is_mst_connector(int drm_fd, uint32_t connector_id)
+{
+	return kmstest_get_property(drm_fd, connector_id,
+				    DRM_MODE_OBJECT_CONNECTOR,
+				    "PATH", NULL,
+				    NULL, NULL);
+}
+
 static bool test(int drm_fd, uint32_t connector_id)
 {
 	drmModeConnector *connector;

@@ -67,10 +75,12 @@ static bool test(int drm_fd, uint32_t connector_id)
 		igt_assert(fd >= 0);
 
 		ret = read(fd, buf, sizeof(buf));
-		igt_assert(ret == sizeof(buf) || errno == ETIMEDOUT);
-
 		igt_info("%s: %s\n", path,
-			 ret > 0 ? "success" : "timed out");
+			 ret > 0 ? "success" : strerror(errno));
+
+		igt_assert(ret == sizeof(buf) ||
+			   errno == ETIMEDOUT ||
+			   (errno == EIO && is_mst_connector(drm_fd, connector_id)));
 
 		close(fd);
Signature · 1 line
2.20.1
Quoted 12 lines
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

Signature · 2 lines
Ville Syrjälä
Intel
Signature · 2 lines
Ville Syrjälä
Intel

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

author
#10 lore raw
Quoted 42 lines · Imre Deak
Quoted 14 lines · Ville Syrjälä
Quoted 13 lines · Imre Deak
Quoted 11 lines · Ville Syrjälä
Quoted 7 lines · Imre Deak

The DPCD of an MST connector is read out with a REMOTE_DPCD_READ MST request. If the given connector is disconnected this read will result in an MST NAK reply and this will be reported as an EIO error to the initiator of the AUX read.

Handle this in the test that attempts to read the DPCD of any exposed connector, whether they are connected or not.

MST connectors get nuked once disconnected no? So is this just to avoid some race with the connector disappearing during the test?

Quoted 8 lines
Quoted 5 lines

During enumeration of the ports of an MSTB (in response to a hotplug when at least one port is connected) a connector is added for all (output) ports, even if they are not connected. If a port gets unplugged the connector is removed yes, but a new connector for this port is added back since the parent MSTB is reprobed then.

That's quite confusing. Why are we trying to base the lifetime of the connector on two different things?

That's how MST core currently works: if a branch device is present then all MST output ports on it will be also present along with the corresponding DRM connector for these output ports, whether or not there is anything plugged to these output ports.

Quoted 2 lines

Also I don't remember seeing any extra connectors for disconnected ports on MST devices. So a bit confused.

But that matches the code and also what I see. After a branch device (a TBT dock in MST mode) is plugged to the host with 1 monitor plugged to it (to port 2) I get:

[ 6451.971549] [drm:drm_dp_send_link_address [drm_kms_helper]] link address reply: 4
[ 6451.985722] [drm:drm_dp_send_link_address [drm_kms_helper]] port 0: input 1, pdt: 1, pn: 0, dpcd_rev: 00, mcs: 1, ddps: 1, ldps 0, sdp 0/0
[ 6451.985727] [drm:drm_dp_send_link_address [drm_kms_helper]] port 1: input 0, pdt: 0, pn: 1, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0
[ 6452.002362] [drm:drm_dp_send_link_address [drm_kms_helper]] port 2: input 0, pdt: 3, pn: 2, dpcd_rev: 11, mcs: 0, ddps: 1, ldps 0, sdp 1/1
[ 6452.002366] [drm:drm_dp_send_link_address [drm_kms_helper]] port 3: input 0, pdt: 0, pn: 3, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0
Quoted 6 lines
$ ls /sys/class/drm/

card0 card0-DP-1 card0-DP-2 card0-DP-3 card0-DP-4 card0-DP-5 card0-DP-6 card0-DP-7 card0-HDMI-A-1 renderD128 version

card0-DP-[567] being the 3 output ports on the branch device, card0-DP-6 in connected and the other 2 in disconnected state.

I checked now what happens when plugging an SST monitor to port 1 and an MST monitor to port 2 on the above dock:

[ 1456.272370] [drm:drm_dp_send_link_address [drm_kms_helper]] link address reply: 4
[ 1456.381696] [drm:drm_dp_send_link_address [drm_kms_helper]] port 0: input 1, pdt: 1, pn: 0, dpcd_rev: 00, mcs: 1, ddps: 1, ldps 0, sdp 0/0
[ 1456.397902] [drm:drm_dp_send_link_address [drm_kms_helper]] port 1: input 0, pdt: 4, pn: 1, dpcd_rev: 00, mcs: 0, ddps: 1, ldps 1, sdp 1/1
[ 1456.397906] [drm:drm_dp_send_link_address [drm_kms_helper]] port 2: input 0, pdt: 2, pn: 2, dpcd_rev: 12, mcs: 1, ddps: 1, ldps 0, sdp 0/0
[ 1456.397910] [drm:drm_dp_send_link_address [drm_kms_helper]] port 3: input 0, pdt: 0, pn: 3, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0
[ 1459.650637] [drm:drm_dp_send_link_address [drm_kms_helper]] link address reply: 3
[ 1459.660720] [drm:drm_dp_send_link_address [drm_kms_helper]] port 0: input 1, pdt: 2, pn: 0, dpcd_rev: 00, mcs: 1, ddps: 1, ldps 0, sdp 0/0
[ 1459.687834] [drm:drm_dp_send_link_address [drm_kms_helper]] port 1: input 0, pdt: 3, pn: 8, dpcd_rev: 12, mcs: 0, ddps: 1, ldps 0, sdp 1/1
[ 1459.717059] [drm:drm_dp_send_link_address [drm_kms_helper]] port 2: input 0, pdt: 0, pn: 1, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0

The driver exposes a connector for the branch device in the MST monitor too, this connector is in disconnected state, but (as expected) we can read out the (branch device) DPCD from it.

The MST monitor has two output ports, on port 1 (pn 8) is its internal sink stream on port 2 (pn 1) is a daisy chain DP port. For both of these ports the driver exposes a connector, the latter one in disconnected state and the remote DPCD read for this will fail with a NAK/EIO error (as in the original case).

So atm the driver exposes a connector for all output ports of branch devices and the branch devices themselves have also a connector (both for the "root" branch device, card0-DP-3 above, and all downstream branch devices). All ports/connectors that have an SST sink plugged into them also expose an I2C and AUX device. Ports/connectors that have a branch device plugged into them only expose an AUX device.

I think this is consistent and (if so) it would make sense to document this somewhere as well.

One inconsistency I noticed is connector numbering, it depends on the plugging order. That's because all connectors are added first for any downstream branch device as they are enumarated on a port, before adding connectors on subsequent ports on the parent branch device.

So in the above case where the dock is plugged with everything else already plugged to it DP-[569] belongs to the dock while DP-[78] belongs to the monitor. This could be made more consistent by adding first all the connectors on a branch device before enumerating any other branch devices attached to it.

--Imre
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev

#11 lore raw
Quoted 80 lines · Imre Deak
Quoted 42 lines · Imre Deak
Quoted 14 lines · Ville Syrjälä
Quoted 13 lines · Imre Deak
Quoted 11 lines · Ville Syrjälä
Quoted 7 lines · Imre Deak

The DPCD of an MST connector is read out with a REMOTE_DPCD_READ MST request. If the given connector is disconnected this read will result in an MST NAK reply and this will be reported as an EIO error to the initiator of the AUX read.

Handle this in the test that attempts to read the DPCD of any exposed connector, whether they are connected or not.

MST connectors get nuked once disconnected no? So is this just to avoid some race with the connector disappearing during the test?

Quoted 8 lines
Quoted 5 lines

During enumeration of the ports of an MSTB (in response to a hotplug when at least one port is connected) a connector is added for all (output) ports, even if they are not connected. If a port gets unplugged the connector is removed yes, but a new connector for this port is added back since the parent MSTB is reprobed then.

That's quite confusing. Why are we trying to base the lifetime of the connector on two different things?

That's how MST core currently works: if a branch device is present then all MST output ports on it will be also present along with the corresponding DRM connector for these output ports, whether or not there is anything plugged to these output ports.

Quoted 2 lines

Also I don't remember seeing any extra connectors for disconnected ports on MST devices. So a bit confused.

But that matches the code and also what I see. After a branch device (a TBT dock in MST mode) is plugged to the host with 1 monitor plugged to it (to port 2) I get:

[ 6451.971549] [drm:drm_dp_send_link_address [drm_kms_helper]] link address reply: 4
[ 6451.985722] [drm:drm_dp_send_link_address [drm_kms_helper]] port 0: input 1, pdt: 1, pn: 0, dpcd_rev: 00, mcs: 1, ddps: 1, ldps 0, sdp 0/0
[ 6451.985727] [drm:drm_dp_send_link_address [drm_kms_helper]] port 1: input 0, pdt: 0, pn: 1, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0
[ 6452.002362] [drm:drm_dp_send_link_address [drm_kms_helper]] port 2: input 0, pdt: 3, pn: 2, dpcd_rev: 11, mcs: 0, ddps: 1, ldps 0, sdp 1/1
[ 6452.002366] [drm:drm_dp_send_link_address [drm_kms_helper]] port 3: input 0, pdt: 0, pn: 3, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0
Quoted 6 lines
$ ls /sys/class/drm/

card0 card0-DP-1 card0-DP-2 card0-DP-3 card0-DP-4 card0-DP-5 card0-DP-6 card0-DP-7 card0-HDMI-A-1 renderD128 version

card0-DP-[567] being the 3 output ports on the branch device, card0-DP-6 in connected and the other 2 in disconnected state.

I checked now what happens when plugging an SST monitor to port 1 and an MST monitor to port 2 on the above dock:

[ 1456.272370] [drm:drm_dp_send_link_address [drm_kms_helper]] link address reply: 4
[ 1456.381696] [drm:drm_dp_send_link_address [drm_kms_helper]] port 0: input 1, pdt: 1, pn: 0, dpcd_rev: 00, mcs: 1, ddps: 1, ldps 0, sdp 0/0
[ 1456.397902] [drm:drm_dp_send_link_address [drm_kms_helper]] port 1: input 0, pdt: 4, pn: 1, dpcd_rev: 00, mcs: 0, ddps: 1, ldps 1, sdp 1/1
[ 1456.397906] [drm:drm_dp_send_link_address [drm_kms_helper]] port 2: input 0, pdt: 2, pn: 2, dpcd_rev: 12, mcs: 1, ddps: 1, ldps 0, sdp 0/0
[ 1456.397910] [drm:drm_dp_send_link_address [drm_kms_helper]] port 3: input 0, pdt: 0, pn: 3, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0
[ 1459.650637] [drm:drm_dp_send_link_address [drm_kms_helper]] link address reply: 3
[ 1459.660720] [drm:drm_dp_send_link_address [drm_kms_helper]] port 0: input 1, pdt: 2, pn: 0, dpcd_rev: 00, mcs: 1, ddps: 1, ldps 0, sdp 0/0
[ 1459.687834] [drm:drm_dp_send_link_address [drm_kms_helper]] port 1: input 0, pdt: 3, pn: 8, dpcd_rev: 12, mcs: 0, ddps: 1, ldps 0, sdp 1/1
[ 1459.717059] [drm:drm_dp_send_link_address [drm_kms_helper]] port 2: input 0, pdt: 0, pn: 1, dpcd_rev: 00, mcs: 0, ddps: 0, ldps 0, sdp 0/0

The driver exposes a connector for the branch device in the MST monitor too, this connector is in disconnected state, but (as expected) we can read out the (branch device) DPCD from it.

The MST monitor has two output ports, on port 1 (pn 8) is its internal sink stream on port 2 (pn 1) is a daisy chain DP port. For both of these ports the driver exposes a connector, the latter one in disconnected state and the remote DPCD read for this will fail with a NAK/EIO error (as in the original case).

So atm the driver exposes a connector for all output ports of branch devices and the branch devices themselves have also a connector (both for the "root" branch device, card0-DP-3 above, and all downstream branch devices). All ports/connectors that have an SST sink plugged into them also expose an I2C and AUX device. Ports/connectors that have a branch device plugged into them only expose an AUX device.

Quoted 7 lines

I think this is consistent and (if so) it would make sense to document this somewhere as well.

One inconsistency I noticed is connector numbering, it depends on the plugging order. That's because all connectors are added first for any downstream branch device as they are enumarated on a port, before adding connectors on subsequent ports on the parent branch device.

So it uses dfs rather than bfs, if I understood correctly.

Quoted 6 lines

So in the above case where the dock is plugged with everything else already plugged to it DP-[569] belongs to the dock while DP-[78] belongs to the monitor. This could be made more consistent by adding first all the connectors on a branch device before enumerating any other branch devices attached to it.

Yeah, bfs approach could avoid a bit of randomness in the numbering when plugging things in different orders.

Signature · 6 lines
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Reviewed-by on v1 1/1
#12 lore raw
In reply to Imre Deak
Quoted 9 lines · Imre Deak

The DPCD of an MST connector is read out with a REMOTE_DPCD_READ MST request. If the given connector is disconnected this read will result in an MST NAK reply and this will be reported as an EIO error to the initiator of the AUX read.

Handle this in the test that attempts to read the DPCD of any exposed connector, whether they are connected or not.

Signed-off-by Imre Deak <[email protected]>
Reviewed-by Ville Syrjälä <[email protected]>
Quoted 46 lines
---
 tests/kms_dp_aux_dev.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)
tests/kms_dp_aux_dev.c +13 -3
index 4f52434a..39fc2b92 100644
@@ -34,6 +34,14 @@
 
 IGT_TEST_DESCRIPTION("Test that /dev/drm_dp_aux reads work");
 
+static bool is_mst_connector(int drm_fd, uint32_t connector_id)
+{
+	return kmstest_get_property(drm_fd, connector_id,
+				    DRM_MODE_OBJECT_CONNECTOR,
+				    "PATH", NULL,
+				    NULL, NULL);
+}
+
 static bool test(int drm_fd, uint32_t connector_id)
 {
 	drmModeConnector *connector;

@@ -67,10 +75,12 @@ static bool test(int drm_fd, uint32_t connector_id)
 		igt_assert(fd >= 0);
 
 		ret = read(fd, buf, sizeof(buf));
-		igt_assert(ret == sizeof(buf) || errno == ETIMEDOUT);
-
 		igt_info("%s: %s\n", path,
-			 ret > 0 ? "success" : "timed out");
+			 ret > 0 ? "success" : strerror(errno));
+
+		igt_assert(ret == sizeof(buf) ||
+			   errno == ETIMEDOUT ||
+			   (errno == EIO && is_mst_connector(drm_fd, connector_id)));
 
 		close(fd);
Signature · 6 lines
2.20.1

_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Signature · 6 lines
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev