Marc, it looks like the CurrentDmesg.txt shows a suspend/resume cycle. I take it then that the system is still responsive after resume, it's just that the display isn't working? If so, can you capture dmesg again after resume when booted with the kernel parameter drm.debug=0xe?
Marc, it looks like the CurrentDmesg.txt shows a suspend/resume cycle. I take it then that the system is still responsive after resume, it's just that the display isn't working? If so, can you capture dmesg again after resume when booted with the kernel parameter drm.debug=0xe?