Bug 106107 - [CI] igt@kms_* - dmesg-warn|fail - *ERROR* Atomic update failure on pipe [ABC]
Summary: [CI] igt@kms_* - dmesg-warn|fail - *ERROR* Atomic update failure on pipe [ABC]
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
: 105951 (view as bug list)
Depends on:
Blocks: 105981
  Show dependency treegraph
 
Reported: 2018-04-17 17:09 UTC by Martin Peres
Modified: 2019-07-10 13:05 UTC (History)
3 users (show)

See Also:
i915 platform: BXT, CFL, CNL, GLK, ICL, KBL, SKL
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 2018-04-17 17:09:23 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_20/fi-cnl-y3/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-blt.html

[  551.033924] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=3467 end=3468) time 7 us, min 2133, max 2159, scanline start 2167, end 2159
Comment 1 Martin Peres 2018-04-20 12:25:18 UTC
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
Comment 2 Jani Saarinen 2018-04-22 15:42:04 UTC
There is community reported issue from the same: *ERROR* Atomic update failure on pipe A error. Is this same issue? See: 91883
Comment 4 Martin Peres 2018-05-28 14:15:10 UTC
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
Comment 5 Martin Peres 2018-06-19 12:31:06 UTC
*** Bug 105951 has been marked as a duplicate of this bug. ***
Comment 6 Martin Peres 2018-07-12 11:23:59 UTC
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
Comment 7 Martin Peres 2018-09-04 07:26:09 UTC
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
Comment 8 Martin Peres 2018-10-29 14:50:17 UTC
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
Comment 9 Maarten Lankhorst 2018-11-05 11:04:46 UTC
Don't pull in unrelated tests please, gpu reset vs atomic update failure looks like it should be its own bug.
Comment 10 Martin Peres 2018-11-05 11:24:47 UTC
(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!
Comment 11 Martin Peres 2018-11-13 15:11:14 UTC
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
Comment 12 Lakshmi 2018-11-23 14:12:06 UTC
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
Comment 13 Martin Peres 2019-04-11 07:18:18 UTC
@Maarten: please suggest a way to split this bug to make it more actionable :)
Comment 14 CI Bug Log 2019-05-07 08:05:16 UTC
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
Comment 15 CI Bug Log 2019-07-10 13:05:42 UTC
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


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.