Bug 1520682

Summary:	amdgpu module fails to load firmware
Product:	[Fedora] Fedora	Reporter:	Isaac Smith <isaac>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	27	CC:	airlied, ajax, bskeggs, ewk, hdegoede, ichavero, isaac, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:05:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Isaac Smith 2017-12-04 23:18:36 UTC

Description of problem:
After upgrading from Fedora 26 to 27, the AMDGPU kernel module fails to load the firmware for my card (Radeon RX 460). The card worked fine with AMDGPU in 26.

From the kernel log:

[    4.324134] [drm] initializing kernel modesetting (POLARIS11 0x1002:0x67EF 0x1682:0x9460 0xCF).
[    4.324145] [drm] register mmio base: 0xFE900000
[    4.324146] [drm] register mmio size: 262144
[    4.324154] [drm] probing gen 2 caps for device 1022:1453 = 733903/e
[    4.324157] [drm] probing mlw for device 1022:1453 = 733903
[    4.324162] [drm] UVD is enabled in VM mode
[    4.324164] [drm] VCE enabled in VM mode
[    4.352466] [drm] BIOS signature incorrect 0 0
[    4.352470] amdgpu 0000:09:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
[    4.352489] ATOM BIOS: 113-BAFFIN_PRO_160513_D5_2G_HYAJR_OC_0_W81
[    4.352494] [drm] GPU post is not needed
[    4.352591] [drm] vm size is 64 GB, block size is 13-bit
[    4.352606] amdgpu 0000:09:00.0: Direct firmware load for amdgpu/polaris11_mc.bin failed with error -2
[    4.352607] mc: Failed to load firmware "amdgpu/polaris11_mc.bin"
[    4.352634] [drm:gmc_v8_0_sw_init [amdgpu]] *ERROR* Failed to load mc firmware!
[    4.352655] [drm:amdgpu_device_init [amdgpu]] *ERROR* sw_init of IP block <gmc_v8_0> failed -2
[    4.352657] amdgpu 0000:09:00.0: amdgpu_init failed
[    4.352659] amdgpu 0000:09:00.0: Fatal error during GPU init
[    4.352660] [drm] amdgpu: finishing device.
[    4.352661] [TTM] Memory type 2 has not been initialized
[    4.373702] amdgpu: probe of 0000:09:00.0 failed with error -2
[    4.501310] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)

The file polaris11_mc.bin is present along with a number of other firmware files in /lib/firmware/amdgpu. However, it is not present in the initramfs as far as I can tell, and the last line of the log snippet seems to indicate that the amdgpu module is being loaded before my root drive (an LVM volume) is mounted.


Version-Release number of selected component (if applicable):
Fedora 27, fully updated at the time of this report.

How reproducible:
Unknown, I only have one machine with this configuration and have not attempted a full reinstall.

Steps to Reproduce:
1. Use a machine with a Radeon RX 460
2. Start Fedora 27

Actual results:
The amdgpu module fails to load firmware, resulting in use of fallback graphics drivers.

Expected results:
The amdgpu loads firmware correctly.

Comment 1 Isaac Smith 2017-12-05 16:15:39 UTC

Rebuilding my initramfs with 'dracut --regenerate-all --force --install "/usr/lib/firmware/amdgpu/*"' worked, so I guess either the firmware needs to go into the initramfs by default or the module load should be delayed until after root is mounted.

Comment 2 Laura Abbott 2018-02-20 20:05:27 UTC

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Isaac Smith 2018-02-21 16:05:43 UTC

This seems to be fixed as of kernel 4.15.3-300.f27.