Bug 1663126 - [regression] kernel-4.19.13-300.fc29.x86_64 broke AMD Raven Ridge GPU firmware
Summary: [regression] kernel-4.19.13-300.fc29.x86_64 broke AMD Raven Ridge GPU firmware
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-03 09:25 UTC by Luya Tshimbalanga
Modified: 2019-01-07 18:48 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-04 04:09:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Journal report with failed raven ridge firmware to load (204.10 KB, text/plain)
2019-01-03 09:25 UTC, Luya Tshimbalanga
no flags Details

Description Luya Tshimbalanga 2019-01-03 09:25:20 UTC
Created attachment 1518100 [details]
Journal report with failed raven ridge firmware to load

Description of problem:
The current kernel broke the Raven Ridge firmware as found on HP Envy x360 laptop despite the updated linux-firmware to 20181219-89.git0f22c852. A regression compared to kernel 4.19.12-301

Version-Release number of selected component (if applicable):
kernel-4.19.13-300.fc29.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Update to kernel-4.19.13-300.fc29.x86_64

2.
3.

Actual results:
journalctl -b -2 --no-hostname| grep raven
Jan 02 16:49:38 kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/raven_gpu_info.bin failed with error -2
Jan 02 16:49:38 kernel: amdgpu 0000:03:00.0: Failed to load gpu_info firmware "amdgpu/raven_gpu_info.bin"

Expected results:
Should boot normally

Additional info:

Comment 1 Yanko Kaneti 2019-01-03 10:21:14 UTC
Did you update your initramfs after the linux-firmware update? error -2 is usually the file just isn't there..

Comment 2 Luya Tshimbalanga 2019-01-03 16:37:38 UTC
Using 'dracut --kver 4.19.13-300.fc29.x86_64 --force' has no effect. I even reinstalled linux-firmware

rpm -q linux-firmware
linux-firmware-20181219-89.git0f22c852.fc29.noarch

Raven Ridge is available

/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_asd.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_ce.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_dmcu.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_gpu_info.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_me.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_mec.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_mec2.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_pfp.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_rlc.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_sdma.bin
/usr/lib/firmware/4.19.13-300.fc29.x86_64/amdgpu/raven_vcn.bin
/usr/lib/firmware/amdgpu/raven_asd.bin
/usr/lib/firmware/amdgpu/raven_ce.bin
/usr/lib/firmware/amdgpu/raven_dmcu.bin
/usr/lib/firmware/amdgpu/raven_gpu_info.bin
/usr/lib/firmware/amdgpu/raven_me.bin
/usr/lib/firmware/amdgpu/raven_mec.bin
/usr/lib/firmware/amdgpu/raven_mec2.bin
/usr/lib/firmware/amdgpu/raven_pfp.bin
/usr/lib/firmware/amdgpu/raven_rlc.bin
/usr/lib/firmware/amdgpu/raven_sdma.bin
/usr/lib/firmware/amdgpu/raven_vcn.bin

Comment 3 Yanko Kaneti 2019-01-03 16:50:06 UTC
"has no effect" is a little ambiguous. Did you make sure the actual initrd that's configured in your bootloader for 4.19.13-300.fc29.x86_64  is updated after that command?
lsinird  ... | grep raven

