<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - chromium takes out X on gen6" href="https://bugs.freedesktop.org/show_bug.cgi?id=74256#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - chromium takes out X on gen6" href="https://bugs.freedesktop.org/show_bug.cgi?id=74256">bug 74256</a> from <a class="email" href="mailto:joe.kappus@gmail.com" title="Joe Kappus <joe.kappus@gmail.com>"> Joe Kappus</a> <pre>Jan 31 00:08:47 superbia kernel: Watchdog[18586]: segfault at 0 ip 00007fcdd2d19868 sp 00007fcdbf522810 error 6 in chrome[7fcdcf65b000+50e9000] Jan 31 00:08:55 superbia kernel: [drm] stuck on render ring Jan 31 00:08:55 superbia kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error Jan 31 00:08:55 superbia kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jan 31 00:08:55 superbia kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jan 31 00:08:55 superbia kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jan 31 00:08:55 superbia kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Jan 31 00:08:55 superbia kernel: [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xcd02000 ctx 2) at 0xcd03a84 Jan 31 00:09:09 superbia acpid: client 2435[0:100] has disconnected Jan 31 00:09:10 superbia acpid: client connected from 20490[0:100] Jan 31 00:09:10 superbia acpid: 1 client rule loaded This is from syslog on the same event. I think X had a clean shutdown this time, the other times it didn't always take down X, I could flip to console and back to X to get my screen back up (just appeared black with cursor until I did this).</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> </ul> </body> </html>