Created attachment 109327 [details] dmesg ==System Environment== -------------------------- Regression: not sure, fail rate:1/10 Non-working platforms: BSW ==kernel== -------------------------- drm-intel-nightly/9a7620f405895714b4e0dc3181a8328b4406287e ==Bug detailed description== It sporadically causes "<3>[ 673.232605] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* pipe B underrun" on BSW with -nightly kernel. fail rate: 1/10. output: Interrupts masked Interrupts unmasked Cleared missed interrupts ==Reproduce steps== ---------------------------- 1. ./drv_missed_irq_hang
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
Chris or Mika, is this normal for hangman?
Apart from the hang, potentially related to bug 85908.
(In reply to Jani Nikula from comment #3) > Apart from the hang, potentially related to bug 85908. Presumed fixed upstream, closing. Please reopen if the problem persists with latest kernels.
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.