FS#78962 - [linux] AMDGPU: Black screen with multiple monitors, "*ERROR* Error waiting for DMUB idle: status=3"

Attached to Project: Arch Linux
Opened by ldare373 (ldare373) - Monday, 03 July 2023, 15:24 GMT
Last edited by Toolybird (Toolybird) - Monday, 03 July 2023, 21:04 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

When using two monitors, both screens turn black and remain that way until one is disconnected. One is connected via DisplayPort, and the other through HDMI, both on the motherboard. The following error also shows up repeatedly in dmesg independent of how many monitors are connected: "*ERROR Error waiting for DMUB idle: status=3". The issue shows up during startup without any other actions required. The issue was not present as recent as a couple weeks ago. Disabling early KMS delayed the onset of the issue until after initramfs, and the "nomodeset" parameter is able to get one screen working with two plugged in, but I believe both are due to amdgpu being disabled.

I have tried the linux and linux-lts kernels on my installation with no change. The issue is also present with version 2023.07.01 of the Arch Linux ISO, but not version 2023.06.01.

Hardware:
AMD Ryzen 5 7600X
Integrated graphics (RDNA2)
B650 chipset

The attached files were created with version 2023.07.01 of the ISO
Kernel: linux 6.3.9-arch1-1

Attached Files:
dmesg > dmesg.txt
pacman -Q > pacman.txt
lspci -vvv > lspci.txt

A second monitor is plugged in after about 220 seconds of uptime.
   lspci.txt (92.7 KiB)
   dmesg.txt (95.7 KiB)
   pacman.txt (7 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 03 July 2023, 21:04 GMT
Reason for closing:  Upstream
Additional comments about closing:  See comments
Comment by loqs (loqs) - Monday, 03 July 2023, 17:25 GMT
https://gitlab.freedesktop.org/drm/amd/-/issues/2666
Comment by ldare373 (ldare373) - Monday, 03 July 2023, 18:19 GMT
Thanks for sharing that! Since it's upstream, I'm going to request to close the task.

Edit: Until it's fixed upstream, downgrading linux-firmware to 20230404.2e92a49f-1 seems to resolve the issue.

Edit 2 (June 9): Bug is fixed on arch with linux-firmware 20230625.ee91452d-4
https://gitlab.archlinux.org/archlinux/packaging/packages/linux-firmware/-/commit/a836641788011dd993d71f19fb92b1b4a17d4b82

Loading...