<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BYT]igt/drv_hangman sporadically causes *ERROR* Timed out: waiting for Render to ack" href="https://bugs.freedesktop.org/show_bug.cgi?id=85684#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BYT]igt/drv_hangman sporadically causes *ERROR* Timed out: waiting for Render to ack" href="https://bugs.freedesktop.org/show_bug.cgi?id=85684">bug 85684</a> from <a class="email" href="mailto:huax.lu@intel.com" title="lu hua <huax.lu@intel.com>"> lu hua</a> <pre>gem_reset_stats also has this issue. @test: Intel_gpu_tools/igt_gem_reset_stats_reset-count-blt returncode: 0 info: @@@Returncode: 0 test case start at: Thu Oct 30 12:32:10 2014 test case end at: Thu Oct 30 12:32:20 2014 Errors: Dmesg: <6>[ 108.951070] [drm] stuck on blitter ring <6>[ 108.958779] [drm] GPU HANG: ecode 2:0xe77ffff3, in gem_reset_stats [5973], reason: Ring hung, action: reset <6>[ 108.958787] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. <6>[ 108.958789] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel <6>[ 108.958792] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. <6>[ 108.958794] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. <6>[ 108.958797] [drm] GPU crash dump saved to /sys/class/drm/card0/error <3>[ 108.958906] [drm:__vlv_force_wake_get [i915]] *ERROR* Timed out: waiting for Render to ack. <6>[ 108.960558] [drm] Simulated gpu hang, resetting stop_rings <5>[ 108.960564] 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>