[kernel-bugs] [Bug 1177256] New: AMD RX 570, amdgpu-pro and kernel 5.3.18-lp152.44-default
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
Bug ID: 1177256
Summary: AMD RX 570, amdgpu-pro and kernel
5.3.18-lp152.44-default
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: x86-64
OS: openSUSE Leap 15.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs@opensuse.org
Reporter: vkelim@bigpond.com
QA Contact: qa-bugs@suse.de
Found By: ---
Blocker: ---
Created attachment 842226
--> http://bugzilla.opensuse.org/attachment.cgi?id=842226&action=edit
/var/log/messages
On updating to kernel 5.3.18-lp152.41-default or 5.3.18-lp152.44-default (from
kernel 5.3.18-lp152.36-default) I experienced a `freeze' during system boot-up.
Using debug mode, the last message was:
Fb0: switching to amdgpudrmfb from EFI VGA
Something seems to be going from when switching graphics mode. Adding
'nomodeset' to the kernel option allows the boot to go to completion, at the
cost of not having an accelerated graphics driver!
The problem is perhaps the same as described on
https://forum.level1techs.comhttps://forum.level1techs.com/t/fb0-switching-t...
, some sort of problem with MMU and ATS?
I am currently booting on the previous kernel version (5.3.18-lp152.36-default)
without any difficulty
My hardware:
Asrock B550M
AMD Ryzen 5 3600
AMD RX 570 graphics card (MSI) - amdgpu-pro driver
Attached is what appears to be the relevant section of /var/log/messages
2020-10-03T16:11:09.966215+10:00 localhost kernel: [ 3.851924] mc: Failed to
load firmware "amdgpu/polaris10_mc.bin"
2020-10-03T16:11:09.966216+10:00 localhost kernel: [ 3.851963]
[drm:gmc_v8_0_sw_init [amdgpu]] *ERROR* Failed to load mc firmware!
2020-10-03T16:11:09.966217+10:00 localhost kernel: [ 3.851998]
[drm:amdgpu_device_init [amdgpu]] *ERROR* sw_init of IP block
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c1
--- Comment #1 from David Fong
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c2
Takashi Iwai
2020-10-03T16:11:09.966215+10:00 localhost kernel: [ 3.851924] mc: Failed to load firmware "amdgpu/polaris10_mc.bin"
Make sure that you have this file under /lib/firmware. If the file is there, it's likely a problem of initrd, and it can be some (long-standing) issue of amdgpu-pro package. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c3
--- Comment #3 from Stefan Dirsch
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c4
--- Comment #4 from David Fong
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c5
Stefan Dirsch
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c6
--- Comment #6 from Stefan Dirsch
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c7
Takashi Iwai
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c8
--- Comment #8 from Stefan Dirsch
The problem is that the dracut config snippet contains fw_dir+="/lib/firmware/5.3.18-lp152.36-default"
and this *overrides* the whole firmware search path, not appending the given one.
Hmm. The manual page tells me something different. # man dracut.conf [...] fw_dir+=" :<dir>[:<dir> ...] " Specify additional directories, where to look for firmwares, separated by : [...] Nevertheless I think this is what they want (replacing them).
Meanwhile the standard amdgpu firmware is provided in /lib/firmware. So this path is no longer searched, hence the firmware loading fails.
Well, I would assume the AMD Pro driver ships firmware with special features and/or better tested against the Pro driver.
So, the simplest solution would be to just drop the line above.
Well, I would assume this would removed special features of Pro driver or may make it less stable. So I wouldn't recommend this.
OTOH, if a KMP provides its own firmware in /lib/firmware/$VERSION and it must use it, it becomes a problem, indeed, when the kmp is weak-linked to a different kernel version. Is this really the case?
AFAIK AMD Pro drivers are installed via dkms, so this is not weak-linked but probably rebuilt once when the new kernel gets started (if I understood the dkms system correctly).
If yes, we'd need to fix weak-modules2 script in suse-module-tools package to deal with the firmware files in a weak-linked kmp, too.
AMD would need to fix this in dkms somehow. Probably at the same time when the
modules(s) get rebuilt for the new kernel version.
Either copying the firmware files to /lib/modules/
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c9
--- Comment #9 from Takashi Iwai
OTOH, if a KMP provides its own firmware in /lib/firmware/$VERSION and it must use it, it becomes a problem, indeed, when the kmp is weak-linked to a different kernel version. Is this really the case?
AFAIK AMD Pro drivers are installed via dkms, so this is not weak-linked but probably rebuilt once when the new kernel gets started (if I understood the dkms system correctly).
If yes, we'd need to fix weak-modules2 script in suse-module-tools package to deal with the firmware files in a weak-linked kmp, too.
AMD would need to fix this in dkms somehow. Probably at the same time when the modules(s) get rebuilt for the new kernel version. Either copying the firmware files to /lib/modules/
or symlinking them.
Right, that's the missing step. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
Stefan Dirsch
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256#c10
--- Comment #10 from Stefan Dirsch
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1177256
Stefan Dirsch
participants (1)
-
bugzilla_noreply@suse.com