Bug 112149

Summary: [CI][DRMTIP] igt@kms_atomic_transition@3x-modeset-transitions-nonblocking - fail - Failed assertion: ret == 0
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: not set    
Priority: not set CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: ICL i915 features: display/Other

Description Lakshmi 2019-10-28 12:03:29 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_394/fi-icl-u4/igt@kms_atomic_transition@3x-modeset-transitions-nonblocking.html
Starting subtest: 3x-modeset-transitions-nonblocking
(kms_atomic_transition:3034) igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3543:
(kms_atomic_transition:3034) igt_kms-CRITICAL: Failed assertion: ret == 0
(kms_atomic_transition:3034) igt_kms-CRITICAL: Last errno: 22, Invalid argument
(kms_atomic_transition:3034) igt_kms-CRITICAL: error: -22 != 0
Subtest 3x-modeset-transitions-nonblocking failed.
Comment 1 CI Bug Log 2019-10-28 12:04:14 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@kms_atomic_transition@3x-modeset-transitions-nonblocking - fail - Failed assertion: ret == 0
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_394/fi-icl-u4/igt@kms_atomic_transition@3x-modeset-transitions-nonblocking.html
Comment 2 Matt Roper 2019-10-29 21:55:55 UTC
<7>[  881.522082] [drm:intel_dp_start_link_train [i915]] [CONNECTOR:255:DP-4] Link Training failed at link rate = 270000, lane count = 2
...
<7>[  883.541809] [drm:intel_dp_compute_config [i915]] DP link computation with max lane count 2 max rate 162000 max bpp 24 pixel clock 148500KHz
<7>[  883.541851] [drm:intel_dp_compute_config [i915]] Force DSC en = 0
<7>[  883.541894] [drm:intel_atomic_check [i915]] Encoder config failure: -22

Another case of link training failure mid-test preventing us from achieving the desired mode.

*** This bug has been marked as a duplicate of bug 111185 ***
Comment 3 CI Bug Log 2019-11-14 12:11:56 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ICL: igt@kms_atomic_transition@3x-modeset-transitions-nonblocking - fail - Failed assertion: ret == 0 -}
{+ KBL ICL: igt@kms_atomic_transition@3x-modeset-transitions-nonblocking - fail - Failed assertion: ret == 0 +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_403/fi-kbl-7560u/igt@kms_atomic_transition@3x-modeset-transitions-fencing.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_403/fi-kbl-7560u/igt@kms_atomic_transition@3x-modeset-transitions-nonblocking.html
Comment 4 CI Bug Log 2019-11-14 12:42:21 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* KBL: igt@runner@aborted - fail - Previous test: kms_atomic_transition (3x-modeset-transitions-fencing)
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_403/fi-kbl-7560u/igt@runner@aborted.html
Comment 5 CI Bug Log 2019-11-14 13:23:46 UTC
A CI Bug Log filter associated to this bug has been updated:

{- KBL: igt@runner@aborted - fail - Previous test: kms_atomic_transition (3x-modeset-transitions-fencing) -}
{+ KBL: igt@runner@aborted - fail - Previous test: kms_atomic_transition (3x-modeset-transitions-fencing) +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_403/fi-kbl-7560u/igt@runner@aborted.html
Comment 6 CI Bug Log 2019-11-20 17:42:09 UTC
A CI Bug Log filter associated to this bug has been updated:

{- KBL: igt@runner@aborted - fail - Previous test: kms_atomic_transition (3x-modeset-transitions-fencing) -}
{+ KBL: igt@runner@aborted - fail - Previous test: kms_atomic_transition (3x-modeset-transitions-fencing) +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_405/fi-kbl-7560u/igt@runner@aborted.html

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.