<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54226#c107">Comment # 107</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54226">bug 54226</a> from <a class="email" href="mailto:longerdev@gmail.com" title="LongerDev <longerdev@gmail.com>"> LongerDev</a> <pre>(In reply to <a href="show_bug.cgi?id=54226#c106">comment #106</a>) > (In reply to <a href="show_bug.cgi?id=54226#c104">comment #104</a>) > > I'm not sure my problem is related to this bug. > > Most likely it isn't - gpu hang is similar to an application crashing. > Please file a new bug report and don't forget to attach the error state > file. That's the first thing we need to triage the bug. > > And of course list the versions of all the userspace driver parts (mesa, > ddx, ...) since like a normal application crash most often it's not a kernel > bug, but a bug in the render commands submitted by userspace to the gpu. Why userspace drivers can breaking render and calling error in kernel part of driver? May be can add "filter" sent commands and ignore (or other reaction, but not execute their) their?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>