CI_DRM_3254 GLK-shards igt@kms_psr_sink_crc@psr_drrs fail: (kms_psr_sink_crc:8736) CRITICAL: Test assertion failure function main, file kms_psr_sink_crc.c:539: (kms_psr_sink_crc:8736) CRITICAL: Failed assertion: drrs_disabled(&data) (kms_psr_sink_crc:8736) CRITICAL: Last errno: 2, No such file or directory Subtest psr_drrs failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3254/shard-glkb5/igt@kms_psr_sink_crc@psr_drrs.html
Also, new subtest and new assert (kms_psr_sink_crc:1513) CRITICAL: Test assertion failure function main, file kms_psr_sink_crc.c:547: (kms_psr_sink_crc:1513) CRITICAL: Failed assertion: wait_psr_entry(&data) (kms_psr_sink_crc:1513) CRITICAL: Last errno: 2, No such file or directory Subtest primary_page_flip failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3257/shard-glkb5/igt@kms_psr_sink_crc@primary_page_flip.html
NOTE on CI_DRM_3265: <tsa> glkb5? <tsa> yeah, I changed the non-psr panel to 3200x psr panel, and now it's red <tsa> need to find fullhd or 2560x psr panel .. <tsa> although, fixing the 3200x issue would be fine too So all these new fails are from that machine with this display: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3265/shard-glkb5/igt@kms_psr_sink_crc@cursor_mmap_cpu.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3265/shard-glkb5/igt@kms_psr_sink_crc@suspend_psr_exit.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3265/shard-glkb5/igt@kms_psr_sink_crc@sprite_mmap_cpu.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3265/shard-glkb5/igt@kms_psr_sink_crc@cursor_render.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3265/shard-glkb5/igt@kms_psr_sink_crc@primary_blt.html
Note now we have the same displays on all GLKs new subtests was hit: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3267/shard-glkb1/igt@kms_psr_sink_crc@cursor_blt.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3267/shard-glkb1/igt@kms_psr_sink_crc@cursor_blt.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3267/shard-glkb1/igt@kms_psr_sink_crc@primary_mmap_gtt.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb1/igt@kms_psr_sink_crc@sprite_blt.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb4/igt@kms_psr_sink_crc@sprite_render.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb5/igt@kms_psr_sink_crc@suspend_psr_active.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb1/igt@kms_psr_sink_crc@sprite_plane_onoff.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb4/igt@kms_psr_sink_crc@sprite_mmap_gtt.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb4/igt@kms_psr_sink_crc@primary_render.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb3/igt@kms_psr_sink_crc@primary_mmap_gtt_waiting.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb4/igt@kms_psr_sink_crc@cursor_mmap_gtt.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb5/igt@kms_psr_sink_crc@cursor_plane_onoff.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb2/igt@kms_psr_sink_crc@sprite_plane_move.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb1/igt@kms_psr_sink_crc@primary_mmap_cpu.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb1/igt@kms_psr_sink_crc@dpms_off_psr_active.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb5/igt@kms_psr_sink_crc@cursor_plane_move.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb1/igt@kms_psr_sink_crc@dpms_off_psr_exit.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3268/shard-glkb4/igt@kms_psr_sink_crc@cursor_mmap_gtt_waiting.html
Quick update: According to CI results this still keeps failing with the wait_psr_entry(&data) assertion.
(In reply to Elizabeth from comment #4) > Quick update: According to CI results this still keeps failing with the > wait_psr_entry(&data) assertion. Please, stop spamming the bugs with information we already know.
prio low due to GLKb-shards having display that doesn't really support PSR
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.