Hi Alex ,
Inline Reply.
Thanks,
Anshuman Gupta.
_____________________________________________
From: Teres Alexis, Alan Previn <alan.previn.teres.alexis@intel.com>
Sent: Tuesday, October 5, 2021 10:52 PM
To: igt-dev@lists.freedesktop.org
Cc: B S, Karthik <karthik.b.s@intel.com>; Gupta, Anshuman <anshuman.gupta@intel.com>; Vivi, Rodrigo <rodrigo.vivi@intel.com>
Subject: RE: [igt-dev] ✗ Fi.CI.BAT: failure for Introduce PXP Test (rev13)
Folks, I believe this CI failure is nothing to do with this IGT PXP test because:
- the errors being reported are kernel errors related to eDP resources during bind/unbind operations but the IGT PXP codes do not modify any of the display IGT libraries and thus would not impact the behavior of other IGT display tests.
- additionally, I did a quick review of the kernel side PXP display changes one more time looking for possible missed that can explain below. In below context I searched for new display code exit-paths caused by getting -ENODEV or -EINVAL when checking for
pxp attributes in FBs (since the default CI kernel is built with CONFIG_PXP == off, all PXP helpers called by display return those errors). I couldn’t find any here.
[Gupta, Anshuman] display code return -EINVAL only in case of async flip in atomic_check if old decrypt state is differs from the new one. You may see -EINVAL error only in case async flip.
IGT changes
Possible regressions
- igt@core_hotunplug@unbind-rebind:
Patch Details
CI Bug Log - changes from IGT_6231 -> IGTPW_6287
Summary
FAILURE
Serious unknown changes coming with IGTPW_6287 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_6287, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Possible new issues
Here are the unknown changes that may have been introduced in IGTPW_6287:
IGT changes
Possible regressions
- igt@core_hotunplug@unbind-rebind:
Known issues
Here are the changes found in IGTPW_6287 that come from known issues:
IGT changes
Issues hit
- igt@amdgpu/amd_prime@amd-to-i915:
- igt@amdgpu/amd_prime@i915-to-amd:
- igt@gem_huc_copy@huc-copy:
- igt@kms_chamelium@dp-hpd-fast:
- igt@kms_chamelium@hdmi-crc-fast:
- igt@kms_chamelium@hdmi-hpd-fast:
- igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- igt@kms_flip@basic-plain-flip@c-dp1:
- igt@kms_force_connector_basic@force-load-detect:
- igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b:
- igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- igt@prime_vgem@basic-userptr:
Possible fixes
- igt@kms_frontbuffer_tracking@basic:
Participating hosts (33 -> 34)
Additional (3): fi-kbl-x1275 fi-snb-2520m fi-tgl-u2
Missing (2): fi-kbl-soraka fi-bsw-cyan
Build changes
- CI: CI-20190529 -> None
- IGT: IGT_6231 -> IGTPW_6287
== Testlist changes ==
+igt@gem_pxp@create-protected-buffer
+igt@gem_pxp@create-regular-buffer
+igt@gem_pxp@create-regular-context-1
+igt@gem_pxp@create-regular-context-2
+igt@gem_pxp@create-valid-protected-context
+igt@gem_pxp@display-protected-crc
+igt@gem_pxp@dmabuf-shared-protected-dst-is-context-refcounted
+igt@gem_pxp@fail-invalid-protected-context
+igt@gem_pxp@hw-rejects-pxp-buffer
+igt@gem_pxp@hw-rejects-pxp-context
+igt@gem_pxp@protected-encrypted-src-copy-not-readible
+igt@gem_pxp@protected-raw-src-copy-not-readible
+igt@gem_pxp@regular-baseline-src-copy-readible
+igt@gem_pxp@reject-modify-context-protection-off-1
+igt@gem_pxp@reject-modify-context-protection-off-2
+igt@gem_pxp@reject-modify-context-protection-off-3
+igt@gem_pxp@reject-modify-context-protection-on
+igt@gem_pxp@verify-pxp-execution-after-suspend-resume
+igt@gem_pxp@verify-pxp-key-change-after-suspend-resume
+igt@gem_pxp@verify-pxp-stale-buf-execution
+igt@gem_pxp@verify-pxp-stale-buf-optout-execution
+igt@gem_pxp@verify-pxp-stale-ctx-execution