I don’t have a Radeon VII to implement this on, and it almost certainly wont work on the Vega 20, the Vega reset implementation is far more complex and some base register addresses have been changed.
Would be the logical next step. Anyone have a Radeon VII to give to Geoff?
You could provide it to him as a temp and he sends it back after he is done.
I know someone from the forums with a Radeon VII locally. I could ask him about it.
Is there something I need to have in mind in regards to the setup. I took the 5.3-rc1 Manjaro kernel from here: https://gitlab.manjaro.org/packages/core/linux53 and edited the PKGBUILD so it incorporates the new patch.
Now when I do a clean shutdown and try to restart the VM with my Navi passed through the boot hangs: I can see the TianoCore boot logo and the endless rotating windows loading icon below it.
I followed the directions in the arch wiki to setuo passthrough on Manjaro.
My VM Setup is the following (removed)
Edit: Don’t know what was wrong. I did destroy the VM and kept the disc image and created a new VM with the very same image. Windows got a error saying it needs to restart and now everything works.
Hi,
PSA: Currently as of 10.11.2019 and Kernel 5.3.8 the Patch is included into Manjaro stable. If you use Manjaro with the 5.3. Kernel the Patch is already included!
These threads from the Manjaro forum explained it for me:
I have done a self compilation of the Kernel the first time myself for this patch. It is not much work on Manjaro and Arch in general.
-
Find the correct sources: First you clone the repositories of the kernel source for the kernel you want to use from here: https://gitlab.manjaro.org/packages/core. So in this page I would recommend you go into the linux53 branch and then hit the blue clone-button and copy the “Clone via https”-link. You need the package “git” installed on your system.
-
Clone the code: Use the terminal navigate to a folder of your choice and run “git clone https://gitlab.manjaro.org/packages/core/linux53.git”. You will have a new linux53 folder. These are the sources for the 5.3 Manjaro Kernel.
-
Copy the code from the Navi patch into a file in the linux53 folder and name it navi.patch or something like this.
-
Create a SHA256 Checksum of the “navi.patch” file with "shasum -a 256 and keep the checksum it generates
-
Open the PKGBUILD file in the linux53 folder in a text editor:
-
Change the line
_kernelname=-MANJAROto something like_kernelname=-VFIO. You do this because it makes it easier to see that you use your patched Kernel when yo rununame -uand also avoids the case that when Manjaro publishes a newer kernel version that yours will be replaced with a newer but unpatched version. -
At the beginning of the file there is a list of files beginning with “source=(” and then listing all the files. At the End behind “‘0013-bootsplash.patch’” create an additional line before the braces close with ‘navi.patch’ or whatever you named your patch file.
-
Directly below the sources part in the PKGBUILD file is the “sha256sums=(”-part with the sha256 checksums. Because you added the navi.patch as the last file in the sources section you need to add the checksum you generated here as the last checksum before the braces close in the same manner.
At this point the PKGBUILD will know about your patch and can verify it with the checksum you generated. Now we need to apply it.
-
Behind the end of the
patch -Np1 -i “${srcdir}/vfs-ino.patch”
lines add an additional line like this:
patch -Np1 -i "${srcdir}/navi.patch"`
-
Save and apply your edits
-
Install manjaro-tools-pkg
sudo pacman -S manjaro-tools-pkg -
outside of the linux53 folder run
buildpkg -p linux53 -
The compilation takes 2 hours for me -> wait
-
in the terminal
cd /var/cache/manjaro-tools/pkg/stable/x86_64your new kernel and it’s header will be there -
Install both with
sudo pacman -U <kernelfilename> <headerfilename> -
Reboot and choose your new kernel in the grub menu by holding shift while booting
-
?
-
Profit
Edit: I wanted to add that packages you install from the Arch User Repository (AUR) on Arch or Manjaro are being build in the same way. You should familiarize yourselfs with the build steps because you can verify and edit alls the software from the AUR if you understand buildpkg.
Edit2: Currently as of 10.11.2019 and Kernel 5.3.8 the Patch is included into Manjaro stable. If you use Manjaro with the 5.3. Kernel the Patch is already included!
6 Likes
Hey guys,
I have a RX 5700 and applied the patch to the kernel, but whenever I try to restart the VM, it always spits out that stuff to dmesg:
[53019.066294] vfio-pci 0000:0b:00.0: Navi10: SOL 0xffffffff
[53019.066295] vfio-pci 0000:0b:00.0: Navi10: device doesn't need to be reset
[53019.066689] vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x19@0x270
[53019.066708] vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x1b@0x2d0
[53019.066715] vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x25@0x400
[53019.066717] vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x26@0x410
[53019.066719] vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x27@0x440
.
.
.
[53026.500510] AMD-Vi: Completion-Wait loop timed out
[53026.680801] AMD-Vi: Completion-Wait loop timed out
[53026.827330] AMD-Vi: Completion-Wait loop timed out
[53026.968287] AMD-Vi: Completion-Wait loop timed out
[53027.094991] AMD-Vi: Completion-Wait loop timed out
[53027.260391] AMD-Vi: Completion-Wait loop timed out
[53027.316206] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0b:00.0 address=0x7fb5724b0]
[53026.500510] AMD-Vi: Completion-Wait loop timed out
[53026.680801] AMD-Vi: Completion-Wait loop timed out
[53026.827330] AMD-Vi: Completion-Wait loop timed out
[53026.968287] AMD-Vi: Completion-Wait loop timed out
[53027.094991] AMD-Vi: Completion-Wait loop timed out
[53027.260391] AMD-Vi: Completion-Wait loop timed out
[53027.316206] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0b:00.0 address=0x7fb5724b0]
[53027.563953] AMD-Vi: Completion-Wait loop timed out
[53028.047223] AMD-Vi: Completion-Wait loop timed out
[53028.318122] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0b:00.0 address=0x7fb572500]
[53029.320002] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0b:00.0 address=0x7fb5725d0]
[53064.854092] vfio-pci 0000:0b:00.0: Navi10: SOL 0x0
[53064.854095] vfio-pci 0000:0b:00.0: Navi10: device doesn't need to be reset
Do I need to use qemu 4.1? I’m using Debian Buster as my OS btw. (but with a 5.3.7 kernel).
By any chance are you running a threadripper?
Sorry I didn’t state that! It’s a R1600 on an AB350N-Gaming WIFI (mITX) (so it’s the primary and I have to use a vbios file)
I’ve got the exact same problem with a Ryzen 2700. Since I’m running a 5.3.6 kernel with this patch, I wonder if its related to the kernel version.
I can however tell you that it’s not related to the RX5700 being the primary GPU or not. I tried both: initialized as second GPU and using it without a vbios-file and initialized as primary gpu using a vbios file. Both work for the first time and fail afterwards with the above mentioned dmesg output.
Thanks, that is good to know! I tried the 5.2.sth with the patch, too, but that’s not the cause either. However I always get the message, that the patch ended unexpectedly or something like that when I apply the patch. Is that to be expected?
What distro are you using?
I’m using Fedora 30.
One really “funny” thing. I can indeed start a VM with the RX5700 repeatedly with the following procedure:
Let the UEFI claim the RX5700 on boot. Pass the GPU over to the vfio-pci driver after boot but keep the efi-framebuffer runing on the GPU. Then try to start a VM (im my case Win10). It will crash as the framebuffer is still connected to the GPU. Disconnect the efi framebuffer and start the VM.
It will start now BUT the Windows AMD driver won’t load even though the Windows device manager and tools like GPU-Z will recognize the GPU as RX5700.
I can now shutdown and start the VM at will. But every time the AMD driver won’t load and I’m stuck at 800x600.
Would it be possible to get a .patch file for this update? As with the vega fix
When I get to it 
as with all things open source and free, they happen as life and time allows 
3 Likes
I appreciate it! Just installed a win vm with looking glass, and am finally free of microsoft! Very happy to know that its in the queue even if its a bit far off lol
1 Like
now it even did some weirder stuff… This happened when I tried to start a macOS VM after shutting down the Q35 Windows 10 VM normally. It always crashes the card, but this time it just printed something different to the logs and I had to force shutdown the whole pc! Here we go, hope this helps:
[48504.498914] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0b:00.0 address=0x7fb573b20]
[48504.665666] AMD-Vi: Completion-Wait loop timed out
[48504.832874] AMD-Vi: Completion-Wait loop timed out
[48505.032100] AMD-Vi: Command buffer timeout
[48505.231066] AMD-Vi: Command buffer timeout
[48505.231096] ------------[ cut here ]------------
[48505.231115] WARNING: CPU: 10 PID: 26679 at drivers/iommu/amd_iommu.c:1272 __domain_flush_pages.cold.44+0xc/0x13
[48505.231116] Modules linked in: hid_generic(E) usbhid(E) hid(E) xt_nat(E) xt_tcpudp(E) veth(E) xt_conntrack(E) xt_MASQUERADE(E) nf_conntrack_netlink(E) xfrm_user(E) xfrm_algo(E) nft_counter(E) xt_addrtype(E) nft_compat(E) nft_chain_nat(E) nf_nat(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) br_netfilter(E) bridge(E) stp(E) llc(E) vhost_net(E) tun(E) vhost(E) macvtap(E) macvlan(E) tap(E) softdog(E) nf_tables(E) nfnetlink(E) overlay(E) cpufreq_conservative(E) cpufreq_userspace(E) cpufreq_powersave(E) btusb(E) edac_mce_amd(E) btrtl(E) btbcm(E) kvm_amd(E) btintel(E) iwlmvm(E) kvm(E) mac80211(E) bluetooth(E) libarc4(E) crct10dif_pclmul(E) nls_ascii(E) drbg(E) crc32_pclmul(E) nls_cp437(E) iwlwifi(E) ansi_cprng(E) ghash_clmulni_intel(E) vfat(E) efi_pstore(E) fat(E) snd_pcm(E) ecdh_generic(E) aesni_intel(E) snd_timer(E) cfg80211(E) sp5100_tco(E) ecc(E) snd(E) aes_x86_64(E) crypto_simd(E) soundcore(E) cryptd(E) glue_helper(E) efivars(E) evdev(E) wmi_bmof(E) pcspkr(E) k10temp(E) watchdog(E)
[48505.231156] rfkill(E) sg(E) ccp(E) rng_core(E) button(E) acpi_cpufreq(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid0(E) multipath(E) linear(E) vfio_pci(E) irqbypass(E) vfio_virqfd(E) vfio_iommu_type1(E) vfio(E) raid1(E) md_mod(E) sd_mod(E) crc32c_intel(E) ahci(E) xhci_pci(E) libahci(E) r8169(E) i2c_piix4(E) xhci_hcd(E) realtek(E) libata(E) libphy(E) usbcore(E) scsi_mod(E) wmi(E) gpio_amdpt(E) gpio_generic(E)
[48505.231183] CPU: 10 PID: 26679 Comm: qemu-system-x86 Tainted: G W E 5.3.7-navi #1
[48505.231184] Hardware name: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI/AB350N-Gaming WIFI-CF, BIOS F25 01/16/2019
[48505.231187] RIP: 0010:__domain_flush_pages.cold.44+0xc/0x13
[48505.231190] Code: ff b8 fb ff ff ff e9 7e ab ff ff 48 c7 c7 d8 39 26 b2 e8 f8 9b ba ff 0f 0b e9 8f b4 ff ff 48 c7 c7 d8 39 26 b2 e8 e5 9b ba ff <0f> 0b e9 ab c8 ff ff 48 89 1c 24 48 89 d3 48 c7 c7 30 c5 2e b2 e8
[48505.231191] RSP: 0018:ffffb5f840a1fc70 EFLAGS: 00010246
[48505.231193] RAX: 0000000000000024 RBX: ffff9c1c3e79fa10 RCX: 0000000000000000
[48505.231194] RDX: 0000000000000000 RSI: ffff9c1f7ec97688 RDI: ffff9c1f7ec97688
[48505.231195] RBP: ffffb5f840a1fcd8 R08: 0000000000002647 R09: 0000000000000004
[48505.231196] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9c1f7b412000
[48505.231197] R13: 00000000fffffffb R14: ffff9c1c3e79fa10 R15: 7fffffffffffffff
[48505.231199] FS: 00007f30ecf2d3c0(0000) GS:ffff9c1f7ec80000(0000) knlGS:0000000000000000
[48505.231201] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[48505.231202] CR2: 000056520fe7b3c0 CR3: 000000000a1da000 CR4: 00000000003406e0
[48505.231203] Call Trace:
[48505.231208] amd_iommu_flush_iotlb_all+0x23/0x30
[48505.231212] vfio_sync_unpin.isra.18+0x2f/0xd0 [vfio_iommu_type1]
[48505.231216] vfio_unmap_unpin+0x315/0x350 [vfio_iommu_type1]
[48505.231220] vfio_remove_dma+0x19/0x60 [vfio_iommu_type1]
[48505.231223] vfio_iommu_type1_ioctl+0x624/0x7bb [vfio_iommu_type1]
[48505.231227] do_vfs_ioctl+0xa4/0x630
[48505.231231] ksys_ioctl+0x60/0x90
[48505.231233] __x64_sys_ioctl+0x16/0x20
[48505.231236] do_syscall_64+0x55/0x110
[48505.231240] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[48505.231242] RIP: 0033:0x7f30eef6c427
[48505.231244] Code: 00 00 90 48 8b 05 69 aa 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 39 aa 0c 00 f7 d8 64 89 01 48
[48505.231245] RSP: 002b:00007fffa9f6b848 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[48505.231247] RAX: ffffffffffffffda RBX: 00007fffa9f6b930 RCX: 00007f30eef6c427
[48505.231248] RDX: 00007fffa9f6b850 RSI: 0000000000003b72 RDI: 0000000000000017
[48505.231249] RBP: 0000000000000000 R08: 0000000080000000 R09: 000000007fffffff
[48505.231250] R10: 0000000000000000 R11: 0000000000000246 R12: 00005581576d2ab0
[48505.231251] R13: 0000000080000000 R14: 0000000080000000 R15: 0000000000000000
[48505.231254] ---[ end trace 3532ad8f65694501 ]---
[48505.434060] AMD-Vi: Command buffer timeout
[48505.434112] ------------[ cut here ]------------
[48505.434136] WARNING: CPU: 0 PID: 0 at drivers/iommu/amd_iommu.c:1272 __domain_flush_pages.cold.44+0xc/0x13
[48505.434141] Modules linked in: hid_generic(E) usbhid(E) hid(E) xt_nat(E) xt_tcpudp(E) veth(E) xt_conntrack(E) xt_MASQUERADE(E) nf_conntrack_netlink(E) xfrm_user(E) xfrm_algo(E) nft_counter(E) xt_addrtype(E) nft_compat(E) nft_chain_nat(E) nf_nat(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) br_netfilter(E) bridge(E) stp(E) llc(E) vhost_net(E) tun(E) vhost(E) macvtap(E) macvlan(E) tap(E) softdog(E) nf_tables(E) nfnetlink(E) overlay(E) cpufreq_conservative(E) cpufreq_userspace(E) cpufreq_powersave(E) btusb(E) edac_mce_amd(E) btrtl(E) btbcm(E) kvm_amd(E) btintel(E) iwlmvm(E) kvm(E) mac80211(E) bluetooth(E) libarc4(E) crct10dif_pclmul(E) nls_ascii(E) drbg(E) crc32_pclmul(E) nls_cp437(E) iwlwifi(E) ansi_cprng(E) ghash_clmulni_intel(E) vfat(E) efi_pstore(E) fat(E) snd_pcm(E) ecdh_generic(E) aesni_intel(E) snd_timer(E) cfg80211(E) sp5100_tco(E) ecc(E) snd(E) aes_x86_64(E) crypto_simd(E) soundcore(E) cryptd(E) glue_helper(E) efivars(E) evdev(E) wmi_bmof(E) pcspkr(E) k10temp(E) watchdog(E)
[48505.434193] rfkill(E) sg(E) ccp(E) rng_core(E) button(E) acpi_cpufreq(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) btrfs(E) zstd_decompress(E) zstd_compress(E) raid10(E) raid456(E) async_raid6_recov(E) async_memcpy(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E) raid0(E) multipath(E) linear(E) vfio_pci(E) irqbypass(E) vfio_virqfd(E) vfio_iommu_type1(E) vfio(E) raid1(E) md_mod(E) sd_mod(E) crc32c_intel(E) ahci(E) xhci_pci(E) libahci(E) r8169(E) i2c_piix4(E) xhci_hcd(E) realtek(E) libata(E) libphy(E) usbcore(E) scsi_mod(E) wmi(E) gpio_amdpt(E) gpio_generic(E)
[48505.434232] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W E 5.3.7-navi #1
[48505.434233] Hardware name: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI/AB350N-Gaming WIFI-CF, BIOS F25 01/16/2019
[48505.434237] RIP: 0010:__domain_flush_pages.cold.44+0xc/0x13
[48505.434240] Code: ff b8 fb ff ff ff e9 7e ab ff ff 48 c7 c7 d8 39 26 b2 e8 f8 9b ba ff 0f 0b e9 8f b4 ff ff 48 c7 c7 d8 39 26 b2 e8 e5 9b ba ff <0f> 0b e9 ab c8 ff ff 48 89 1c 24 48 89 d3 48 c7 c7 30 c5 2e b2 e8
[48505.434242] RSP: 0018:ffffb5f840003df0 EFLAGS: 00010246
[48505.434245] RAX: 0000000000000024 RBX: ffff9c1f70525010 RCX: 0000000000000000
[48505.434246] RDX: 0000000000000000 RSI: ffff9c1f7ea17688 RDI: ffff9c1f7ea17688
[48505.434247] RBP: ffffb5f840003e58 R08: 000000000000266d R09: 0000000000000004
[48505.434248] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9c1f70525860
[48505.434250] R13: 00000000fffffffb R14: ffff9c1f70525010 R15: 7fffffffffffffff
[48505.434252] FS: 0000000000000000(0000) GS:ffff9c1f7ea00000(0000) knlGS:0000000000000000
[48505.434253] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[48505.434255] CR2: 00007f7a4fffdff8 CR3: 000000043fb6a000 CR4: 00000000003406f0
[48505.434256] Call Trace:
[48505.434259] <IRQ>
[48505.434266] ? cpumask_next_and+0x19/0x20
[48505.434270] ? load_balance+0x144/0xb20
[48505.434273] ? fq_ring_free+0xd0/0xd0
[48505.434276] iova_domain_flush_tlb+0x23/0x30
[48505.434280] iova_domain_flush+0x1a/0x30
[48505.434283] fq_flush_timeout+0x2d/0x90
[48505.434287] ? fq_ring_free+0xd0/0xd0
[48505.434293] call_timer_fn+0x2d/0x130
[48505.434296] run_timer_softirq+0x19e/0x410
[48505.434298] ? __hrtimer_run_queues+0x130/0x280
[48505.434301] ? ktime_get+0x3a/0xa0
[48505.434305] __do_softirq+0xdf/0x2e5
[48505.434310] irq_exit+0xa3/0xb0
[48505.434313] smp_apic_timer_interrupt+0x74/0x130
[48505.434315] apic_timer_interrupt+0xf/0x20
[48505.434317] </IRQ>
[48505.434321] RIP: 0010:cpuidle_enter_state+0xbc/0x450
[48505.434324] Code: e8 79 6f ae ff 80 7c 24 13 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 67 03 00 00 31 ff e8 2b 92 b4 ff fb 66 0f 1f 44 00 00 <45> 85 e4 0f 89 d1 01 00 00 c7 45 10 00 00 00 00 48 83 c4 18 44 89
[48505.434325] RSP: 0018:ffffffffb2403e60 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
[48505.434328] RAX: ffff9c1f7ea2a580 RBX: ffffffffb24bc680 RCX: 000000000000001f
[48505.434329] RDX: 00002c1d7c356ba1 RSI: 0000000028133e14 RDI: 0000000000000000
[48505.434330] RBP: ffff9c1f6fcc4000 R08: 0000000000000002 R09: 0000000000029e00
[48505.434331] R10: 00008cfcfa1870a0 R11: ffff9c1f7ea294e4 R12: 0000000000000002
[48505.434332] R13: ffffffffb24bc758 R14: 0000000000000002 R15: 00000000d6d2f8aa
[48505.434338] cpuidle_enter+0x29/0x40
[48505.434342] do_idle+0x228/0x270
[48505.434345] cpu_startup_entry+0x19/0x20
[48505.434350] start_kernel+0x558/0x576
[48505.434355] secondary_startup_64+0xa4/0xb0
[48505.434359] ---[ end trace 3532ad8f65694502 ]---
EDIT: Great now I can’t even boot debian anymore, hope I can fix it in a chroot 
Since I switched to fedora 31, I made a small dirty Dockerfile to compile the Fedora-Kernel with the navi patch applied:
FROM fedora:31
ENV KVER kernel-5.3.7-301.fc31
RUN sudo dnf -y install fedpkg fedora-packager rpmdevtools ncurses-devel pesign
RUN rpmdev-setuptree && cd ~ && koji download-build --arch=src $KVER.src.rpm
RUN useradd -s /sbin/nologin mockbuild && rpm -Uvh ~/$KVER.src.rpm && cd ~/rpmbuild/SOURCES && curl -o navi.patch https://pastebin.com/raw/aKkLytWP
RUN cd ~/rpmbuild/SPECS/ && sudo dnf -y builddep kernel.spec
RUN cd ~/rpmbuild/SPECS/ && sed -i -e 's/# define buildid .local/%define buildid .navi/g' kernel.spec && sed -i "s/# END OF PATCH DEFINITIONS/# END OF PATCH DEFINITIONS\nPatch9001: navi.patch/" kernel.spec
RUN cd ~/rpmbuild/SPECS/ && rpmbuild -bb --without debug --target=x86_64 kernel.spec
ENTRYPOINT cp ~/rpmbuild/RPMS/x86_64/kernel* /output
Works fine with bildah too! Just use podman build --tag sth/fedora-navi-sth -v $PWD/out:/output and let it run in a screen or whatever
EDIT: And don’t forget to remove the old image 
:
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/local/kernel-patch latest 299b74aaaae3 21 minutes ago 23.5 GB
docker.io/library/fedora 31 f0858ad3febd 6 days ago 201 MB
1 Like
Does this mean the patch works for you on Fedora 31? Because I’m also using Fedora 31 and on every Kernel I tried, up to 5.4-rc6 I get the same Error when starting a VM for the second time.
But there is even more amiss here as I can’t unbind the device from the amdgpu driver as well.
No sorry I didn’t even try it yet. I just compiled the kernel didn’t have time for the rest…