FS#65363 - [linux-firmware] UVD not responding on Oland GPUs

Attached to Project: Arch Linux
Opened by Shixin Zeng (szeng) - Tuesday, 04 February 2020, 03:48 GMT
Last edited by freswa (frederik) - Thursday, 20 February 2020, 21:32 GMT
Task Type Bug Report
Category Packages: Extra
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 2
Private No

Details

Description:
After upgrading to 20200122.1eb2408-1, I noticed that Gnome wayland session was not starting, and it auto started into Xorg. Looking into the journals, I found these lines:

Feb 03 21:21:48 ws kernel: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb 03 21:21:49 ws kernel: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb 03 21:21:50 ws kernel: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb 03 21:21:51 ws kernel: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb 03 21:21:51 ws kernel: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!!
Feb 03 21:21:51 ws kernel: radeon 0000:01:00.0: failed initializing UVD (-1).

Additional info:
GPU info:
lspci|grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] (rev 87)

After downgrading to 20191220.6871bff-1, the errors from kernel went away, and gnome wayland session started working again.
This task depends upon

Closed by  freswa (frederik)
Thursday, 20 February 2020, 21:32 GMT
Reason for closing:  Fixed
Additional comments about closing:  20200204.b791e15-1
Comment by loqs (loqs) - Tuesday, 04 February 2020, 05:34 GMT Comment by Saiki Kunio (kunio) - Tuesday, 04 February 2020, 11:13 GMT Comment by loqs (loqs) - Saturday, 08 February 2020, 10:22 GMT
Can you confirm linux-firmware 20200204.b791e15-1 has resolved the issue?
Comment by Saiki Kunio (kunio) - Sunday, 09 February 2020, 08:44 GMT
Upgrading to testing/linux-firmware 20200204.b791e15-1 seems to fix the issue for me.

Loading...