<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BDW] System hard lock-up on resume from suspend" href="https://bugs.freedesktop.org/show_bug.cgi?id=91585#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BDW] System hard lock-up on resume from suspend" href="https://bugs.freedesktop.org/show_bug.cgi?id=91585">bug 91585</a> from <a class="email" href="mailto:an.inbox@free.fr" title="Jerome <an.inbox@free.fr>"> Jerome</a> <pre>Created <a href="attachment.cgi?id=117599" name="attach_117599" title="Console mode resume glitch, journal extract (nightly kernel)">attachment 117599</a> <a href="attachment.cgi?id=117599&action=edit" title="Console mode resume glitch, journal extract (nightly kernel)">[details]</a> Console mode resume glitch, journal extract (nightly kernel) I tried suspend/resume with X disabled (console mode) with the Intel DRM nightly kernel (same as before) just in case, and there is a i915/DRM glitch. The system recovers and works fine, but there's a console output and journal info. It occurred 3 times out of 3, so may be systematic (more tests to do). I attached the relevant journal extracts. If it's systematic, it may not fully explain the lock-up when X is enabled (as the lock-up is not systematic), but hopefully may be related and could give an idea where to look. TBC. In any case, when X is enabled and the system locks-up it's a hard lock-up: the network is down (no reply to ping), and USB is also down (when hooking an optical mouse, its bottom LED doesn't light up). So not easy to see what happened... For more info on the laptop environment, see Debian initial bug: <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794393">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794393</a> Let me know if there's anything I can do to collect useful information. I'll try in console mode with the older kernels I used too to see if I get a similar behavior.</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>