<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - piglit.spec.arb_shader_image_load_store.invalid causes intermittent GPU HANG" href="https://bugs.freedesktop.org/show_bug.cgi?id=91718#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - piglit.spec.arb_shader_image_load_store.invalid causes intermittent GPU HANG" href="https://bugs.freedesktop.org/show_bug.cgi?id=91718">bug 91718</a> from <a class="email" href="mailto:mark.a.janes@intel.com" title="Mark Janes <mark.a.janes@intel.com>"> Mark Janes</a> <pre>OK, thanks for clarifying. I only saw the piglit.spec.arb_shader_image_load_store.invalid test hang on IVB. I don't have a way to audit historical results to understand which tests cause gpu hangs. To find out which test is hanging, I have to take a machine out of the test pool, boot it with i915.reset=0, and repeatedly run piglit until I get a hang. Then I can look in the test directory to see which tests were running at the time. If reset is enabled, then there is no information that I can use to figure out which tests were running when the hang occurred. For example, arb_shader_image_load_store.invalid triggers the hang while reporting success. IVB had the most common hangs, so I investigated that platform first. BSW is encountering hangs even with host-mem-barrier disabled, but I have to do some investigation before I can tell you what test is the culprit. I have no information indicating it is from image_load_store. I'll try to catch a hang on BSW tonight.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>