<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - deadlock occurs during GPU reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=109692#c37">Comment # 37</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - deadlock occurs during GPU reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=109692">bug 109692</a> from <a class="email" href="mailto:andrey.grodzovsky@amd.com" title="Andrey Grodzovsky <andrey.grodzovsky@amd.com>"> Andrey Grodzovsky</a> <pre>(In reply to mikhail.v.gavrilov from <a href="show_bug.cgi?id=109692#c36">comment #36</a>) > Created <a href="attachment.cgi?id=143928" name="attach_143928" title="Demonstration how message "drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!" get a real pain">attachment 143928</a> <a href="attachment.cgi?id=143928&action=edit" title="Demonstration how message "drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!" get a real pain">[details]</a> > Demonstration how message "drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to > initialize parser -125!" get a real pain Those messages are actually expected for this particular use case, i might consider switching them to info. I am working on completing review and pushing those patches into our upstream branch. Thanks for testing.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>