<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - tests/gem_close_race, threads SEGFAULT on BDW, GPU hang SKL, machine hang on SNB" href="https://bugs.freedesktop.org/show_bug.cgi?id=95048#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - tests/gem_close_race, threads SEGFAULT on BDW, GPU hang SKL, machine hang on SNB" href="https://bugs.freedesktop.org/show_bug.cgi?id=95048">bug 95048</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>commit 757b9be460e06c8466f6c49ab7f0d7ff234b5b54 Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Fri Apr 22 16:02:12 2016 +0100 igt/gem_close_race: Avoid using threads, use signals instead Emulate the behaviour of the second thread killing fd at random by having a signal fire at a random time instead. Only one thread and so we do not have the issue of accessing another valid handle on another fd and so executing a blank buffer - triggering GPU hangs. References: <a class="bz_bug_link bz_status_NEW " title="NEW - tests/gem_close_race, threads SEGFAULT on BDW, GPU hang SKL, machine hang on SNB" href="show_bug.cgi?id=95048">https://bugs.freedesktop.org/show_bug.cgi?id=95048</a> Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Please test and confirm that we are not killing machines...</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> </ul> </body> </html>