| Summary: | [CI] igt@kms_flip@flip-vs-panning-vs-hang[-interruptible] or igt@kms_vblank@pipe-[abc]-ts-continuation-modeset-hang - dmesg-warn - *ERROR* Potential atomic update failure on pipe [A|B] | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | low | CC: | intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | IVB, SNB | i915 features: | display/atomic |
| Bug Depends on: | |||
| Bug Blocks: | 105981 | ||
|
Description
Marta Löfstedt
2017-11-20 06:42:08 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7225/shard-snb7/igt@kms_flip@flip-vs-panning-vs-hang-interruptible.html [ 651.065471] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe B https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3482/shard-snb6/igt@kms_flip@flip-vs-modeset-vs-hang.html [ 150.686422] i915 0000:00:02.0: Resetting chip after gpu hang [ 158.776079] i915 0000:00:02.0: Resetting chip after gpu hang [ 159.087922] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe B Besides this other issue: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3803/shard-snb4/igt@kms_flip@flip-vs-modeset-vs-hang.html [ 81.869168] [drm:intel_check_pch_fifo_underruns [i915]] *ERROR* pch fifo underrun on pch transcoder A It seems that the warn *ERROR* Potential atomic update failure on pipe [A|B] haven't appeared again on SNB. (In reply to Elizabeth from comment #4) > Besides this other issue: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3803/shard-snb4/ > igt@kms_flip@flip-vs-modeset-vs-hang.html > [ 81.869168] [drm:intel_check_pch_fifo_underruns [i915]] *ERROR* pch fifo > underrun on pch transcoder A > It seems that the warn > *ERROR* Potential atomic update failure on pipe [A|B] > haven't appeared again on SNB. The issue that the bug was filed for has happened within the 1 month cuf-off time for CI generated bugs. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-ivb-3770/igt@kms_flip@flip-vs-panning-vs-hang-interruptible.html [ 83.916736] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe B https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_14/fi-ivb-3520m/igt@kms_flip@2x-flip-vs-panning-vs-hang-interruptible.html [ 238.908384] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe B https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_17/fi-snb-2600/igt@kms_flip@flip-vs-panning-vs-hang-interruptible.html [ 179.100618] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe A https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_32/fi-ivb-3520m/igt@kms_vblank@pipe-b-ts-continuation-modeset-hang.html [ 47.730434] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe B https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_33/fi-ivb-3520m/igt@kms_vblank@pipe-a-ts-continuation-modeset-hang.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_39/fi-ivb-3520m/igt@kms_vblank@pipe-a-ts-continuation-modeset-hang.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_73/fi-ivb-3770/igt@kms_flip@flip-vs-panning-vs-hang.html [ 88.999202] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe B https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_73/fi-ivb-3770/igt@kms_flip@flip-vs-panning-vs-hang.html [ 88.801608] i915 0000:00:02.0: Resetting chip for hang on rcs0 [ 88.999202] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe B According to Maarten, this issue happens only when GPU resets at the same time as atomic update. Lowering the priority. Used to be seen multiple times per week, now nothing since CI_DRM_4456_full (3 months, 3 weeks / 2050 runs ago). Closing! |
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.