<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [CFL] Latitude 7400 2-in-1: intermittent screen freezes (i915)" href="https://bugs.freedesktop.org/show_bug.cgi?id=111500#c28">Comment # 28</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [CFL] Latitude 7400 2-in-1: intermittent screen freezes (i915)" href="https://bugs.freedesktop.org/show_bug.cgi?id=111500">bug 111500</a> from <a class="email" href="mailto:leho@kraav.com" title="Leho Kraav (:macmaN :lkraav) <leho@kraav.com>"> Leho Kraav (:macmaN :lkraav)</a> <pre>(In reply to Lakshmi from <a href="show_bug.cgi?id=111500#c27">comment #27</a>) > (In reply to Leho Kraav (:macmaN :lkraav) from <a href="show_bug.cgi?id=111500#c26">comment #26</a>) > > I just got the same freeze on drm-tip (* d45d78ff950b - drm-tip: > > 2019y-09m-08d-15h-18m-05s UTC integration manifest (21 hours ago) <Chris > > Wilson>) by just moving the mouse around in a Firefox window. > > > Thanks for the feedback from drmtip. Can you please attach the dmseg log > from boot with debug parameters? Argh, that last short session I forgot to add drm.debug parameter. But my latest drm-tip boot log attachment from yesterday <a href="https://bugs.freedesktop.org/attachment.cgi?id=145300&action=edit">https://bugs.freedesktop.org/attachment.cgi?id=145300&action=edit</a> should be exactly the same, at least for the early phase? Alternatively, if my current 4.19.71 session should freeze, I will re-do a drm-tip session with drm.debug, and upon freeze, will be able to capture full `journalctl -b` output for the whole session (it will be several hundred MB uncompressed). > What is the impact of this issue as a user? How do you recover this > situation? It's a complete deal-breaker, there is no recovery other than forced reboot via power button (or Magic SysRq > REISUB). There seems to be no way to unfreeze the screen. I haven't experienced this type of an difficult to solve graphics stack issue on DELL laptop hardware for years. I generally like this Latitude 7400 2-in-1 physical hardware quality, it's the only reason I'm going through so much trouble trying to identify whether it's a Linux software issue. I ran all pre-BIOS hardware tests yesterday, also in Thorough mode, everything passed w/ green checkmark - Memory, Processor, Video, etc. Testing Win10 on this machine is prohibitively difficult workflow-wise, even though it'd be the best way to eliminate "faulty hardware" vector. I also have another contact in the wild, who has been running this Latitude 7400 2-in-1 hardware on Linux 4.19 branch, and while there have been other problems, he confirmed not having experienced such screen freezes. Ideally I'd test my setup with another identical laptop, but I have my doubts if the DELL people are going to supply me with one without purchase.</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>