<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - GPU HANG: ecode 9:0:0x86dfbff9, in Map-GL [6016], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=111395#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - GPU HANG: ecode 9:0:0x86dfbff9, in Map-GL [6016], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=111395">bug 111395</a> from <a class="email" href="mailto:mark.a.janes@intel.com" title="Mark Janes <mark.a.janes@intel.com>"> Mark Janes</a> <pre>It is unrealistic to expect that the problem can be pinpointed solely by looking at the error state. The entire graphics stack is a big question mark for this product. If you want progress to be made on this bug, you need to follow up on the requests that have been made: - test with an upstream recent kernel - test with the latest mesa release - Provide reproduction steps If your customer thinks updating to a newer graphics stack is riskier than shipping the bugs that have been already fixed, you still need to *test* with the new stack to understand which bug fixes need backports to your system.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>