Bug 111610 - [CI][RESUME] igt@kms_plane_scaling@*(pixel-format*|clamping) - fail - Failed assertion: ret == 0
Summary: [CI][RESUME] igt@kms_plane_scaling@*(pixel-format*|clamping) - fail - Failed ...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-09 11:10 UTC by Martin Peres
Modified: 2019-09-17 10:45 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-09-09 11:10:24 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane_scaling@pipe-b-scaler-with-pixel-format.html

Starting subtest: pipe-B-scaler-with-pixel-format
(kms_plane_scaling:1382) igt_kms-CRITICAL: Test assertion failure function do_display_commit, file ../lib/igt_kms.c:3464:
(kms_plane_scaling:1382) igt_kms-CRITICAL: Failed assertion: ret == 0
(kms_plane_scaling:1382) igt_kms-CRITICAL: Last errno: 22, Invalid argument
(kms_plane_scaling:1382) igt_kms-CRITICAL: error: -22 != 0
Comment 1 CI Bug Log 2019-09-09 11:10:40 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@kms_plane_scaling@*(pixel-format*|clamping) - fail - Failed assertion: ret == 0
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_362/fi-tgl-u/igt@kms_plane_scaling@pipe-c-scaler-with-pixel-format.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_362/fi-tgl-u/igt@kms_plane_scaling@pipe-a-scaler-with-pixel-format.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@kms_plane_scaling@pipe-b-scaler-with-pixel-format.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@kms_plane@pixel-format-pipe-c-planes-source-clamping.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@kms_plane@pixel-format-pipe-a-planes.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@kms_plane@pixel-format-pipe-b-planes.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@kms_plane_scaling@pipe-c-scaler-with-clipping-clamping.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-tgl-u/igt@kms_plane_scaling@pipe-a-scaler-with-clipping-clamping.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane_scaling@pipe-b-scaler-with-pixel-format.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane@pixel-format-pipe-a-planes-source-clamping.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane@pixel-format-pipe-c-planes.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane@pixel-format-pipe-b-planes-source-clamping.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane@pixel-format-pipe-c-planes-source-clamping.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane@pixel-format-pipe-a-planes.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane@pixel-format-pipe-b-planes.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane_scaling@pipe-c-scaler-with-clipping-clamping.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@kms_plane_scaling@pipe-a-scaler-with-clipping-clamping.html
Comment 2 Juha-Pekka Heikkilä 2019-09-10 13:21:27 UTC
There's in log comment which says "[drm:skl_check_pipe_max_pixel_rate [i915]] Max supported pixel clock with scaling exceeded", on log where I checked this failed is used on screen XR4H and RG16 formats on plane sizes which are too big for scaler..so this is problem of the test.
Comment 4 Juha-Pekka Heikkilä 2019-09-12 14:14:46 UTC
I went checking on ICL how this "*-scaler-with-clipping-clamping" test really behave and feel this test is less than useless.

On normal 1080p as well as 4k display all runs trying YUV formats will fail silently, none of them could ever come to screen. This silently failing is by design in this test, if you look at dmesg while "*-scaler-with-clipping-clamping" is running you see almost all runs will fail but still test says "SUCCESS".

Why "*-scaler-with-clipping-clamping" was now visibly failing in CI was there used special screen resolution "3200x1800" which allowed YUV formats to try to show on screen. So, in other words this clipping or clamping with scalers is likely never actually tested using YUV formats and should probably go check if scalers with YUV are tested at all.


..onto the actual bug which look like is a *real* bug that can be seen better in kms_plane@pixel-format-pipe-*-planes, DRM_FORMAT_XRGB16161616F is used just on regular plane of size 64x64 without anything special and it fails with comment "[drm:skl_check_pipe_max_pixel_rate [i915]] Max supported pixel clock with scaling exceeded" so that probably need some fix. This does work on ICL.
Comment 5 Jani Saarinen 2019-09-17 10:45:09 UTC
According to Ville/J-P should be fixed by https://patchwork.freedesktop.org/series/63373/


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.