<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BSW]igt/drv_missed_irq_hang sporadically causes *ERROR* pipe B underrun" href="https://bugs.freedesktop.org/show_bug.cgi?id=86189#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BSW]igt/drv_missed_irq_hang sporadically causes *ERROR* pipe B underrun" href="https://bugs.freedesktop.org/show_bug.cgi?id=86189">bug 86189</a> from <a class="email" href="mailto:huax.lu@intel.com" title="lu hua <huax.lu@intel.com>"> lu hua</a> <pre>drv_hangman also sporadically causes this error. @test: Intel_gpu_tools/igt_drv_hangman_error-state-capture-blt returncode: 0 info: @@@Returncode: 0 test case start at: Sun Jan 18 07:40:10 2015 test case end at: Sun Jan 18 07:40:39 2015 Errors: Dmesg: <3>[ 89.783289] [drm:valleyview_pipestat_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun <6>[ 91.783839] [drm] stuck on blitter ring <6>[ 91.815444] [drm] GPU HANG: ecode 8:2:0xfffffffe, in drv_hangman [5231], reason: Ring hung, action: reset <6>[ 91.815458] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. <6>[ 91.815462] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel <6>[ 91.815464] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. <6>[ 91.815467] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. <6>[ 91.815470] [drm] GPU crash dump saved to /sys/class/drm/card0/error <6>[ 91.817453] [drm] Simulated gpu hang, resetting stop_rings <5>[ 91.817457] drm/i915: Resetting chip after gpu hang</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>