[Intel-gfx] ✗ Fi.CI.BAT: failure for Enabling the IGT for HDCP1.4 (rev4)

Tue Oct 23 08:03:26 UTC 2018

On 10/23/2018 1:15 PM, Martin Peres wrote:
> On 23/10/2018 08:42, C, Ramalingam wrote:
>> On 10/22/2018 10:47 PM, Patchwork wrote:
>>> == Series Details ==
>>>
>>> Series: Enabling the IGT for HDCP1.4 (rev4)
>>> URL   : https://patchwork.freedesktop.org/series/51113/
>>> State : failure
>>>
>>> == Summary ==
>>>
>>> = CI Bug Log - changes from CI_DRM_5017 -> Patchwork_10527 =
>>>
>>> == Summary - FAILURE ==
>>>
>>>    Serious unknown changes coming with Patchwork_10527 absolutely need to be
>>>    verified manually.
>>>    
>>>    If you think the reported changes have nothing to do with the changes
>>>    introduced in Patchwork_10527, please notify your bug team to allow them
>>>    to document this new failure mode, which will reduce false positives in CI.
>>>
>>>    External URL: https://patchwork.freedesktop.org/api/1.0/series/51113/revisions/4/mbox/
>>>
>>> == Possible new issues ==
>>>
>>>    Here are the unknown changes that may have been introduced in Patchwork_10527:
>>>
>>>    === IGT changes ===
>>>
>>>      ==== Possible regressions ====
>>>
>>>      igt at debugfs_test@read_all_entries:
>>>        fi-skl-iommu:       PASS -> DMESG-WARN
>>>        fi-bdw-gvtdvm:      PASS -> DMESG-WARN
>>>        fi-bdw-5557u:       PASS -> DMESG-WARN
>>>        fi-skl-guc:         PASS -> DMESG-WARN
>>>        fi-glk-j4005:       PASS -> DMESG-WARN
>>>        fi-cfl-8700k:       PASS -> DMESG-WARN
>>>        fi-cfl-guc:         PASS -> DMESG-WARN
>> All these dmesg warnings are there because of the sink in CI which doesn't support hdcp registers. Which is expected in case of dummy HDMI sinks.
>> So we could go ahead and merge these patches.
> DMESG-WARN is not allowed for any test, so the patch is currently
> unacceptable. Please simply report that the sync does not support HDCP
> in i915_hdcp_sink_capability, but no warnings are allowed in dmesg.
>
> In Linux, we put the cost of integration on the person writing the
> patch. Thus, if you need to rework the internals of i915 to achieve a
> warning-free dmesg log, you will be expected to do so, so as not to
> regress anything.

Thanks Martin, for pointing it out. These errors were part of authentication we have.
New patches are using a routine from auth flow hence when DDC request fail caused these errors.
As I had a closure with danvet, I will move these errors to debug level.

>
> Looking forward to seeing an updated patch :)
>
> PS: The retry button should not be pressed lightly as it steals machine
> time from other tasks. If you believe some noise might just have
> happened and blocked the testing of your patch series, please contact me
> to file a bug in our suppression system (CI Bug Log) *before* being
> allowed to press the button.

Agreed. At first attempt to request retest I saw that without result update,
re-queued for test state was gone. So clicked couple of times.
I remember this mistake next time. :)

Thanks,
--Ram

>
>> --Ram
>>
>>>      
>>> == Known issues ==
>>>
>>>    Here are the changes found in Patchwork_10527 that come from known issues:
>>>
>>>    === IGT changes ===
>>>
>>>      ==== Issues hit ====
>>>
>>>      igt at gem_exec_store@basic-all:
>>>        fi-icl-u:           NOTRUN -> DMESG-WARN (fdo#107732) +5
>>>
>>>      igt at gem_exec_suspend@basic:
>>>        fi-icl-u:           NOTRUN -> DMESG-WARN (fdo#107724) +24
>>>
>>>      igt at gem_exec_suspend@basic-s3:
>>>        fi-icl-u:           NOTRUN -> DMESG-WARN (fdo#108512)
>>>
>>>      igt at gem_mmap@basic-small-bo:
>>>        fi-icl-u2:          NOTRUN -> DMESG-WARN (fdo#107732) +1
>>>
>>>      
>>>      ==== Possible fixes ====
>>>
>>>      igt at gem_exec_suspend@basic-s4-devices:
>>>        fi-kbl-7500u:       DMESG-WARN (fdo#105128, fdo#107139) -> PASS
>>>
>>>      igt at kms_frontbuffer_tracking@basic:
>>>        fi-byt-clapper:     FAIL (fdo#103167) -> PASS
>>>
>>>      igt at prime_vgem@basic-fence-flip:
>>>        fi-cfl-8700k:       FAIL (fdo#104008) -> PASS
>>>
>>>      
>>>    fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
>>>    fdo#104008 https://bugs.freedesktop.org/show_bug.cgi?id=104008
>>>    fdo#105128 https://bugs.freedesktop.org/show_bug.cgi?id=105128
>>>    fdo#107139 https://bugs.freedesktop.org/show_bug.cgi?id=107139
>>>    fdo#107724 https://bugs.freedesktop.org/show_bug.cgi?id=107724
>>>    fdo#107732 https://bugs.freedesktop.org/show_bug.cgi?id=107732
>>>    fdo#108512 https://bugs.freedesktop.org/show_bug.cgi?id=108512
>>>
>>>
>>> == Participating hosts (51 -> 46) ==
>>>
>>>    Additional (1): fi-icl-u
>>>    Missing    (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-snb-2520m fi-ctg-p8600
>>>
>>>
>>> == Build changes ==
>>>
>>>      * Linux: CI_DRM_5017 -> Patchwork_10527
>>>
>>>    CI_DRM_5017: 9510f8e44127260f92b5b6c3127aafa22b15f741 @ git://anongit.freedesktop.org/gfx-ci/linux
>>>    IGT_4685: 78619fde4008424c472906041edb1d204e014f7c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>>>    Patchwork_10527: 757bbb8cb440de47c5c48ba5ca87c76681075424 @ git://anongit.freedesktop.org/gfx-ci/linux
>>>
>>>
>>> == Linux commits ==
>>>
>>> 757bbb8cb440 drm/i915/debugfs: hdcp capability of a sink
>>> e82aaa2cb827 drm/i915: hdcp_check_link only on CP_IRQ
>>> 1698e218c4ae drm/i915: Pullout the bksv read and validation
>>>
>>> == Logs ==
>>>
>>> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10527/issues.html
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx/attachments/20181023/decc1104/attachment.html>