https://bugzilla.kernel.org/show_bug.cgi?id=211425 barnoid@xxxxxxx changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |barnoid@xxxxxxx --- Comment #25 from barnoid@xxxxxxx --- I have observed this as well on a 5.15.32 kernel. The system is equipped with an AMD Threadripper 3970X and 2 x LG HDMI displays connected via DP (4K@60Hz). The error happens when powering-up the monitors after a long power-down period. >[122427.564568] amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes >[122427.603599] amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes >[122427.954560] [drm] fb mappable at 0xC0E00000 >[122427.954563] [drm] vram apper at 0xC0000000 >[122427.954563] [drm] size 33177600 >[122427.954564] [drm] fb depth is 24 >[122427.954564] [drm] pitch is 15360 >[122427.954625] fbcon: amdgpudrmfb (fb0) is primary device >[122427.954759] Console: switching to colour frame buffer device 480x135 >[122427.954763] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer >device >[122482.729791] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for >>more than 20secs aborting >[122482.729839] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* >atombios stuck executing C220 (len 62, WS 0, PS 0) @ 0xC23C Ctrl-Alt-F1 and restarting X (i.e., the login manager) is sufficient to bring the system back into a useable state. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
