https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_134/fi-icl-u2/igt@kms_rotation_crc@primary-y-tiled-reflect-x-270.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_135/fi-icl-u/igt@kms_rotation_crc@primary-y-tiled-reflect-x-90.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_135/fi-icl-u/igt@kms_rotation_crc@primary-x-tiled-reflect-x-0.html <3> [341.390549] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=1255 end=1256) time 303 us, min 1054, max 1079, scanline start 1053, end 1084 <3> [341.667743] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=1280 end=1281) time 710 us, min 1054, max 1079, scanline start 1035, end 1107 <3> [349.342470] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=358 end=359) time 503 us, min 1054, max 1079, scanline start 1033, end 1084 <3> [349.886176] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=407 end=408) time 614 us, min 1054, max 1079, scanline start 1031, end 1093 <3> [350.440815] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=457 end=458) time 492 us, min 1054, max 1079, scanline start 1038, end 1088 <3> [358.526621] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe C (start=442 end=443) time 396 us, min 1054, max 1079, scanline start 1039, end 1080
Last seen over a month ago, with a 0.0% 0/162 run reproduction - I propose this be closed. Martin and Lakshmi, any objections?
This issue occurred twice (back to back). Last seen, drmtip_135 (1 month, 2 weeks / 1156 runs ago). Closing the bug assuming this has been fixed.
icl-u not in CI anymore and https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_168/fi-icl-u2/igt@kms_rotation_crc@primary-y-tiled-reflect-x-270.html passes on ICL-U2 but https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_168/fi-icl-u2/igt@kms_rotation_crc@primary-x-tiled-reflect-x-0.html is this different bug?
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.