Wrong DP ports and refresh rates after MST reset. MCLK is stuck at 100%

Brief summary of the problem:

When DP MST configuration is reset (such as: going out of sleep, power off/on both monitors, reset the MST splitter, reconnect the MST splitter to the laptop):

• Monitors get connected through different DP ports which breaks GNOME monitor layout
• Refresh rates get different for two identical monitors
• MCLK is stuck at 1.00G (max value) resulting in 29.0 W power consumption in idle mode
• Also noticed that in this mode Gnome Night Light does not work (it does not change the gamma of the monitors)

Hardware description:

• Radeon RX 6800M is set as primary GPU and connected through USB-C to 3*DP MST splitter to two 4k 60Hz monitors
• GPU: 03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1002:73df] (rev c3)
• MST splitter: USB-C® to MST Hub with Triple DisplayPort™ & PD
• Display(s): 2 * PHL 328E1 PHLC204 3840x2160 697x392mm 31.5-inch
• Full hw-probe with logs: PROBE-ID

System information:

• Distro name and Version: Manjaro 21.2.3
• Kernel version: Linux 5.16.7-1-MANJARO SMP PREEMPT Sun Feb 6 12:22:29 UTC 2022 x86_64 GNU/Linux
• AMD official driver version: N/A

How to reproduce the issue:

• Preconditions: laptop is shut down, USB-C MST splitter is connected to laptop and both monitors
• Cold boot the laptop, login into GNOME Wayland session, run sudo radeontop -b 3 notice the memory clock is 0.10G and changes when windows are open/resized
• Go to Settings -> Displays, configure the layout and apply
• Open ~/.config/monitors.xml (first configuration). Notice that external monitors are connected to the DP-3, DP-4 and have the same refresh rate 59.996623992919922
• Provided output of drm_info (drm_info_variable_mclk.txt) and amdgpu_mst_topology (amdgpu_mst_topology_variable_mclk.txt)
• Reset the MST splitter through the reset button, or unplug the power of both monitors and then plug them in again
• Notice that the monitor layout is lost and memory clock is fixed at 1.00G
• Go to Settings -> Displays, configure the layout again and apply
• Open ~/.config/monitors.xml (second configuration). Notice that external monitors are now connected to the DP-5, DP-6 and have different refresh rate 59.995990753173828 and 59.996051788330078 respectively
• Provided output of drm_info (drm_info_fixed_mclk.txt) and amdgpu_mst_topology (amdgpu_mst_topology_fixed_mclk.txt)

Attached files:

• Current boot journal: manjaro-log-helper.logs

added DC label

mentioned in issue #1969

mentioned in issue #1982 (closed)

changed title from Wrong DP ports and refresh rates after MST reset to Wrong DP ports and refresh rates after MST reset. MCLK is stuck at 100%

changed the description

I can still reproduce this issue in kernel 5.17.6.

This issue hasn't had any activity since 2022-05-17. The AMD driver stack changes rapidly and contains lots of shared code across products so it's possible that it has already been fixed. Please upgrade to a current stable kernel and userspace stack and try again. If you still experience this issue with the latest driver stack, please capture relevant logging and open a new issue referring back to this one.

closed

