<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED NOTOURBUG - [skl] Hard lockup (Freeze) after reset failure: GPU HANG: ecode 9:0:0x85dffffb" href="https://bugs.freedesktop.org/show_bug.cgi?id=109949#c34">Comment # 34</a> on <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED NOTOURBUG - [skl] Hard lockup (Freeze) after reset failure: GPU HANG: ecode 9:0:0x85dffffb" href="https://bugs.freedesktop.org/show_bug.cgi?id=109949">bug 109949</a> from <a class="email" href="mailto:arcadiy@ivanov.biz" title="Arcadiy Ivanov <arcadiy@ivanov.biz>"> Arcadiy Ivanov</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=109949#c33">comment #33</a>) > Do what exactly? Userspace hangs the GPU, the kernel detects the hung GPU, > resets the hung GPU and if userspace keeps on doing so, kills the userspace. > We can't magically fix userspace. Chris, this is not what're discussing here. If it was the issue, nobody would make a peep! The issue isn't that userspace hangs GPU and GPU then kills userspace. The issue is that userspace hangs the GPU AND ***kills the kernel***: GPU is hung, but it's not the userspace that dies it's the kernel that gets completely seized up - no IO, no interrupts. Everything dies.</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>