Bug 1802641 - kernel 5.4 Bug Radeon
Summary: kernel 5.4 Bug Radeon
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: linux-firmware
Version: 31
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1811090 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-13 15:31 UTC by xzj8b3
Modified: 2020-10-23 14:24 UTC (History)
24 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-10-23 14:24:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg (85.27 KB, text/plain)
2020-02-13 15:31 UTC, xzj8b3
no flags Details

Description xzj8b3 2020-02-13 15:31:10 UTC
Created attachment 1662981 [details]
dmesg

Does the Bug Radeon persist even with Kernel 5.4.18 when it will be solved allowing the driver to boot correctly ?





[drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   66.027338] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   67.047516] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   68.067686] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   69.087879] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   70.108070] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   71.128240] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   72.148409] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   73.168580] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   74.188755] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
[   74.208771] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!!
[   74.208776] radeon 0000:04:00.0: failed initializing UVD (-1).

Comment 1 xzj8b3 2020-02-18 21:15:07 UTC
But at least on kernel 5.5 problem has been fixed given that bugs reoccur every time the 5.4 kernel is released???

Comment 3 virtmem4096 2020-03-06 13:42:30 UTC
Else you can downgrade linux-firmware: yum downgrade linux-firmware

Comment 4 virtmem4096 2020-03-06 13:53:33 UTC
UPD: downgrade not help

Comment 5 Justin M. Forbes 2020-03-06 15:23:27 UTC
Thanks for the update, will reassign to linux-firmware.

Comment 6 Justin M. Forbes 2020-03-06 15:24:43 UTC
*** Bug 1811090 has been marked as a duplicate of this bug. ***

Comment 7 xzj8b3 2020-03-08 17:22:50 UTC
Now back to Windows,too many last kernel problems with that graphics card and you that bug was communicated very promptly for each release!!!!

For now I need Photoshop, maybe I will try Again Fedora after summer hoping that by then it has solved some Bugs that on economic Notebooks bring many problems!!!!

Comment 8 Przemek Klosowski 2020-03-12 02:42:46 UTC
I also see that on [AMD/ATI] Mars XTX [Radeon HD 8790M]. It started showing up in mid Feb, when I upgraded the kernel to 5.4.18-200.fc31.x86_64 and later, but I agree it's probably due to linux-firmware changes, not kernel.

It can be mitigated by adding radeon.modeset=0 to the kernel commandline in /etc/defaults/grub followed by grub2-mkconfig

I also tried directly disabling features in the driver, per advice from Ubuntu
cat > /etc/modprobe.d/radeon.conf
options radeon vce=0

but it didn't work (VCE is not a problem, UVD is). Somewhere else I saw a patch that allowed no_uvd=1 but I wasn't sure if it went mainline, so I didn't even try it

Comment 9 Peter Robinson 2020-10-23 14:24:33 UTC
Fixed in the 20200316 release


Note You need to log in before you can comment on or make changes to this bug.