https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_320/fi-icl-u4/igt@kms_color@pipe-b-ctm-negative.html Starting subtest: pipe-B-ctm-negative (kms_color:1256) igt_kms-CRITICAL: Test assertion failure function igt_primary_plane_commit_legacy, file ../lib/igt_kms.c:2870: (kms_color:1256) igt_kms-CRITICAL: Failed assertion: ret == 0 (kms_color:1256) igt_kms-CRITICAL: Last errno: 22, Invalid argument (kms_color:1256) igt_kms-CRITICAL: error: -22 != 0 Subtest pipe-B-ctm-negative failed.
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@kms_color@pipe-b-ctm-negative - fail - Failed assertion: ret == 0, error: -22 != 0 - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_320/fi-icl-u4/igt@kms_color@pipe-b-ctm-negative.html
Synced the latest drm-tip and IGT and tried to test this IGT test. I can see there is no error while executing the kms_color@pipe-b-ctm-negative. Can someone confirm this from CI side. If this is indeed the case, we can close this issue.
A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@kms_color@pipe-b-ctm-negative - fail - Failed assertion: ret == 0, error: -22 != 0 -} {+ ICL: igt@kms_color@pipe-* - fail - Failed assertion: ret == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_326/fi-icl-u4/igt@kms_color@pipe-c-ctm-0-5.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_327/fi-icl-u4/igt@kms_color@pipe-a-ctm-green-to-red.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_328/fi-icl-u4/igt@kms_color@pipe-a-ctm-green-to-red.html
(In reply to Uma Shankar from comment #2) > Synced the latest drm-tip and IGT and tried to test this IGT test. I can see > there is no error while executing the kms_color@pipe-b-ctm-negative. > > Can someone confirm this from CI side. If this is indeed the case, we can > close this issue. (In reply to CI Bug Log from comment #3) > A CI Bug Log filter associated to this bug has been updated: > > {- ICL: igt@kms_color@pipe-b-ctm-negative - fail - Failed assertion: ret == > 0, error: -22 != 0 -} > {+ ICL: igt@kms_color@pipe-* - fail - Failed assertion: ret == 0, error: -22 > != 0 +} > > New failures caught by the filter: > > * > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_326/fi-icl-u4/ > igt@kms_color@pipe-c-ctm-0-5.html > * > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_327/fi-icl-u4/ > igt@kms_color@pipe-a-ctm-green-to-red.html > * > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_328/fi-icl-u4/ > igt@kms_color@pipe-a-ctm-green-to-red.html @Uma These are new failures. Can you please comment on the latest failures?
A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@kms_color@pipe-* - fail - Failed assertion: ret == 0, error: -22 != 0 -} {+ ICL: igt@kms_color@pipe-* - fail - Failed assertion: ret == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_341/fi-icl-u4/igt@kms_color@pipe-b-ctm-green-to-red.html
This appears to be a duplicate of bug 111067; the failures here aren't caused by anything related to color management, but rather by a general -EINVAL returned by the encoder's compute_config() handler. *** This bug has been marked as a duplicate of bug 111185 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.