https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_23/fi-cfl-s3/igt@kms_draw_crc@draw-method-xrgb8888-blt-xtiled.html

[  264.708326] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=3688 end=3689) time 5 us, min 1417, max 1439, scanline start 1447, end 1439

There is community reported issue from the same: *ERROR* Atomic update failure on pipe A error. Is this same issue? See: 91883

Seen on KBL-r: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_27/fi-kbl-r/igt@kms_frontbuffer_tracking@fbcpsr-badstride.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_39/fi-skl-6600u/igt@syncobj_wait@wait-delayed-signal.html

[  172.978476] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=1781 end=1782) time 49 us, min 1777, max 1799, scanline start 1803, end 1799

*** Bug 105951 has been marked as a duplicate of this bug. ***

Also seen on GLK: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4400/shard-glk2/igt@kms_vblank@pipe-a-wait-forked-busy-hang.html

[   62.752672] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[   70.752534] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[   70.754741] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=5336 end=5337) time 532 us, min 1063, max 1079, scanline start 1049, end 1085

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4757/shard-apl3/igt@kms_vblank@pipe-b-ts-continuation-idle-hang.html

[  346.592996] i915 0000:00:02.0: Resetting rcs0 for no progress on rcs0
[  346.595649] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=830 end=831) time 606 us, min 1063, max 1079, scanline start 1052, end 1093

Also seen on ICL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2006/fi-icl-u2/igt@kms_pipe_crc_basic@read-crc-pipe-a.html

<3> [417.026012] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=27 end=28) time 355 us, min 2126, max 2159, scanline start 2114, end 2162

Don't pull in unrelated tests please, gpu reset vs atomic update failure looks like it should be its own bug.

(In reply to Maarten Lankhorst from comment #9)
> Don't pull in unrelated tests please, gpu reset vs atomic update failure
> looks like it should be its own bug

That's what you get when bug filing is done by an i915 noob ;)

Anyway, please suggest the way you would like bug filing done in this case (which bug should be filed for which failures).

Thanks!

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_139/fi-byt-j1900/igt@kms_flip@2x-flip-vs-panning-interruptible.html

<3> [172.869392] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=1163 end=1164) time 408 us, min 755, max 767, scanline start 749, end 749

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_148/fi-cfl-8109u/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html


Dmesg-Warnings	
<3> [35.936838] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=3167 end=3169) time 18371 us, min 1063, max 1079, scanline start 997, end 1112


https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_148/fi-cfl-8109u/igt@kms_cursor_legacy@short-flip-before-cursor-toggle.html

Dmesg-Warnings	
<3> [218.283913] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=1130 end=1133) time 56231 us, min 1063, max 1079, scanline start 629, end 56
<3> [218.559477] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=1151 end=1152) time 5210 us, min 1063, max 1079, scanline start 950, end 177

@Maarten: please suggest a way to split this bug to make it more actionable :)

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* fi-glk-dsi: igt@gem_pwrite@small-gtt-fbr - timeout - *ERROR* Atomic update failure on pipe [ABC]
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_273/fi-glk-dsi/igt@gem_pwrite@small-gtt-fbr.html

A CI Bug Log filter associated to this bug has been updated:

{- BYT BSW SKL APL KBL GLK CFL CNL ICL: all tests - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] -}
{+ BYT BSW SKL APL KBL GLK CFL CNL ICL: all tests - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6448/fi-bxt-dsi/igt@i915_pm_rpm@module-reload.html

A CI Bug Log filter associated to this bug has been updated:

{- BYT BSW SKL APL KBL GLK CFL CNL ICL: all tests - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] -}
{+ All machines: igt@kms_* - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7252/re-tgl-y/igt@kms_frontbuffer_tracking@fbcpsr-1p-shrfb-fliptrack.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7252/re-tgl-y/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7252/re-tgl-y/igt@kms_plane_cursor@pipe-b-overlay-size-128.html

A CI Bug Log filter associated to this bug has been updated:

{- All machines: igt@kms_* - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] -}
{+ All machines: igt@kms_* - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5262/shard-skl3/igt@debugfs_test@read_all_entries_display_on.html

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL:  igt@gem_exec_reloc@basic-wc-read-active - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC]
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7275/shard-skl9/igt@gem_exec_reloc@basic-wc-read-active.html

A CI Bug Log filter associated to this bug has been updated:

{- SKL:  igt@gem_exec_reloc@basic-wc-read-active - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] -}
{+ SKL:  igt@gem_exec_reloc@basic-wc-read-active - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7282/shard-skl10/igt@gem_wait@busy-vcs0.html

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* All Machines: Random tests - dmesg-warn- *ERROR* Atomic update failure on pipe [ABC]
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7298/fi-icl-u3/igt@i915_pm_rpm@module-reload.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7291/shard-skl7/igt@gem_wait@write-wait-bcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5297/fi-icl-u4/igt@i915_pm_rpm@module-reload.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7294/shard-skl7/igt@gem_exec_reloc@basic-range-active.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7295/shard-skl3/igt@gem_exec_reloc@basic-gtt-wc-active.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7298/shard-skl1/igt@gem_exec_reloc@basic-cpu-wc-active.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_401/fi-icl-dsi/igt@i915_hangman@error-state-capture-bcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_401/fi-icl-dsi/igt@prime_vgem@busy-render.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_401/fi-icl-u2/igt@gem_ctx_isolation@bcs0-s3.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7307/shard-skl5/igt@gem_exec_reloc@basic-write-gtt-active.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7308/shard-skl4/igt@gem_wait@wait-vcs0.html

The CI Bug Log issue associated to this bug has been updated.

### Removed filters

* All machines: igt@kms_* - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] (added on 1 week ago)
* SKL:  igt@gem_exec_reloc@basic-wc-read-active - dmesg-warn - *ERROR* Atomic update failure on pipe [ABC] (added on 2 days, 18 hours ago)
* fi-glk-dsi: igt@gem_pwrite@small-gtt-fbr - timeout - *ERROR* Atomic update failure on pipe [ABC] (added on 6 months, 1 week ago)
* All Machines: Random tests - dmesg-warn- *ERROR* Atomic update failure on pipe [ABC] (added on 1 day, 22 hours ago)

### New filters associated

* All machines - All tests - dmesg-warn - \*ERROR\* Atomic update failure on pipe [ABC]
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14803/fi-tgl-u/igt@i915_module_load@reload-with-fault-injection.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5164/fi-tgl-u/igt@i915_module_load@reload.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3658/fi-icl-dsi/igt@prime_vgem@basic-fence-read.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15160/fi-icl-dsi/igt@prime_self_import@basic-with_one_bo.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15207/fi-icl-dsi/igt@gem_sync@basic-each.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15209/fi-icl-dsi/igt@gem_ctx_exec@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15209/fi-icl-dsi/igt@gem_ctx_switch@rcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15223/fi-icl-dsi/igt@gem_mmap@basic-small-bo.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15227/fi-icl-dsi/igt@gem_render_tiled_blits@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15229/fi-icl-dsi/igt@gem_ringfill@basic-default.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15238/fi-icl-dsi/igt@gem_ctx_switch@rcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15252/fi-icl-dsi/igt@gem_ctx_exec@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7338/fi-icl-dsi/igt@prime_self_import@basic-with_one_bo.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7338/fi-icl-u2/igt@gem_exec_suspend@basic-s0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3700/fi-icl-u2/igt@gem_exec_suspend@basic-s0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7341/fi-icl-dsi/igt@gem_basic@create-close.html

-- 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/109.