All of lore.kernel.org
 help / color / mirror / Atom feed
* [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
@ 2020-10-12 17:56 Imre Deak
  2020-10-12 18:37 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
                   ` (5 more replies)
  0 siblings, 6 replies; 13+ messages in thread
From: Imre Deak @ 2020-10-12 17:56 UTC (permalink / raw)
  To: igt-dev

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 <imre.deak@intel.com>
---
 tests/kms_dp_aux_dev.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/tests/kms_dp_aux_dev.c b/tests/kms_dp_aux_dev.c
index 4f52434a..39fc2b92 100644
--- a/tests/kms_dp_aux_dev.c
+++ b/tests/kms_dp_aux_dev.c
@@ -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);
 
-- 
2.20.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply related	[flat|nested] 13+ messages in thread

* [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-12 17:56 [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors Imre Deak
@ 2020-10-12 18:37 ` Patchwork
  2020-10-12 19:57   ` Imre Deak
  2020-10-12 20:11 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
                   ` (4 subsequent siblings)
  5 siblings, 1 reply; 13+ messages in thread
From: Patchwork @ 2020-10-12 18:37 UTC (permalink / raw)
  To: Imre Deak; +Cc: igt-dev


[-- Attachment #1.1: Type: text/plain, Size: 6112 bytes --]

== 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@live@blt.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-snb-2520m/igt@i915_selftest@live@blt.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][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@i915_module_load@reload.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@i915_module_load@reload.html

  * 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@kms_chamelium@hdmi-crc-fast.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-fast.html

  * 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@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html

  * 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@basic-flip-vs-wf_vblank@c-edp1.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1.html

  * 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@vgem_basic@unload.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-skl-guc/igt@vgem_basic@unload.html

  
#### 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@gem_exec_suspend@basic-s0.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@gem_exec_suspend@basic-s0.html

  * 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@live@coherency.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-gdg-551/igt@i915_selftest@live@coherency.html

  * 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@basic-flip-vs-dpms@a-dsi1.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-dsi/igt@kms_flip@basic-flip-vs-dpms@a-dsi1.html

  * 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@basic-flip-vs-wf_vblank@b-edp1.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1.html

  
  {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

[-- Attachment #1.2: Type: text/html, Size: 7337 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-12 18:37 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
@ 2020-10-12 19:57   ` Imre Deak
  0 siblings, 0 replies; 13+ messages in thread
From: Imre Deak @ 2020-10-12 19:57 UTC (permalink / raw)
  To: igt-dev, Lakshminarayana Vudum

Hi Lakshmi,

On Mon, Oct 12, 2020 at 06:37:21PM +0000, Patchwork wrote:
> == 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@live@blt.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-snb-2520m/igt@i915_selftest@live@blt.html

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

> 
>   
> 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@i915_module_load@reload.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@i915_module_load@reload.html
> 
>   * 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@kms_chamelium@hdmi-crc-fast.html
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-fast.html
> 
>   * 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@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
> 
>   * 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@basic-flip-vs-wf_vblank@c-edp1.html
>    [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1.html
> 
>   * 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@vgem_basic@unload.html
>    [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-skl-guc/igt@vgem_basic@unload.html
> 
>   
> #### 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@gem_exec_suspend@basic-s0.html
>    [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@gem_exec_suspend@basic-s0.html
> 
>   * 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@live@coherency.html
>    [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-gdg-551/igt@i915_selftest@live@coherency.html
> 
>   * 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@basic-flip-vs-dpms@a-dsi1.html
>    [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-dsi/igt@kms_flip@basic-flip-vs-dpms@a-dsi1.html
> 
>   * 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@basic-flip-vs-wf_vblank@b-edp1.html
>    [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1.html
> 
>   
>   {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
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-12 17:56 [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors Imre Deak
  2020-10-12 18:37 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
@ 2020-10-12 20:11 ` Patchwork
  2020-10-13  0:52 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2020-10-12 20:11 UTC (permalink / raw)
  To: Imre Deak; +Cc: igt-dev


[-- Attachment #1.1: Type: text/plain, Size: 5729 bytes --]

== 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@i915_module_load@reload.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@i915_module_load@reload.html

  * 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@live@blt.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-snb-2520m/igt@i915_selftest@live@blt.html

  * 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@kms_chamelium@hdmi-crc-fast.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-fast.html

  * 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@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html

  * 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@basic-flip-vs-wf_vblank@c-edp1.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1.html

  * 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@vgem_basic@unload.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-skl-guc/igt@vgem_basic@unload.html

  
#### 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@gem_exec_suspend@basic-s0.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-u2/igt@gem_exec_suspend@basic-s0.html

  * 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@live@coherency.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-gdg-551/igt@i915_selftest@live@coherency.html

  * 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@basic-flip-vs-dpms@a-dsi1.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-tgl-dsi/igt@kms_flip@basic-flip-vs-dpms@a-dsi1.html

  * 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@basic-flip-vs-wf_vblank@b-edp1.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1.html

  
  {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

[-- Attachment #1.2: Type: text/html, Size: 6942 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-12 17:56 [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors Imre Deak
  2020-10-12 18:37 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
  2020-10-12 20:11 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
@ 2020-10-13  0:52 ` Patchwork
  2020-10-13  7:18 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2020-10-13  0:52 UTC (permalink / raw)
  To: Imre Deak; +Cc: igt-dev


[-- Attachment #1.1: Type: text/plain, Size: 20946 bytes --]

== 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@gem_exec_whisper@basic-fds-forked.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@gem_exec_whisper@basic-fds-forked.html

  * 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@gem_linear_blits@interruptible.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb2/igt@gem_linear_blits@interruptible.html

  * 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@dpms-off-confusion@c-hdmi-a1.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw7/igt@kms_flip@dpms-off-confusion@c-hdmi-a1.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][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@basic-many-active@rcs0.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl3/igt@gem_exec_reloc@basic-many-active@rcs0.html

  * 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@basic-many-active@vcs0.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk7/igt@gem_exec_reloc@basic-many-active@vcs0.html

  * 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@gem_exec_whisper@basic-forked-all.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk6/igt@gem_exec_whisper@basic-forked-all.html

  * 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@gem_huc_copy@huc-copy.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb6/igt@gem_huc_copy@huc-copy.html

  * 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@gem_mmap_wc@copy.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@gem_mmap_wc@copy.html

  * 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@kms_big_fb@y-tiled-32bpp-rotate-0.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@kms_big_fb@y-tiled-32bpp-rotate-0.html

  * 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@kms_big_fb@yf-tiled-32bpp-rotate-0.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl2/igt@kms_big_fb@yf-tiled-32bpp-rotate-0.html

  * 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@kms_cursor_crc@pipe-c-cursor-256x256-onscreen.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk9/igt@kms_cursor_crc@pipe-c-cursor-256x256-onscreen.html

  * 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@kms_cursor_crc@pipe-c-cursor-suspend.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
    - 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@kms_cursor_crc@pipe-c-cursor-suspend.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl7/igt@kms_cursor_crc@pipe-c-cursor-suspend.html

  * 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@feature_discovery@psr2.html
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@feature_discovery@psr2.html

  * {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@pi@rcs0.html
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk9/igt@gem_exec_capture@pi@rcs0.html

  * 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@gem_exec_schedule@smoketest-all.html
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk4/igt@gem_exec_schedule@smoketest-all.html

  * 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@gem_mmap_offset@blt-coherency.html
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk5/igt@gem_mmap_offset@blt-coherency.html

  * 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@gem_partial_pwrite_pread@writes-after-reads.html
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@gem_partial_pwrite_pread@writes-after-reads.html
    - shard-snb:          [INCOMPLETE][45] ([i915#82]) -> [PASS][46]
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-snb7/igt@gem_partial_pwrite_pread@writes-after-reads.html
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb5/igt@gem_partial_pwrite_pread@writes-after-reads.html

  * 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@gem_render_copy@y-tiled.html
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk2/igt@gem_render_copy@y-tiled.html
    - 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@gem_render_copy@y-tiled.html
   [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl1/igt@gem_render_copy@y-tiled.html
    - shard-kbl:          [FAIL][51] ([i915#2541]) -> [PASS][52]
   [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl4/igt@gem_render_copy@y-tiled.html
   [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@gem_render_copy@y-tiled.html
    - shard-hsw:          [FAIL][53] ([i915#2541]) -> [PASS][54]
   [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@gem_render_copy@y-tiled.html
   [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@gem_render_copy@y-tiled.html
    - shard-iclb:         [FAIL][55] ([i915#2541]) -> [PASS][56]
   [55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb1/igt@gem_render_copy@y-tiled.html
   [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb6/igt@gem_render_copy@y-tiled.html

  * 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb5/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html

  * 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@i915_suspend@fence-restore-tiled2untiled.html
   [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@i915_suspend@fence-restore-tiled2untiled.html

  * {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@kms_async_flips@async-flip-with-page-flip-events.html
   [62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@kms_async_flips@async-flip-with-page-flip-events.html

  * 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@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
   [64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl6/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html

  * 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@kms_hdmi_inject@inject-audio.html
   [66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb5/igt@kms_hdmi_inject@inject-audio.html

  * 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@kms_plane_lowres@pipe-a-tiling-y.html
   [68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-y.html

  * 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@kms_setmode@basic.html
   [72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl8/igt@kms_setmode@basic.html
    - shard-hsw:          [FAIL][73] ([i915#31]) -> [PASS][74]
   [73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw4/igt@kms_setmode@basic.html
   [74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@kms_setmode@basic.html

  * 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@kms_universal_plane@universal-plane-gen9-features-pipe-b.html
   [76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb2/igt@kms_universal_plane@universal-plane-gen9-features-pipe-b.html

  * 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@perf@invalid-oa-exponent.html
   [78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw2/igt@perf@invalid-oa-exponent.html
    - shard-iclb:         [SKIP][79] ([i915#405]) -> [PASS][80]
   [79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb6/igt@perf@invalid-oa-exponent.html
   [80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb3/igt@perf@invalid-oa-exponent.html
    - shard-glk:          [SKIP][81] ([fdo#109271]) -> [PASS][82]
   [81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk5/igt@perf@invalid-oa-exponent.html
   [82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk2/igt@perf@invalid-oa-exponent.html
    - shard-tglb:         [SKIP][83] ([i915#405]) -> [PASS][84]
   [83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb6/igt@perf@invalid-oa-exponent.html
   [84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb8/igt@perf@invalid-oa-exponent.html
    - 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@perf@invalid-oa-exponent.html
   [86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl7/igt@perf@invalid-oa-exponent.html
    - shard-kbl:          [SKIP][87] ([fdo#109271]) -> [PASS][88]
   [87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl6/igt@perf@invalid-oa-exponent.html
   [88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@perf@invalid-oa-exponent.html

  * 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@perf@polling-parameterized.html
   [90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk1/igt@perf@polling-parameterized.html

  
#### 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw1/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb7/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl3/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb7/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk6/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html

  
  {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

[-- Attachment #1.2: Type: text/html, Size: 25322 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [igt-dev] ✓ Fi.CI.IGT: success for tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-12 17:56 [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors Imre Deak
                   ` (2 preceding siblings ...)
  2020-10-13  0:52 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
@ 2020-10-13  7:18 ` Patchwork
  2020-10-13 11:27 ` [igt-dev] [PATCH] " Ville Syrjälä
  2020-10-15 19:08 ` Ville Syrjälä
  5 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2020-10-13  7:18 UTC (permalink / raw)
  To: Imre Deak; +Cc: igt-dev


[-- Attachment #1.1: Type: text/plain, Size: 20710 bytes --]

== 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@basic-many-active@rcs0.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl3/igt@gem_exec_reloc@basic-many-active@rcs0.html

  * 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@basic-many-active@vcs0.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk7/igt@gem_exec_reloc@basic-many-active@vcs0.html

  * 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@gem_exec_whisper@basic-fds-forked.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@gem_exec_whisper@basic-fds-forked.html

  * 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@gem_exec_whisper@basic-forked-all.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk6/igt@gem_exec_whisper@basic-forked-all.html

  * 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@gem_huc_copy@huc-copy.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb6/igt@gem_huc_copy@huc-copy.html

  * 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@gem_linear_blits@interruptible.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb2/igt@gem_linear_blits@interruptible.html

  * 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@gem_mmap_wc@copy.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@gem_mmap_wc@copy.html

  * 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@kms_big_fb@y-tiled-32bpp-rotate-0.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@kms_big_fb@y-tiled-32bpp-rotate-0.html

  * 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@kms_big_fb@yf-tiled-32bpp-rotate-0.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl2/igt@kms_big_fb@yf-tiled-32bpp-rotate-0.html

  * 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@kms_cursor_crc@pipe-c-cursor-256x256-onscreen.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk9/igt@kms_cursor_crc@pipe-c-cursor-256x256-onscreen.html

  * 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@kms_cursor_crc@pipe-c-cursor-suspend.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
    - 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@kms_cursor_crc@pipe-c-cursor-suspend.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl7/igt@kms_cursor_crc@pipe-c-cursor-suspend.html

  * 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@dpms-off-confusion@c-hdmi-a1.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw7/igt@kms_flip@dpms-off-confusion@c-hdmi-a1.html

  * 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@feature_discovery@psr2.html
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb2/igt@feature_discovery@psr2.html

  * {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@pi@rcs0.html
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk9/igt@gem_exec_capture@pi@rcs0.html

  * 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@gem_exec_schedule@smoketest-all.html
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk4/igt@gem_exec_schedule@smoketest-all.html

  * 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@gem_mmap_offset@blt-coherency.html
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk5/igt@gem_mmap_offset@blt-coherency.html

  * 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@gem_partial_pwrite_pread@writes-after-reads.html
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@gem_partial_pwrite_pread@writes-after-reads.html
    - shard-snb:          [INCOMPLETE][45] ([i915#82]) -> [PASS][46]
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-snb7/igt@gem_partial_pwrite_pread@writes-after-reads.html
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb5/igt@gem_partial_pwrite_pread@writes-after-reads.html

  * 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@gem_render_copy@y-tiled.html
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk2/igt@gem_render_copy@y-tiled.html
    - 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@gem_render_copy@y-tiled.html
   [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl1/igt@gem_render_copy@y-tiled.html
    - shard-kbl:          [FAIL][51] ([i915#2541]) -> [PASS][52]
   [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl4/igt@gem_render_copy@y-tiled.html
   [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@gem_render_copy@y-tiled.html
    - shard-hsw:          [FAIL][53] ([i915#2541]) -> [PASS][54]
   [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw5/igt@gem_render_copy@y-tiled.html
   [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@gem_render_copy@y-tiled.html
    - shard-iclb:         [FAIL][55] ([i915#2541]) -> [PASS][56]
   [55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb1/igt@gem_render_copy@y-tiled.html
   [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb6/igt@gem_render_copy@y-tiled.html

  * 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb5/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html

  * 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@i915_suspend@fence-restore-tiled2untiled.html
   [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@i915_suspend@fence-restore-tiled2untiled.html

  * {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@kms_async_flips@async-flip-with-page-flip-events.html
   [62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@kms_async_flips@async-flip-with-page-flip-events.html

  * 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@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
   [64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl6/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html

  * 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@kms_hdmi_inject@inject-audio.html
   [66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb5/igt@kms_hdmi_inject@inject-audio.html

  * 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@kms_plane_lowres@pipe-a-tiling-y.html
   [68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-y.html

  * 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@kms_setmode@basic.html
   [72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl8/igt@kms_setmode@basic.html
    - shard-hsw:          [FAIL][73] ([i915#31]) -> [PASS][74]
   [73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-hsw4/igt@kms_setmode@basic.html
   [74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw6/igt@kms_setmode@basic.html

  * 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@kms_universal_plane@universal-plane-gen9-features-pipe-b.html
   [76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb2/igt@kms_universal_plane@universal-plane-gen9-features-pipe-b.html

  * 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@perf@invalid-oa-exponent.html
   [78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw2/igt@perf@invalid-oa-exponent.html
    - shard-iclb:         [SKIP][79] ([i915#405]) -> [PASS][80]
   [79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-iclb6/igt@perf@invalid-oa-exponent.html
   [80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb3/igt@perf@invalid-oa-exponent.html
    - shard-glk:          [SKIP][81] ([fdo#109271]) -> [PASS][82]
   [81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-glk5/igt@perf@invalid-oa-exponent.html
   [82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk2/igt@perf@invalid-oa-exponent.html
    - shard-tglb:         [SKIP][83] ([i915#405]) -> [PASS][84]
   [83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-tglb6/igt@perf@invalid-oa-exponent.html
   [84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-tglb8/igt@perf@invalid-oa-exponent.html
    - 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@perf@invalid-oa-exponent.html
   [86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl7/igt@perf@invalid-oa-exponent.html
    - shard-kbl:          [SKIP][87] ([fdo#109271]) -> [PASS][88]
   [87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9130/shard-kbl6/igt@perf@invalid-oa-exponent.html
   [88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl6/igt@perf@invalid-oa-exponent.html

  * 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@perf@polling-parameterized.html
   [90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk1/igt@perf@polling-parameterized.html

  
#### 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-hsw1/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-kbl1/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-snb7/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-apl3/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-iclb7/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
    - 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@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html
   [102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5060/shard-glk6/igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-yf-tiled.html

  
  {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

[-- Attachment #1.2: Type: text/html, Size: 25063 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-12 17:56 [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors Imre Deak
                   ` (3 preceding siblings ...)
  2020-10-13  7:18 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
@ 2020-10-13 11:27 ` Ville Syrjälä
  2020-10-13 11:36   ` Imre Deak
  2020-10-15 19:08 ` Ville Syrjälä
  5 siblings, 1 reply; 13+ messages in thread
From: Ville Syrjälä @ 2020-10-13 11:27 UTC (permalink / raw)
  To: Imre Deak; +Cc: igt-dev

On Mon, Oct 12, 2020 at 08:56:54PM +0300, Imre Deak wrote:
> 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?

> 
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
>  tests/kms_dp_aux_dev.c | 16 +++++++++++++---
>  1 file changed, 13 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/kms_dp_aux_dev.c b/tests/kms_dp_aux_dev.c
> index 4f52434a..39fc2b92 100644
> --- a/tests/kms_dp_aux_dev.c
> +++ b/tests/kms_dp_aux_dev.c
> @@ -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);
>  
> -- 
> 2.20.1
> 
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev

-- 
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-13 11:27 ` [igt-dev] [PATCH] " Ville Syrjälä
@ 2020-10-13 11:36   ` Imre Deak
  2020-10-13 12:56     ` Ville Syrjälä
  0 siblings, 1 reply; 13+ messages in thread
From: Imre Deak @ 2020-10-13 11:36 UTC (permalink / raw)
  To: Ville Syrjälä; +Cc: igt-dev

On Tue, Oct 13, 2020 at 02:27:12PM +0300, Ville Syrjälä wrote:
> On Mon, Oct 12, 2020 at 08:56:54PM +0300, Imre Deak wrote:
> > 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.

> 
> > 
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> >  tests/kms_dp_aux_dev.c | 16 +++++++++++++---
> >  1 file changed, 13 insertions(+), 3 deletions(-)
> > 
> > diff --git a/tests/kms_dp_aux_dev.c b/tests/kms_dp_aux_dev.c
> > index 4f52434a..39fc2b92 100644
> > --- a/tests/kms_dp_aux_dev.c
> > +++ b/tests/kms_dp_aux_dev.c
> > @@ -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);
> >  
> > -- 
> > 2.20.1
> > 
> > _______________________________________________
> > igt-dev mailing list
> > igt-dev@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/igt-dev
> 
> -- 
> Ville Syrjälä
> Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-13 11:36   ` Imre Deak
@ 2020-10-13 12:56     ` Ville Syrjälä
  2020-10-13 13:19       ` Imre Deak
  0 siblings, 1 reply; 13+ messages in thread
From: Ville Syrjälä @ 2020-10-13 12:56 UTC (permalink / raw)
  To: Imre Deak; +Cc: igt-dev

On Tue, Oct 13, 2020 at 02:36:32PM +0300, Imre Deak wrote:
> On Tue, Oct 13, 2020 at 02:27:12PM +0300, Ville Syrjälä wrote:
> > On Mon, Oct 12, 2020 at 08:56:54PM +0300, Imre Deak wrote:
> > > 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.

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.

> 
> > 
> > > 
> > > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > > ---
> > >  tests/kms_dp_aux_dev.c | 16 +++++++++++++---
> > >  1 file changed, 13 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/tests/kms_dp_aux_dev.c b/tests/kms_dp_aux_dev.c
> > > index 4f52434a..39fc2b92 100644
> > > --- a/tests/kms_dp_aux_dev.c
> > > +++ b/tests/kms_dp_aux_dev.c
> > > @@ -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);
> > >  
> > > -- 
> > > 2.20.1
> > > 
> > > _______________________________________________
> > > igt-dev mailing list
> > > igt-dev@lists.freedesktop.org
> > > https://lists.freedesktop.org/mailman/listinfo/igt-dev
> > 
> > -- 
> > Ville Syrjälä
> > Intel

-- 
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-13 12:56     ` Ville Syrjälä
@ 2020-10-13 13:19       ` Imre Deak
  2020-10-15 14:29         ` Imre Deak
  0 siblings, 1 reply; 13+ messages in thread
From: Imre Deak @ 2020-10-13 13:19 UTC (permalink / raw)
  To: Ville Syrjälä; +Cc: igt-dev

On Tue, Oct 13, 2020 at 03:56:30PM +0300, Ville Syrjälä wrote:
> On Tue, Oct 13, 2020 at 02:36:32PM +0300, Imre Deak wrote:
> > On Tue, Oct 13, 2020 at 02:27:12PM +0300, Ville Syrjälä wrote:
> > > On Mon, Oct 12, 2020 at 08:56:54PM +0300, Imre Deak wrote:
> > > > 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.
> 
> 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.

> 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



> > > > 
> > > > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > > > ---
> > > >  tests/kms_dp_aux_dev.c | 16 +++++++++++++---
> > > >  1 file changed, 13 insertions(+), 3 deletions(-)
> > > > 
> > > > diff --git a/tests/kms_dp_aux_dev.c b/tests/kms_dp_aux_dev.c
> > > > index 4f52434a..39fc2b92 100644
> > > > --- a/tests/kms_dp_aux_dev.c
> > > > +++ b/tests/kms_dp_aux_dev.c
> > > > @@ -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);
> > > >  
> > > > -- 
> > > > 2.20.1
> > > > 
> > > > _______________________________________________
> > > > igt-dev mailing list
> > > > igt-dev@lists.freedesktop.org
> > > > https://lists.freedesktop.org/mailman/listinfo/igt-dev
> > > 
> > > -- 
> > > Ville Syrjälä
> > > Intel
> 
> -- 
> Ville Syrjälä
> Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-13 13:19       ` Imre Deak
@ 2020-10-15 14:29         ` Imre Deak
  2020-10-15 19:08           ` Ville Syrjälä
  0 siblings, 1 reply; 13+ messages in thread
From: Imre Deak @ 2020-10-15 14:29 UTC (permalink / raw)
  To: Ville Syrjälä; +Cc: igt-dev

On Tue, Oct 13, 2020 at 04:19:06PM +0300, Imre Deak wrote:
> On Tue, Oct 13, 2020 at 03:56:30PM +0300, Ville Syrjälä wrote:
> > On Tue, Oct 13, 2020 at 02:36:32PM +0300, Imre Deak wrote:
> > > On Tue, Oct 13, 2020 at 02:27:12PM +0300, Ville Syrjälä wrote:
> > > > On Mon, Oct 12, 2020 at 08:56:54PM +0300, Imre Deak wrote:
> > > > > 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.
> > 
> > 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.
> 
> > 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.

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
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-15 14:29         ` Imre Deak
@ 2020-10-15 19:08           ` Ville Syrjälä
  0 siblings, 0 replies; 13+ messages in thread
From: Ville Syrjälä @ 2020-10-15 19:08 UTC (permalink / raw)
  To: Imre Deak; +Cc: igt-dev

On Thu, Oct 15, 2020 at 05:29:35PM +0300, Imre Deak wrote:
> On Tue, Oct 13, 2020 at 04:19:06PM +0300, Imre Deak wrote:
> > On Tue, Oct 13, 2020 at 03:56:30PM +0300, Ville Syrjälä wrote:
> > > On Tue, Oct 13, 2020 at 02:36:32PM +0300, Imre Deak wrote:
> > > > On Tue, Oct 13, 2020 at 02:27:12PM +0300, Ville Syrjälä wrote:
> > > > > On Mon, Oct 12, 2020 at 08:56:54PM +0300, Imre Deak wrote:
> > > > > > 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.
> > > 
> > > 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.
> > 
> > > 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.
> 
> 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 it uses dfs rather than bfs, if I understood correctly.

> 
> 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.

-- 
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors
  2020-10-12 17:56 [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors Imre Deak
                   ` (4 preceding siblings ...)
  2020-10-13 11:27 ` [igt-dev] [PATCH] " Ville Syrjälä
@ 2020-10-15 19:08 ` Ville Syrjälä
  5 siblings, 0 replies; 13+ messages in thread
From: Ville Syrjälä @ 2020-10-15 19:08 UTC (permalink / raw)
  To: Imre Deak; +Cc: igt-dev

On Mon, Oct 12, 2020 at 08:56:54PM +0300, Imre Deak wrote:
> 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 <imre.deak@intel.com>

Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> ---
>  tests/kms_dp_aux_dev.c | 16 +++++++++++++---
>  1 file changed, 13 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/kms_dp_aux_dev.c b/tests/kms_dp_aux_dev.c
> index 4f52434a..39fc2b92 100644
> --- a/tests/kms_dp_aux_dev.c
> +++ b/tests/kms_dp_aux_dev.c
> @@ -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);
>  
> -- 
> 2.20.1
> 
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev

-- 
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2020-10-15 19:08 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-12 17:56 [igt-dev] [PATCH] tests/kms_dp_aux_dev: Handle AUX failures on disconnected MST connectors Imre Deak
2020-10-12 18:37 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2020-10-12 19:57   ` Imre Deak
2020-10-12 20:11 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-10-13  0:52 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-13  7:18 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2020-10-13 11:27 ` [igt-dev] [PATCH] " Ville Syrjälä
2020-10-13 11:36   ` Imre Deak
2020-10-13 12:56     ` Ville Syrjälä
2020-10-13 13:19       ` Imre Deak
2020-10-15 14:29         ` Imre Deak
2020-10-15 19:08           ` Ville Syrjälä
2020-10-15 19:08 ` Ville Syrjälä

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.