Bug 102371

Summary: [CI][SNB] CPU pipe A FIFO underrun in igt@kms_busy@extended-modeset-hang-newfb*
Product: DRI Reporter: Martin Peres <martin.peres>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Martin Peres 2017-08-23 11:40:18 UTC 
When running the igt@kms_busy@extended-modeset-hang-newfb* tests on Sandybrige, we consistently hit the following issue:

[   49.763465] i915 0000:00:02.0: Resetting chip after gpu hang
[   60.894990] asynchronous wait on fence i915:[global]:201 timed out
[   60.933406] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
[   60.933613] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder B
[   60.933648] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun

Full logs:
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_2993/shard-snb6/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-A.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_2993/shard-snb5/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-B.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_2993/shard-snb4/igt@kms_busy@extended-modeset-hang-newfb-render-A.html
 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_2993/shard-snb5/igt@kms_busy@extended-modeset-hang-newfb-render-B.html
Comment 1 Marta Löfstedt 2017-09-12 07:05:03 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3074/shard-hsw1/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html

[   28.724991] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Comment 2 Marta Löfstedt 2017-09-19 13:33:41 UTC 

*** This bug has been marked as a duplicate of bug 102373 ***

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.