<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Mouse Cursor halts CPU for multiple display configurations i915 i5-5287U" href="https://bugs.freedesktop.org/show_bug.cgi?id=95064#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Mouse Cursor halts CPU for multiple display configurations i915 i5-5287U" href="https://bugs.freedesktop.org/show_bug.cgi?id=95064">bug 95064</a> from <a class="email" href="mailto:ismail@inbox247.com" title="Harry <ismail@inbox247.com>"> Harry</a> <pre>This bugs hangs the CPU (as in not only the GPU) The system has to be powered off with a 4-second power button press It is clearly a kernel problem, does that mean it has to be drm? I was reading over here: <a href="https://01.org/linuxgraphics/documentation/how-report-bugs">https://01.org/linuxgraphics/documentation/how-report-bugs</a> - So I should use drm-intel-nightly I can capture dmesg until halt on another networked machine I am not sure if cat /sys/class/drm/card0/error will be possible since the cpu halts? (kernel options: drm.debug=0x1e log_buf_len=1M) However, this is a MacBook Pro 2015 13", "everybody" has one. And it's the latest 16.04 "everybody" has that, too cpu/gpu: i5-5287U CPU @ 2.90GHz Two displays via two DisplayPort cables - it crashes with a single external display, too - it does not crash without external displays Running Weston from 16.04, it's 100% reproducible uname --kernel-release --machine 4.4.0-21-generic x86_64 I am running KDE/X now, b/c that does not crash.</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>