Bug 111742 - [CI][DRMTIP] igt@kms_force_connector_basic@force-edid - fail - Failed assertion: temp->count_modes == start_n_modes
Summary: [CI][DRMTIP] igt@kms_force_connector_basic@force-edid - fail - Failed asserti...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: low minor
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-19 08:54 UTC by Lakshmi
Modified: 2019-10-24 18:43 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: display/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-09-19 08:54:54 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_372/fi-skl-6700k2/igt@kms_force_connector_basic@force-edid.html

Starting subtest: force-edid
(kms_force_connector_basic:1488) CRITICAL: Test assertion failure function __real_main78, file ../tests/kms_force_connector_basic.c:293:
(kms_force_connector_basic:1488) CRITICAL: Failed assertion: temp->count_modes == start_n_modes
(kms_force_connector_basic:1488) CRITICAL: error: 11 != 7
Subtest force-edid failed.
**** DEBUG ****
(kms_force_connector_basic:1488) igt_kms-DEBUG: Connector card0-HDMI-A-1/status is now forced on
(kms_force_connector_basic:1488) igt_kms-DEBUG: Current forced connectors:
(kms_force_connector_basic:1488) igt_kms-DEBUG: 	card0-HDMI-A-1/status
(kms_force_connector_basic:1488) igt_kms-DEBUG: 	card0-HDMI-A-2/status
(kms_force_connector_basic:1488) igt_kms-DEBUG: 	card0-HDMI-A-3/status
(kms_force_connector_basic:1488) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(kms_force_connector_basic:1488) igt_kms-DEBUG: Test requirement passed: debugfs_fd != -1
(kms_force_connector_basic:1488) DEBUG: num_conn 5
(kms_force_connector_basic:1488) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(kms_force_connector_basic:1488) igt_kms-DEBUG: Test requirement passed: debugfs_fd != -1
(kms_force_connector_basic:1488) igt_kms-DEBUG: Connector card0-HDMI-A-1/status is now forced detect
(kms_force_connector_basic:1488) igt_kms-DEBUG: Current forced connectors:
(kms_force_connector_basic:1488) igt_kms-DEBUG: 	card0-HDMI-A-1/status
(kms_force_connector_basic:1488) igt_kms-DEBUG: 	card0-HDMI-A-2/status
(kms_force_connector_basic:1488) igt_kms-DEBUG: 	card0-HDMI-A-3/status
(kms_force_connector_basic:1488) CRITICAL: Test assertion failure function __real_main78, file ../tests/kms_force_connector_basic.c:293:
(kms_force_connector_basic:1488) CRITICAL: Failed assertion: temp->count_modes == start_n_modes
(kms_force_connector_basic:1488) CRITICAL: error: 11 != 7
(kms_force_connector_basic:1488) igt_core-INFO: Stack trace:
(kms_force_connector_basic:1488) igt_core-INFO:   #0 ../lib/igt_core.c:1674 __igt_fail_assert()
(kms_force_connector_basic:1488) igt_core-INFO:   #1 ../tests/kms_force_connector_basic.c:279 __real_main78()
(kms_force_connector_basic:1488) igt_core-INFO:   #2 [<unknown>+0x0]
****  END  ****
Subtest force-edid: FAIL (0.151s)
Comment 1 CI Bug Log 2019-09-19 08:58:24 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@kms_force_connector_basic@force-edid - fail - Failed assertion: temp-&gt;count_modes == start_n_modes
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_372/fi-skl-6700k2/igt@kms_force_connector_basic@force-edid.html
Comment 2 Vanshidhar Konda 2019-10-24 18:43:13 UTC
This issue has occurred only once so far on a SKL machine.

The issue noted here that at the start of the test it noted that HDMI-A-1 had 7 modes (should have been 11) but during the test after forcing the connection and getting EDID it notes that there are 11 modes (the correct number).

Lowering priority and severity of the bug as it has only occurred once and there have been 12/12 successful runs since then.


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.