Description of problem: Installed secondary video card (Diamond HD 5450) with my primary (Power Color RX 560) and having them both in prevents booting with this error. Having only a single one in seems to function OK. Error in dmesg was: drm:radeon_get_bios [radeon] *ERROR* ACPI VFCT table present but broken (too short #2) I added the 5450 to my list for vfio to grab but it didn't make a difference (I didn't rebuild initramfs/dracut yet to see if that makes a difference). I'm assuming this is an issue related to the one you can find reported by netkas on the phoronix forums where 2 VBIOSes don't play well together but obviously there's another issue when using these cards. I've been able to use an ASUS HD7770 with the Power Color RX560 without issue. Perhaps those both use amdgpu while the 5450 wants to use the radeon driver? I've not tried blacklisting radeon either. Additional info: reporter: libreport-2.9.3 WARNING: CPU: 10 PID: 1426 at drivers/gpu/drm/drm_mode_config.c:473 drm_mode_config_cleanup+0x2bb/0x2d0 [drm] Modules linked in: xt_CHECKSUM tun ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep sunrpc vfat fat arc4 iwlmvm amd64_edac_mod wmi_bmof mxm_wmi edac_mce_amd mac80211 kvm_amd kvm snd_hda_codec_realtek snd_hda_codec_generic iwlwifi snd_hda_codec_hdmi snd_usb_audio btusb btrtl snd_hda_intel snd_usbmidi_lib btbcm snd_hda_codec btintel snd_rawmidi cfg80211 bluetooth snd_hda_core joydev snd_seq snd_hwdep snd_seq_device sp5100_tco snd_pcm i2c_piix4 cdc_acm k10temp ecdh_generic snd_timer snd rfkill soundcore gpio_amdpt wmi pcc_cpufreq gpio_generic pinctrl_amd acpi_cpufreq dm_crypt amdkfd amd_iommu_v2 amdgpu radeon chash gpu_sched drm_kms_helper ttm igb drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel dca ccp i2c_algo_bit nvme nvme_core vfio_pci irqbypass vfio_virqfd vfio_iommu_type1 vfio i2c_dev CPU: 10 PID: 1426 Comm: libvirtd Not tainted 4.18.9-100.fc27.x86_64 #1 Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS P3.20 09/08/2017 RIP: 0010:drm_mode_config_cleanup+0x2bb/0x2d0 [drm] Code: ff ff eb 0c 48 8b 70 48 48 89 df e8 0f f5 ff ff 48 89 e7 e8 a7 a3 ff ff 48 85 c0 75 e7 48 89 e7 e8 9a 95 ff ff e9 f8 fd ff ff <0f> 0b e9 ef fe ff ff 0f 0b eb 9a e8 65 2b b3 fb 0f 1f 44 00 00 0f RSP: 0018:ffffb425cbd3fcd0 EFLAGS: 00010206 RAX: ffff92fed45e8508 RBX: ffff92fedab64bf8 RCX: 000000008020001e RDX: ffff92fedab64c20 RSI: 0000000000000001 RDI: ffff92fedab64bf8 RBP: ffff92fedab64800 R08: 0000000000000000 R09: ffffffffc057ab00 R10: ffff92fed380e300 R11: 0000000000000001 R12: ffff92fedab64ac8 R13: ffffffffc07c31d0 R14: 0000000000000060 R15: ffff92fed6cb53a0 FS: 00007f9ff17fa700(0000) GS:ffff92fede880000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fa025bfb4b0 CR3: 00000008034a6000 CR4: 00000000003406e0 Call Trace: radeon_modeset_fini+0x8d/0xa0 [radeon] radeon_driver_unload_kms+0x36/0x70 [radeon] drm_dev_unregister+0x3f/0xd0 [drm] drm_put_dev+0x27/0x50 [drm] pci_device_remove+0x3b/0xb0 device_release_driver_internal+0x182/0x250 unbind_store+0xb4/0x180 kernfs_fop_write+0x10f/0x190 __vfs_write+0x36/0x1a0 ? selinux_file_permission+0x11d/0x130 ? security_file_permission+0x2a/0xb0 vfs_write+0xad/0x1a0 ksys_write+0x52/0xc0 do_syscall_64+0x5b/0x160 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fa0218d5cdb Code: 53 48 89 d5 48 89 f3 48 83 ec 18 48 89 7c 24 08 e8 5a fd ff ff 48 89 ea 41 89 c0 48 89 de 48 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 90 fd ff ff 48 RSP: 002b:00007f9ff17f9680 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f9fb41fbc34 RCX: 00007fa0218d5cdb RDX: 000000000000000c RSI: 00007f9fb41fbc34 RDI: 0000000000000019 RBP: 000000000000000c R08: 0000000000000000 R09: 7665642f6963702f R10: 0000000000000000 R11: 0000000000000293 R12: 00007f9fb41fbc34 R13: 0000000000000000 R14: 0000000000000019 R15: 00007fa0258e2e3b
Created attachment 1488465 [details] File: dmesg
Recreated initramfs & vfio picks up the 5450 now. Attempting to use the 5450 with a VM results in the following in dmesg: [ 102.768620] vfio-pci 0000:0f:00.0: enabling device (0002 -> 0003) [ 102.783908] vfio-pci 0000:0f:00.1: enabling device (0000 -> 0002) [ 104.030887] vfio_bar_restore: 0000:0f:00.1 reset recovery - restoring bars [ 104.755739] vfio-pci 0000:0f:00.1: timed out waiting for pending transaction; performing function level reset anyway [ 105.955932] vfio-pci 0000:0f:00.1: not ready 1023ms after FLR; waiting [ 107.043921] vfio-pci 0000:0f:00.1: not ready 2047ms after FLR; waiting These continue until vfio gives up and performs another FLR. I'm including this in case it's of value to fixing the original issue; if not I'll file a separate bug (or return the 5450).
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.