@superm1 I recently started using again the display/GPU configuration described in this ticket. Everything seems to be working OK but kernel log now has a few stack traces below during boot. Is it harmless or should I raise an issue for that? Here is the full log:amdgpu_mst_kernel_traces.txt

Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: ------------[ cut here ]------------
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: WARNING: CPU: 2 PID: 26 at drivers/gpu/drm/drm_mode_object.c:45 drm_mode_object_add+0x7a/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: Modules linked in: hid_asus asus_wmi ledtrig_audio sparse_keymap platform_profile rfkill usbhid amdgpu(+) i2c_algo_bit drm_ttm_helper ttm drm_sub>
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: CPU: 2 PID: 26 Comm: kworker/2:0 Not tainted 6.5.1-1-MANJARO #1 7346bd254052f3eff560d630d13644e007627eb3
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: Hardware name: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY/G513QY, BIOS G513QY.331 02/24/2023
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: Workqueue: events_long drm_dp_mst_link_probe_work [drm_display_helper]
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: RIP: 0010:drm_mode_object_add+0x7a/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: Code: c0 78 07 89 45 00 44 89 65 04 4c 89 ef e8 0e a6 4c 00 31 c0 85 db 0f 4e c3 5b 5d 41 5c 41 5d e9 6c 1d 4d 00 80 7f 58 00 74 a8 <0f> 0b eb a4>
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: RSP: 0018:ffffadf7802479b0 EFLAGS: 00010202
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: RAX: ffffffffc0ee2d60 RBX: ffff965d56680010 RCX: 0000000000000001
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: RDX: 00000000b0b0b0b0 RSI: ffff965d576cf310 RDI: ffff965d56680010
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: RBP: ffff965d576cf310 R08: ffffadf780247960 R09: ffff965d576b2600
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: R10: 00000000000390a0 R11: 0000000000000000 R12: 00000000b0b0b0b0
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: R13: 0000000000000005 R14: ffffffffa4e19fd5 R15: 0000000000000000
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: FS:  0000000000000000(0000) GS:ffff966c1e680000(0000) knlGS:0000000000000000
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: CR2: 00007f64383a6573 CR3: 000000096e620000 CR4: 0000000000750ee0
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: PKRU: 55555554
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: Call Trace:
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  <TASK>
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? drm_mode_object_add+0x7a/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? __warn+0x81/0x130
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? drm_mode_object_add+0x7a/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? report_bug+0x171/0x1a0
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? handle_bug+0x3c/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? exc_invalid_op+0x17/0x70
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? asm_exc_invalid_op+0x1a/0x20
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? drm_mode_object_add+0x7a/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_property_create+0xc0/0x170
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_property_create_enum+0x22/0x70
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_mode_create_colorspace_property+0xb7/0x100
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? amdgpu_dm_connector_funcs_reset+0x40/0xb0 [amdgpu fa58ae024af9f7e54af3774a5faf04403d37fbec]
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? drm_mode_object_add+0x7a/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? __warn+0x81/0x130
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? drm_mode_object_add+0x7a/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? report_bug+0x171/0x1a0
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? handle_bug+0x3c/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? exc_invalid_op+0x17/0x70
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? asm_exc_invalid_op+0x1a/0x20
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? drm_mode_object_add+0x7a/0x80
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_property_create+0xc0/0x170
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_property_create_enum+0x22/0x70
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_mode_create_colorspace_property+0xb7/0x100
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? amdgpu_dm_connector_funcs_reset+0x40/0xb0 [amdgpu fa58ae024af9f7e54af3774a5faf04403d37fbec]
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  amdgpu_dm_connector_init_helper+0x204/0x2d0 [amdgpu fa58ae024af9f7e54af3774a5faf04403d37fbec]
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  dm_dp_add_mst_connector+0xbd/0x1a0 [amdgpu fa58ae024af9f7e54af3774a5faf04403d37fbec]
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_dp_mst_port_add_connector+0x228/0x310 [drm_display_helper 02073186b30ded4ba195839058b4c948a04b6863]
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_dp_send_link_address+0x536/0xad0 [drm_display_helper 02073186b30ded4ba195839058b4c948a04b6863]
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? srso_alias_return_thunk+0x5/0x7f
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? queue_work_on+0x3b/0x50
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? srso_alias_return_thunk+0x5/0x7f
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_dp_check_and_send_link_address+0x7a/0xa0 [drm_display_helper 02073186b30ded4ba195839058b4c948a04b6863]
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  drm_dp_mst_link_probe_work+0x125/0x1a0 [drm_display_helper 02073186b30ded4ba195839058b4c948a04b6863]
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  process_one_work+0x1e1/0x3f0
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  worker_thread+0x51/0x390
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? __pfx_worker_thread+0x10/0x10
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  kthread+0xe8/0x120
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? __pfx_kthread+0x10/0x10
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ret_from_fork+0x34/0x50
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ? __pfx_kthread+0x10/0x10
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  ret_from_fork_asm+0x1b/0x30
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel:  </TASK>
Sep 16 22:19:47 dvoloshyn-rogstrixg513qy kernel: ---[ end trace 0000000000000000 ]---

That is harmless and should be fixed with this patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69a959610229

And I sent it to stable separately so it will not be noisy in upcoming stable kernels too: https://lore.kernel.org/stable/42a47017-633a-4749-8215-2ff35913f578@amd.com/