<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - stuck on render ring (v4.7-rc7 Sky Lake Integrated Graphics [8086:1916])" href="https://bugs.freedesktop.org/show_bug.cgi?id=96894#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - stuck on render ring (v4.7-rc7 Sky Lake Integrated Graphics [8086:1916])" href="https://bugs.freedesktop.org/show_bug.cgi?id=96894">bug 96894</a> from <a class="email" href="mailto:bjorn@mork.no" title="Bjørn Mork <bjorn@mork.no>"> Bjørn Mork</a> <pre>Created <a href="attachment.cgi?id=129051" name="attach_129051" title="dmesg, Xorg.log and /sys/class/drm/card0/error from drm-tip GPU hang and repeated resets">attachment 129051</a> <a href="attachment.cgi?id=129051&action=edit" title="dmesg, Xorg.log and /sys/class/drm/card0/error from drm-tip GPU hang and repeated resets">[details]</a> dmesg, Xorg.log and /sys/class/drm/card0/error from drm-tip GPU hang and repeated resets I was lucky. Just got a hang again running the current drm-tip. The resets were repeated multiple times, before the X session died and I was sent back to the xdm window. The whole process was considerably quicker this time. But having all X clients die is still a no-go... Attaching a tar.tz with 3 files: dmesg output, /sys/class/drm/card0/error and /var/log/Xorg.0.log. The kernel/driver/drm was built from commit 6b590a717c7f ("drm-tip: 2017y-01m-19d-15h-51m-19s UTC integration manifest")</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>