Bug 112088 - [CI][RESUME] igt@kms_draw_crc@* - fail - Failed assertion: rc == 0
Summary: [CI][RESUME] igt@kms_draw_crc@* - fail - Failed assertion: rc == 0
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-22 07:04 UTC by Lakshmi
Modified: 2019-11-29 19:42 UTC (History)
1 user (show)

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


Attachments

Description Lakshmi 2019-10-22 07:04:23 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb2101010-blt-ytiled.html
Starting subtest: draw-method-xrgb2101010-blt-ytiled
(kms_draw_crc:1134) CRITICAL: Test assertion failure function get_method_crc, file ../tests/kms_draw_crc.c:149:
(kms_draw_crc:1134) CRITICAL: Failed assertion: rc == 0
(kms_draw_crc:1134) CRITICAL: Last errno: 22, Invalid argument
(kms_draw_crc:1134) CRITICAL: error: -22 != 0
Subtest draw-method-xrgb2101010-blt-ytiled failed.
Comment 1 CI Bug Log 2019-10-22 07:05:11 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@kms_draw_crc@* - fail - Failed assertion: rc == 0
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb2101010-blt-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb2101010-mmap-cpu-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb2101010-mmap-gtt-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb2101010-mmap-wc-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb2101010-pwrite-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb8888-blt-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb8888-mmap-cpu-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb8888-mmap-wc-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb8888-pwrite-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@draw-method-xrgb8888-render-ytiled.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_draw_crc@fill-fb.html
Comment 2 Maarten Lankhorst 2019-10-23 09:27:51 UTC
These failing tests should be fixed to use igt_display.

The failing call is drmModeSetCrtc().

However the above does not look to be the root cause here:

<7> [632.129879] [drm:skl_allocate_pipe_ddb [i915]] Requested display configuration exceeds system DDB limitations
<7> [632.129897] [drm:skl_allocate_pipe_ddb [i915]] minimum required 243/238

From boot:
<7> [ 15.420845] [drm:skl_compute_wm [i915]] [PLANE:87:cursor A] ddb (   0 -    0) -> ( 959 - 1024), size    0 ->   65

A bug in DDB allocation or other watermarks code?

Impact: Unable to set the primary plane to certain formats, or less optimal use of the watermark allocations, resulting in increased power consumption.
Comment 3 Martin Peres 2019-11-29 19:42:39 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/535.


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.