From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx@lists.freedesktop.org,
Martin Peres <martin.peres@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for HDCP2.2 Phase II (rev14)
Date: Fri, 2 Aug 2019 12:34:10 +0530 [thread overview]
Message-ID: <20190802070409.GA16854@intel.com> (raw)
In-Reply-To: <20190801184316.30397.52163@emeril.freedesktop.org>
On 2019-08-01 at 18:43:16 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: HDCP2.2 Phase II (rev14)
> URL : https://patchwork.freedesktop.org/series/57232/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_6605 -> Patchwork_13834
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_13834 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_13834, 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/Patchwork_13834/
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_13834:
>
> ### IGT changes ###
>
> #### Possible regressions ####
Martin,
There is no regression in this test result. Known skips and expected
failures due to hdcp sinks are observed on the new HDCP test called
"SRM".
I have provided the reasoning for each observations below. With these
filters in CI results supposed to be GREEN.
How should we proceed here further? Thanks.
>
> * igt@i915_module_load@reload-with-fault-injection:
> - fi-skl-6770hq: [PASS][1] -> [DMESG-WARN][2] +2 similar issues
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-skl-6770hq/igt@i915_module_load@reload-with-fault-injection.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-skl-6770hq/igt@i915_module_load@reload-with-fault-injection.html
These dmesg warnings are caused due to the DP aux transfer failures.
[drm:intel_dp_aux_xfer [i915]] dp_aux_ch timeout status 0x7d4003ff
>
> * {igt@kms_content_protection@srm} (NEW):
SRM test is newly added at
https://patchwork.freedesktop.org/series/57756/ and used here to test.
> - fi-cfl-8109u: NOTRUN -> [FAIL][3]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-cfl-8109u/igt@kms_content_protection@srm.html
Failed due to the known HDCP error on LspCON
<7> [388.944041] [drm:intel_hdcp_auth [i915]] KSV list failed to become ready (-110)
> - {fi-icl-u4}: NOTRUN -> [SKIP][4]
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-icl-u4/igt@kms_content_protection@srm.html
> - fi-icl-dsi: NOTRUN -> [SKIP][5]
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-icl-dsi/igt@kms_content_protection@srm.html
Above two tests are expected to skip as No connector found with HDCP
capability.
> - fi-skl-lmem: NOTRUN -> [FAIL][6]
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-skl-lmem/igt@kms_content_protection@srm.html
> - fi-apl-guc: NOTRUN -> [FAIL][7]
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-apl-guc/igt@kms_content_protection@srm.html
Above two tests expected failed due to the known HDCP error on LspCON
<7> [459.700324] [drm:intel_hdcp_auth [i915]] KSV list failed to become ready (-110)
> - fi-icl-u3: NOTRUN -> [FAIL][8]
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-icl-u3/igt@kms_content_protection@srm.html
Failed due to invalid BKSV. Hence expected behaviour on this sink.
<7> [296.873715] [drm:intel_hdcp_read_valid_bksv.isra.1 [i915]] Bksv is invalid
> - fi-cml-u2: NOTRUN -> [SKIP][9]
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-cml-u2/igt@kms_content_protection@srm.html
Test expected to skip as No connector found with HDCP capability.
-Ram
>
>
> New tests
> ---------
>
> New tests have been introduced between CI_DRM_6605 and Patchwork_13834:
>
> ### New IGT tests (1) ###
>
> * igt@kms_content_protection@srm:
> - Statuses : 4 fail(s) 5 pass(s) 34 skip(s)
> - Exec time: [0.0, 130.44] s
>
>
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_13834 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@kms_addfb_basic@size-max:
> - fi-icl-u3: [PASS][10] -> [DMESG-WARN][11] ([fdo#107724])
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-icl-u3/igt@kms_addfb_basic@size-max.html
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-icl-u3/igt@kms_addfb_basic@size-max.html
>
> * igt@kms_chamelium@dp-hpd-fast:
> - fi-kbl-7500u: [PASS][12] -> [DMESG-WARN][13] ([fdo#103558] / [fdo#105602])
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-kbl-7500u/igt@kms_chamelium@dp-hpd-fast.html
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-kbl-7500u/igt@kms_chamelium@dp-hpd-fast.html
>
> * igt@kms_flip@basic-flip-vs-dpms:
> - fi-skl-6770hq: [PASS][14] -> [SKIP][15] ([fdo#109271]) +23 similar issues
> [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-skl-6770hq/igt@kms_flip@basic-flip-vs-dpms.html
> [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-skl-6770hq/igt@kms_flip@basic-flip-vs-dpms.html
>
> * igt@prime_vgem@basic-fence-mmap:
> - fi-elk-e7500: [PASS][16] -> [INCOMPLETE][17] ([fdo#103989] / [fdo#111276])
> [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-elk-e7500/igt@prime_vgem@basic-fence-mmap.html
> [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-elk-e7500/igt@prime_vgem@basic-fence-mmap.html
>
> * igt@prime_vgem@basic-fence-read:
> - fi-bsw-kefka: [PASS][18] -> [INCOMPLETE][19] ([fdo#111278])
> [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-bsw-kefka/igt@prime_vgem@basic-fence-read.html
> [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-bsw-kefka/igt@prime_vgem@basic-fence-read.html
>
>
> #### Possible fixes ####
>
> * igt@i915_module_load@reload:
> - fi-icl-u3: [DMESG-WARN][20] ([fdo#107724]) -> [PASS][21]
> [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-icl-u3/igt@i915_module_load@reload.html
> [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-icl-u3/igt@i915_module_load@reload.html
>
> * igt@i915_selftest@live_execlists:
> - fi-skl-gvtdvm: [DMESG-FAIL][22] ([fdo#111108]) -> [PASS][23]
> [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-skl-gvtdvm/igt@i915_selftest@live_execlists.html
> [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-skl-gvtdvm/igt@i915_selftest@live_execlists.html
>
> * igt@kms_busy@basic-flip-a:
> - fi-kbl-7567u: [SKIP][24] ([fdo#109271] / [fdo#109278]) -> [PASS][25] +2 similar issues
> [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-kbl-7567u/igt@kms_busy@basic-flip-a.html
> [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-kbl-7567u/igt@kms_busy@basic-flip-a.html
>
> * igt@kms_chamelium@hdmi-hpd-fast:
> - fi-kbl-7500u: [FAIL][26] ([fdo#109485]) -> [PASS][27]
> [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
> [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
>
> * igt@prime_vgem@basic-busy-default:
> - fi-bxt-j4205: [FAIL][28] ([fdo#111277]) -> [PASS][29]
> [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-bxt-j4205/igt@prime_vgem@basic-busy-default.html
> [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-bxt-j4205/igt@prime_vgem@basic-busy-default.html
>
> * igt@prime_vgem@basic-fence-mmap:
> - fi-pnv-d510: [INCOMPLETE][30] ([fdo#110740] / [fdo#111276]) -> [PASS][31]
> [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6605/fi-pnv-d510/igt@prime_vgem@basic-fence-mmap.html
> [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-pnv-d510/igt@prime_vgem@basic-fence-mmap.html
>
>
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> [fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
> [fdo#103989]: https://bugs.freedesktop.org/show_bug.cgi?id=103989
> [fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
> [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
> [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
> [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
> [fdo#109485]: https://bugs.freedesktop.org/show_bug.cgi?id=109485
> [fdo#110740]: https://bugs.freedesktop.org/show_bug.cgi?id=110740
> [fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
> [fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
> [fdo#111108]: https://bugs.freedesktop.org/show_bug.cgi?id=111108
> [fdo#111276]: https://bugs.freedesktop.org/show_bug.cgi?id=111276
> [fdo#111277]: https://bugs.freedesktop.org/show_bug.cgi?id=111277
> [fdo#111278]: https://bugs.freedesktop.org/show_bug.cgi?id=111278
>
>
> Participating hosts (47 -> 44)
> ------------------------------
>
> Additional (2): fi-icl-dsi fi-apl-guc
> Missing (5): fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus
>
>
> Build changes
> -------------
>
> * CI: CI-20190529 -> None
> * IGT: IGT_5120 -> IGTPW_3263
> * Linux: CI_DRM_6605 -> Patchwork_13834
>
> CI-20190529: 20190529
> CI_DRM_6605: 09970f7b8f1336416254cfac87f196578e3c1d13 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGTPW_3263: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3263/
> IGT_5120: b3138fbea79d5d7935e53530b90efe3e816236f4 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_13834: 26394e4cc3b27ba4aecaab2bff93fd036a2c3f91 @ git://anongit.freedesktop.org/gfx-ci/linux
>
>
> == Linux commits ==
>
> 26394e4cc3b2 drm/hdcp: reference for srm file format
> f052ab943daa drm/i915: update the hdcp state with uevent
> 3b164c38b461 drm/hdcp: update content protection property with uevent
> add126230c60 drm: uevent for connector status change
> 5a8acad0bc86 drm/i915: Attach content type property
> ce79e1d0d5a1 drm: Add Content protection type property
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-02 7:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 11:41 [PATCH v12 0/6] HDCP2.2 Phase II Ramalingam C
2019-08-01 11:41 ` [PATCH v12 1/6] drm: Add Content protection type property Ramalingam C
2019-08-01 11:41 ` [PATCH v12 2/6] drm/i915: Attach content " Ramalingam C
2019-08-01 11:41 ` [PATCH v12 3/6] drm: uevent for connector status change Ramalingam C
2019-08-01 11:41 ` [PATCH v12 4/6] drm/hdcp: update content protection property with uevent Ramalingam C
2019-08-01 11:41 ` [PATCH v12 5/6] drm/i915: update the hdcp state " Ramalingam C
2019-08-01 11:41 ` [PATCH v12 6/6] drm/hdcp: reference for srm file format Ramalingam C
2019-08-01 18:17 ` ✗ Fi.CI.CHECKPATCH: warning for HDCP2.2 Phase II (rev14) Patchwork
2019-08-01 18:43 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-08-02 7:04 ` Ramalingam C [this message]
2019-08-14 12:17 ` Martin Peres
2019-08-05 8:09 ` [Intel-gfx] [PATCH v12 0/6] HDCP2.2 Phase II Jani Nikula
2019-08-06 10:29 ` Ramalingam C
2019-08-14 14:30 ` ✗ Fi.CI.BAT: failure for HDCP2.2 Phase II (rev15) Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190802070409.GA16854@intel.com \
--to=ramalingam.c@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=martin.peres@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.