https://bugzilla.kernel.org/show_bug.cgi?id=211425 Daniel Roschka (danielroschka+kernel@xxxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danielroschka+kernel@phoeni | |tydawn.de --- Comment #21 from Daniel Roschka (danielroschka+kernel@xxxxxxxxxxxxxxx) --- I got the same problem, although the symptoms differ slightly, probably because of the monitor in use. I use an AMD Ryzen 5 PRO 4650G with a DELL UltraSharp U2713H as display. As I started to use this APU with Linux 5.10 I had the problems from the beginning. Here is how it looks in my logs: > Sep 24 10:13:02 localhost kernel: [ 1200.673943] [drm] > perform_link_training_with_retries: Link training attempt 1 of 4 failed > Sep 24 10:13:22 localhost kernel: [ 1221.274959] [drm:atom_op_jump [amdgpu]] > *ERROR* atombios stuck in loop for more than 20secs aborting > Sep 24 10:13:22 localhost kernel: [ 1221.275078] > [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck > executing B228 (len 3608, WS 8, PS 0) @ 0xB376 > Sep 24 10:13:22 localhost kernel: [ 1221.275171] > [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck > executing B11C (len 268, WS 4, PS 0) @ 0xB16F > Sep 24 10:13:22 localhost kernel: [ 1221.275264] > [drm:dcn10_link_encoder_enable_dp_output [amdgpu]] *ERROR* > dcn10_link_encoder_enable_dp_output: Failed to execute VBIOS command table! > Sep 24 10:13:22 localhost kernel: [ 1221.311894] [drm] > perform_link_training_with_retries: Link training attempt 2 of 4 failed > Sep 24 10:13:24 localhost kernel: [ 1222.528157] [drm] > perform_link_training_with_retries: Link training attempt 3 of 4 failed > Sep 24 10:13:44 localhost kernel: [ 1243.230246] [drm:atom_op_jump [amdgpu]] > *ERROR* atombios stuck in loop for more than 20secs aborting > Sep 24 10:13:44 localhost kernel: [ 1243.230360] > [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck > executing B228 (len 3608, WS 8, PS 0) @ 0xB712 > Sep 24 10:13:44 localhost kernel: [ 1243.230453] > [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck > executing B11C (len 268, WS 4, PS 0) @ 0xB16F > Sep 24 10:13:44 localhost kernel: [ 1243.230553] > [drm:dcn10_link_encoder_enable_dp_output [amdgpu]] *ERROR* > dcn10_link_encoder_enable_dp_output: Failed to execute VBIOS command table! > Sep 24 10:13:44 localhost kernel: [ 1243.265681] [drm] enabling link 1 > failed: 15 > Sep 24 10:14:06 localhost kernel: [ 1265.165859] [drm:atom_op_jump [amdgpu]] > *ERROR* atombios stuck in loop for more than 20secs aborting > Sep 24 10:14:06 localhost kernel: [ 1265.165971] > [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck > executing B228 (len 3608, WS 8, PS 0) @ 0xB712 > Sep 24 10:14:06 localhost kernel: [ 1265.166064] > [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck > executing B11C (len 268, WS 4, PS 0) @ 0xB16F > Sep 24 10:14:06 localhost kernel: [ 1265.166157] > [drm:dcn10_link_encoder_enable_dp_output [amdgpu]] *ERROR* > dcn10_link_encoder_enable_dp_output: Failed to execute VBIOS command table! > Sep 24 10:14:30 localhost kernel: [ 1288.496778] [drm:atom_op_jump [amdgpu]] > *ERROR* atombios stuck in loop for more than 20secs aborting > Sep 24 10:14:30 localhost kernel: [ 1288.496903] > [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck > executing B228 (len 3608, WS 8, PS 0) @ 0xB712 > Sep 24 10:14:30 localhost kernel: [ 1288.496996] > [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck > executing B11C (len 268, WS 4, PS 0) @ 0xB16F > Sep 24 10:14:30 localhost kernel: [ 1288.497101] > [drm:dcn10_link_encoder_enable_dp_output [amdgpu]] *ERROR* > dcn10_link_encoder_enable_dp_output: Failed to execute VBIOS command table! The behavior I see is the same black screen after the display gets switched of using DPMS, however it doesn't recover on its own. I have to manually push a button on the monitor to re-trigger input detection or even completely power cycle the monitor. That also doesn't work in all cases. Having the monitor configured to use DisplayPort 1.1a it works most of the time with the mentioned manual intervention (however the success ratio got worse when I switched from Linux 5.10 to 5.14), with DisplayPort 1.2 it's completely unusable, as it's like a one in a hundred chance to get the monitor to display something again. I'd be happy to provide more information to further debug this issue. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
