Created attachment 143433 [details] dmesg On resume after suspend I get the following error on my Dell Latitude E6540 with an Intel and a Radeon graphics controller running Arch Linux: [30893.254641] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [30893.254655] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing D170 (len 62, WS 0, PS 0) @ 0xD18C [30893.254668] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B8D2 (len 236, WS 4, PS 0) @ 0xB99F [30893.254679] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B830 (len 74, WS 0, PS 8) @ 0xB838 [30893.255547] [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [30893.255561] [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed In the attached output of dmesg, you'll see the error between 6170.599551 and 6291.483893 as well as after 30893.254641. The errors with the lower time happened after resume on a docking station with 2 DVI displays, the errors starting at 30893.254641 happened after resume back on the previous docking station with 1 DVI display. While I experience no issue in the first case, in the latter case Xorg crashes. Xorg keeps crashing on every start and the above error is printed until reboot. I've now tried different kernel versions and the error starts with Linux 4.17. When looking for differences between 4.16 and 4.17 I found this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.17.y&id=07f4f97d7b4bf325d9f558c5b58230387e4e57e0 Could this be the reason for the issue? Let me know if you need any further information.
Created attachment 143434 [details] lspci
Possibly related to this bug? https://bugzilla.kernel.org/show_bug.cgi?id=201519 if so, does this patch help? https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-5.0&id=450d007d199e632a1a4c4b91302deacd7d56815f
Yes, this patch helps. I had no atombios error with this patch on resume. Thanks!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.