Comment 4 Luya Tshimbalanga 2019-01-03 16:59:16 UTC
(In reply to Yanko Kaneti from comment #3)
> "has no effect" is a little ambiguous. Did you make sure the actual initrd
> that's configured in your bootloader for 4.19.13-300.fc29.x86_64  is updated
> after that command?
> lsinird  ... | grep raven

# lsinird  ... | grep raven
bash: lsinird: command not found...

Comment 5 Luya Tshimbalanga 2019-01-03 17:04:03 UTC
I figured it was a typo

lsinitrd -k 4.19.13-300.fc29.x86_64 | grep raven gives no result.

Comment 6 Luya Tshimbalanga 2019-01-03 17:06:04 UTC
lsinitrd -k 4.19.13-300.fc29.x86_64 | grep raven gives no result.

Contrast with lsinitrd -k 4.19.12-301.fc29.x86_64 | grep raven

lsinitrd -k 4.19.12-301.fc29.x86_64 | grep raven
-rw-r--r--   1 root     root        49664 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_asd.bin
-rw-r--r--   1 root     root         9344 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_ce.bin
-rw-r--r--   1 root     root          316 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_gpu_info.bin
-rw-r--r--   1 root     root        17536 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_me.bin
-rw-r--r--   2 root     root       268048 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_mec2.bin
-rw-r--r--   2 root     root            0 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_mec.bin
-rw-r--r--   1 root     root        21632 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_pfp.bin
-rw-r--r--   1 root     root        39036 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_rlc.bin
-rw-r--r--   1 root     root        17408 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_sdma.bin
-rw-r--r--   1 root     root       341728 Dec  4 02:27 usr/lib/firmware/amdgpu/raven_vcn.bin

I don't know why that update somehow will no pick raven firmware.

Comment 7 Luya Tshimbalanga 2019-01-04 04:09:48 UTC
I figured out what actually happened. The system has ROCm package installed needed to test ROCm OpenGL for applications like Gimp,Darktable and Blender.
According to AMD ROCm documentation (https://rocm.github.io/install_issues.html), the issue is caused from ROCm driver not properly initialize initramfs.

Instead of using "dracut -fv 4.19.13-300.fc29.x86_64.img" command, "dracut --regenerate-all --force" worked and properly initialize the Raven Ridge firmware.

dmesg | grep amdgpu
[    5.465710] [drm] amdgpu kernel modesetting enabled.
[    5.494477] fb: switching to amdgpudrmfb from EFI VGA
[    5.494779] amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
[    5.499469] amdgpu 0000:03:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
[    5.499473] amdgpu 0000:03:00.0: GART: 1024M 0x000000F500000000 - 0x000000F53FFFFFFF
[    5.499760] [drm] amdgpu: 2048M of VRAM memory ready
[    5.499762] [drm] amdgpu: 3072M of GTT memory ready.
[    5.659737] amdgpu: [powerplay] dpm has been enabled
[    5.660921] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
[    5.706422] fbcon: amdgpudrmfb (fb0) is primary device
[    5.706428] amdgpu 0000:03:00.0: fb0: amdgpudrmfb frame buffer device
[    5.713635] amdgpu 0000:03:00.0: ring 0(gfx) uses VM inv eng 4 on hub 0
[    5.713639] amdgpu 0000:03:00.0: ring 1(comp_1.0.0) uses VM inv eng 5 on hub 0
[    5.713642] amdgpu 0000:03:00.0: ring 2(comp_1.1.0) uses VM inv eng 6 on hub 0
[    5.713645] amdgpu 0000:03:00.0: ring 3(comp_1.2.0) uses VM inv eng 7 on hub 0
[    5.713648] amdgpu 0000:03:00.0: ring 4(comp_1.3.0) uses VM inv eng 8 on hub 0
[    5.713650] amdgpu 0000:03:00.0: ring 5(comp_1.0.1) uses VM inv eng 9 on hub 0
[    5.713653] amdgpu 0000:03:00.0: ring 6(comp_1.1.1) uses VM inv eng 10 on hub 0
[    5.713656] amdgpu 0000:03:00.0: ring 7(comp_1.2.1) uses VM inv eng 11 on hub 0
[    5.713658] amdgpu 0000:03:00.0: ring 8(comp_1.3.1) uses VM inv eng 12 on hub 0
[    5.713661] amdgpu 0000:03:00.0: ring 9(kiq_2.1.0) uses VM inv eng 13 on hub 0
[    5.713664] amdgpu 0000:03:00.0: ring 10(sdma0) uses VM inv eng 4 on hub 1
[    5.713667] amdgpu 0000:03:00.0: ring 11(vcn_dec) uses VM inv eng 5 on hub 1
[    5.713669] amdgpu 0000:03:00.0: ring 12(vcn_enc0) uses VM inv eng 6 on hub 1
[    5.713672] amdgpu 0000:03:00.0: ring 13(vcn_enc1) uses VM inv eng 7 on hub 1
[    5.713675] amdgpu 0000:03:00.0: ring 14(vcn_jpeg) uses VM inv eng 8 on hub 1
[    5.718785] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:03:00.0 on minor 0
[    5.751630] audit: type=1130 audit(1546573900.976:68): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-backlight@backlight:amdgpu_bl0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  827.479692] amdgpu: [powerplay] pp_dpm_switch_power_profile was not implemented.
 luya 


I am closing this report now the issue is resolved. Thanks for helping debugging.


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