Turning off monitor via DisplayPort causes Kernel warning + stack trace
Submitted by James Harvey @jamespharvey20
Assigned to Default DRI bug account
Link to original bug (#108294)
Description
Created attachment 141955
kernel warning + stack trace - from when HDMI monitor is turned off and back on
Up to date Arch Linux, including: linux 4.18.12.arch1-1, xf86-video-amdgpu 18.1.0-1, mesa 18.2.2-1, opencl-mesa 18.2.2-1, xorg-server 1.20.1-1, and plasma-desktop 5.13.5-1.
(Recently installed system that STARTED with: linux 4.18.9.arch1-1, mesa 18.2.1-1, and opencl-mesa 18.2.1-1.) It was also doing this then.
$ lspci -k | grep VGA
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] (rev e7)
Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
It's the: XFX AMD Radeon RX 580 GTS Black Edition 8GB GDDR5 PCI Express 3.0
I have (5) Acer K272HUL bmiidp monitors hooked up via DisplayPort. Left 2 are chained, and right 2 are chained.
ASRock EP2C602 Motherboard w/ P1.90 BIOS. (2) Intel Xeon E5-2690 (v1).
Anytime a monitor turns off, it causes a couple of kernel warnings and stack traces. Usually 2-3 warnings each time.
When the monitor turns back on, it just logs what are I think are (3) expected "[drm]" lines about the "new" connection.
See attached file for a sample of the kernel warnings/stack traces. The first part is when a monitor turned off, and the last part is when it turned back on.
By turned off/on, I mean regardless of if I press its power button on the monitor, pull the plug and plug it back in, or if a graphics issue somewhere in a driver or graphics API turns off a monitor until I cycle it.
The only time I'm having this now is occasionally a few programs that use OpenGL graphics. (Monitors turning off/back on was happening a lot with the Acer-provided DisplayPort cables, but replacing them with certified Accell UltraAV DisplayPort cables fixed that.)
When I turn it back on, KDE/Plasma properly re-adds it, gives it the right resolution, rotation, and alignment next to the other monitors.
Attachment 141955, "kernel warning + stack trace - from when HDMI monitor is turned off and back on":
rGeaiafC.txt
Activity
@jamespharvey20said:For searchability, here's a few of the lines I think are most useful. Again, the full dmesg section is attached to the original report.
[163437.787090] [drm] DM_MST: stopping TM on aconnector: 00000000286ba738 [id: 57]
[163437.787579] [drm] DM_MST: Disabling connector: 00000000032767bf [id: 64] [master: 00000000286ba738]
[163437.787655] [drm] DM_MST: Disabling connector: 00000000fac2e679 [id: 73] [master: 00000000286ba738]
[163437.789965] WARNING: CPU: 23 PID: 9069 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:2957 dm_crtc_helper_atomic_check+0x48/0x60 [amdgpu]
...
[163437.790086] RIP: 0010:dm_crtc_helper_atomic_check+0x48/0x60 [amdgpu]
...
[163437.790125] Call Trace:
[163437.790136] drm_atomic_helper_check_planes+0x130/0x1b0 [drm_kms_helper]
...
[163438.595567] [drm:generic_reg_wait [amdgpu]] ERROR REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:927
...This issue hasn't had any activity since 2019-11-19. 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.
