[Bug 102371] New: [CI][SNB] CPU pipe A FIFO underrun in igt at kms_busy@extended-modeset-hang-newfb*
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Aug 23 11:40:18 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=102371
Bug ID: 102371
Summary: [CI][SNB] CPU pipe A FIFO underrun in
igt at kms_busy@extended-modeset-hang-newfb*
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: martin.peres at free.fr
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
When running the igt at 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
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170823/74c8d5a7/attachment.html>
More information about the intel-gfx-bugs
mailing list