Thanks but I meant collecting drm_info while the bug was still happening. It's good that it seems to be working now.
If the problem reoccurs in future then most likely it's a combination of a hardware and kernel problem whereby the kernel can only detect support for 30Hz when waking up. So if it continues to happen in future please try using a new monitor cable.
Thanks but I meant collecting drm_info while the bug was still happening. It's good that it seems to be working now.
If the problem reoccurs in future then most likely it's a combination of a hardware and kernel problem whereby the kernel can only detect support for 30Hz when waking up. So if it continues to happen in future please try using a new monitor cable.