You are not logged in.

Pages: 1

#1 2021-08-09 20:05:37

PropagandaPanda
Member
Registered: 2021-08-09
Posts: 4

Kernel errors on binding and unbinding radeon driver to AMD R9 290X

First post, please be gentle.

I am trying to pass a GPU through to a Windows VM and after weeks of digging, I think I have isolated the problem.

My GPU is an AMD R9 290X, I am loading and binding vfio-pci at boot to it so that I can pass it to the VM and it works like that.
Now, I would like to use the GPU on Arch too, so I want to unbind it from vfio-pci and bind it to the radeon driver.
That still works, but when I try to unbind it from that, I get a kernel stack trace and on every subsequent bind/unbind there are errors/stacktraces.

This is the journalctl output from the first unbind from radeon:

Aug 09 21:11:53 ArchDev kernel: [drm] radeon: finishing device.
Aug 09 21:11:53 ArchDev kernel: ------------[ cut here ]------------
Aug 09 21:11:53 ArchDev kernel: Memory manager not clean during takedown.
Aug 09 21:11:53 ArchDev kernel: WARNING: CPU: 7 PID: 1264 at drivers/gpu/drm/drm_mm.c:998 drm_mm_takedown+0x1f/0x30 [d>
Aug 09 21:11:53 ArchDev kernel: Modules linked in: uinput rfcomm snd_seq_dummy snd_hrtimer snd_seq xt_CHECKSUM xt_MASQ>
Aug 09 21:11:53 ArchDev kernel:  iTCO_wdt vfat snd_intel_dspcfg intel_pmc_bxt snd_intel_sdw_acpi at24 iTCO_vendor_supp>
Aug 09 21:11:53 ArchDev kernel: CPU: 7 PID: 1264 Comm: bash Tainted: G           OE     5.13.9-arch1-1 #1
Aug 09 21:11:53 ArchDev kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H97 Killer, BIOS P2.60 03>
Aug 09 21:11:53 ArchDev kernel: RIP: 0010:drm_mm_takedown+0x1f/0x30 [drm]
Aug 09 21:11:53 ArchDev kernel: Code: 48 e9 6a ff ff ff 0f 1f 44 00 00 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 f8>
Aug 09 21:11:53 ArchDev kernel: RSP: 0018:ffffa58b013afcb0 EFLAGS: 00010282
Aug 09 21:11:53 ArchDev kernel: RAX: 0000000000000000 RBX: ffff8f0912d906e8 RCX: 0000000000000027
Aug 09 21:11:53 ArchDev kernel: RDX: ffff8f0c2ffd8728 RSI: 0000000000000001 RDI: ffff8f0c2ffd8720
Aug 09 21:11:53 ArchDev kernel: RBP: ffff8f090691e800 R08: 0000000000000000 R09: ffffa58b013afae0
Aug 09 21:11:53 ArchDev kernel: R10: ffffa58b013afad8 R11: ffffffff932ccde8 R12: 0000000000000000
Aug 09 21:11:53 ArchDev kernel: R13: 0000000000000001 R14: ffff8f090691e958 R15: ffff8f09046b3f20
Aug 09 21:11:53 ArchDev kernel: FS:  00007f443865fb80(0000) GS:ffff8f0c2ffc0000(0000) knlGS:0000000000000000
Aug 09 21:11:53 ArchDev kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 09 21:11:53 ArchDev kernel: CR2: 000055f7bb818f20 CR3: 000000010252a005 CR4: 00000000001706e0
Aug 09 21:11:53 ArchDev kernel: Call Trace:
Aug 09 21:11:53 ArchDev kernel:  ttm_range_man_fini+0x90/0x100 [ttm]
Aug 09 21:11:53 ArchDev kernel:  radeon_ttm_fini+0xc2/0x100 [radeon]
Aug 09 21:11:53 ArchDev kernel:  radeon_bo_fini+0xe/0x30 [radeon]
Aug 09 21:11:53 ArchDev kernel:  cik_fini+0x144/0x170 [radeon]
Aug 09 21:11:53 ArchDev kernel:  radeon_device_fini+0x37/0xf4 [radeon]
Aug 09 21:11:53 ArchDev kernel:  radeon_driver_unload_kms+0x3e/0xa0 [radeon]
Aug 09 21:11:53 ArchDev kernel:  drm_dev_unregister+0x5c/0x90 [drm]
Aug 09 21:11:53 ArchDev kernel:  drm_put_dev+0x27/0x80 [drm]
Aug 09 21:11:53 ArchDev kernel:  pci_device_remove+0x3b/0xa0
Aug 09 21:11:53 ArchDev kernel:  __device_release_driver+0x17a/0x230
Aug 09 21:11:53 ArchDev kernel:  device_driver_detach+0x3c/0xa0
Aug 09 21:11:53 ArchDev kernel:  unbind_store+0x113/0x130
Aug 09 21:11:53 ArchDev kernel:  kernfs_fop_write_iter+0x11c/0x1b0
Aug 09 21:11:53 ArchDev kernel:  new_sync_write+0x159/0x1f0
Aug 09 21:11:53 ArchDev kernel:  vfs_write+0x1db/0x270
Aug 09 21:11:53 ArchDev kernel:  ksys_write+0x67/0xe0
Aug 09 21:11:53 ArchDev kernel:  do_syscall_64+0x40/0x80
Aug 09 21:11:53 ArchDev kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Aug 09 21:11:53 ArchDev kernel: RIP: 0033:0x7f44387c0907
Aug 09 21:11:53 ArchDev kernel: Code: 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25>
Aug 09 21:11:53 ArchDev kernel: RSP: 002b:00007fff2b43a898 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
Aug 09 21:11:53 ArchDev kernel: RAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007f44387c0907
Aug 09 21:11:53 ArchDev kernel: RDX: 000000000000000d RSI: 0000561f60ec30b0 RDI: 0000000000000001
Aug 09 21:11:53 ArchDev kernel: RBP: 0000561f60ec30b0 R08: 000000000000000a R09: 00007f44388564e0
Aug 09 21:11:53 ArchDev kernel: R10: 00007f44388563e0 R11: 0000000000000246 R12: 000000000000000d
Aug 09 21:11:53 ArchDev kernel: R13: 00007f4438892520 R14: 000000000000000d R15: 00007f4438892700
Aug 09 21:11:53 ArchDev kernel: ---[ end trace d1118fc432ee7c38 ]---
Aug 09 21:11:53 ArchDev kernel: [drm] radeon: ttm finalized

If you need more info like loaded modules or boot parameters, I'll comply asap.

Edit: Oh, well, maybe you need the errors on binding again aswell smile
This is dmesg output from right after binding. By the way, I am binding and unbinding with

[root@ArchDev max]# echo "0000:01:00.0" > /sys/bus/pci/drivers/radeon/bind
[root@ArchDev max]# echo "0000:01:00.0" > /sys/bus/pci/devices/0000\:01\:00.0/driver/unbind
[root@ArchDev max]# echo "0000:01:00.0" > /sys/bus/pci/drivers/vfio-pci/bind
[root@ArchDev max]# echo "0000:01:00.0" > /sys/bus/pci/devices/0000\:01\:00.0/driver/unbind
[root@ArchDev max]# echo "0000:01:00.0" > /sys/bus/pci/drivers/radeon/bind

Yes, I am root, but only because sudo just doesn't work for some reason(system files not allowed?).

[ 3622.301666] [drm] initializing kernel modesetting (HAWAII 0x1002:0x67B0 0x174B:0xE282 0x00).
[ 3622.301728] [drm] doorbell mmio base: 0xE0000000
[ 3622.301731] [drm] doorbell mmio size: 8388608
[ 3622.627525] ATOM BIOS: C67101
[ 3622.627583] radeon 0000:01:00.0: VRAM: 4096M 0x0000000000000000 - 0x00000000FFFFFFFF (4096M used)
[ 3622.627585] radeon 0000:01:00.0: GTT: 2048M 0x0000000100000000 - 0x000000017FFFFFFF
[ 3622.627588] [drm] Detected VRAM RAM=4096M, BAR=256M
[ 3622.627589] [drm] RAM width 512bits DDR
[ 3622.627594] debugfs: File 'page_pool' in directory 'ttm' already present!
[ 3622.627595] debugfs: File 'page_pool_shrink' in directory 'ttm' already present!
[ 3622.627597] debugfs: File 'buffer_objects' in directory 'ttm' already present!
[ 3622.627602] [drm] radeon: 4096M of VRAM memory ready
[ 3622.627603] [drm] radeon: 2048M of GTT memory ready.
[ 3622.627607] [drm] Loading hawaii Microcode
[ 3622.627613] [drm] Internal thermal controller with fan control
[ 3622.797778] [drm:ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed
[ 3622.797812] [drm:radeon_pm_init [radeon]] *ERROR* radeon: dpm initialization failed
[ 3622.797899] [drm] Found UVD firmware Version: 1.64 Family ID: 9
[ 3622.798197] [drm] Found VCE firmware/feedback version 40.2.2 / 15!
[ 3622.798203] [drm] GART: num cpu pages 524288, num gpu pages 524288
[ 3622.799066] [drm] PCIE gen 3 link speeds already enabled
[ 3622.804942] [drm] PCIE GART of 2048M enabled (table at 0x000000000030E000).
[ 3622.805043] radeon 0000:01:00.0: WB enabled
[ 3622.805050] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000100000c00
[ 3622.805051] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000100000c04
[ 3622.805052] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000100000c08
[ 3622.805053] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000100000c0c
[ 3622.805054] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000100000c10
[ 3622.805409] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000078d30
[ 3622.805547] radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000100000c18
[ 3622.805548] radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000100000c1c
[ 3622.806182] radeon 0000:01:00.0: radeon: using MSI.
[ 3622.806199] [drm] radeon: irq initialized.
[ 3622.808482] [drm] ring test on 0 succeeded in 4 usecs
[ 3622.808554] [drm] ring test on 1 succeeded in 3 usecs
[ 3622.808569] [drm] ring test on 2 succeeded in 3 usecs
[ 3622.808735] [drm] ring test on 3 succeeded in 4 usecs
[ 3622.808743] [drm] ring test on 4 succeeded in 4 usecs
[ 3622.854781] [drm] ring test on 5 succeeded in 2 usecs
[ 3622.874794] [drm] UVD initialized successfully.
[ 3622.978637] [drm] ring test on 6 succeeded in 2279 usecs
[ 3622.978648] [drm] ring test on 7 succeeded in 4 usecs
[ 3622.978648] [drm] VCE initialized successfully.
[ 3622.979933] [drm] ib test on ring 0 succeeded in 0 usecs
[ 3622.980068] [drm] ib test on ring 1 succeeded in 0 usecs
[ 3622.980200] [drm] ib test on ring 2 succeeded in 0 usecs
[ 3622.980333] [drm] ib test on ring 3 succeeded in 0 usecs
[ 3622.980466] [drm] ib test on ring 4 succeeded in 0 usecs
[ 3623.507919] [drm] ib test on ring 5 succeeded
[ 3623.528918] [drm] ib test on ring 6 succeeded
[ 3623.529755] [drm] ib test on ring 7 succeeded
[ 3623.530448] [drm] Radeon Display Connectors
[ 3623.530451] [drm] Connector 0:
[ 3623.530453] [drm]   DP-1
[ 3623.530454] [drm]   HPD2
[ 3623.530455] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
[ 3623.530458] [drm]   Encoders:
[ 3623.530459] [drm]     DFP1: INTERNAL_UNIPHY2
[ 3623.530461] [drm] Connector 1:
[ 3623.530462] [drm]   HDMI-A-3
[ 3623.530463] [drm]   HPD3
[ 3623.530464] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c
[ 3623.530466] [drm]   Encoders:
[ 3623.530467] [drm]     DFP2: INTERNAL_UNIPHY2
[ 3623.530468] [drm] Connector 2:
[ 3623.530469] [drm]   DVI-D-1
[ 3623.530470] [drm]   HPD1
[ 3623.530471] [drm]   DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c
[ 3623.530474] [drm]   Encoders:
[ 3623.530475] [drm]     DFP3: INTERNAL_UNIPHY1
[ 3623.530476] [drm] Connector 3:
[ 3623.530477] [drm]   DVI-D-2
[ 3623.530478] [drm]   HPD6
[ 3623.530478] [drm]   DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 0x658c 0x658c
[ 3623.530481] [drm]   Encoders:
[ 3623.530482] [drm]     DFP4: INTERNAL_UNIPHY
[ 3623.620394] [drm] fb mappable at 0xD0731000
[ 3623.620397] [drm] vram apper at 0xD0000000
[ 3623.620397] [drm] size 9216000
[ 3623.620398] [drm] fb depth is 24
[ 3623.620398] [drm]    pitch is 7680
[ 3623.620547] radeon 0000:01:00.0: [drm] fb1: radeondrmfb frame buffer device
[ 3623.620571] [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor 1

I just have not been able to figure things out. It seems to have something to do with drm, but I am a pretty new GNU/Linux user and simply do not understand kernel and module internals.
Thanks in advance, and yes, I have read the manuals, google and forums as best as I could smile

Last edited by PropagandaPanda (2021-08-09 20:10:54)

Offline

#2 2021-08-10 11:38:48

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,085

Re: Kernel errors on binding and unbinding radeon driver to AMD R9 290X

Welcome to archlinux forums.

You have read https://wiki.archlinux.org/title/PCI_pa … h_via_OVMF and are aware of

However, due to their size and complexity, GPU drivers do not tend to support dynamic rebinding very well, so you cannot just have some GPU you use on the host be transparently passed to a VM without having both drivers conflict with each other. Because of this, it is generally advised to bind those placeholder drivers manually before starting the VM, in order to stop other drivers from attempting to claim it.

?

Your bind/unbind commands look like they only deal with one device and that may be the problem .
Typically modern videocards also need to bind/unbind atleast their audio part.

Please post 

$ lspci -nnk # (run as user to avoid Too Much Information)

Also journalctl -b (as root) and the output of the script from Ensuring that the groups are valid

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2021-08-10 16:16:44

PropagandaPanda
Member
Registered: 2021-08-09
Posts: 4

Re: Kernel errors on binding and unbinding radeon driver to AMD R9 290X

Thank you for your answer!

Yes, I have read that page, it was a real lifesaver so far. The Arch wiki in general is just awesome!

My problem is not that closely related to VMs since I get those errors when (un-)binding manually. I load the drivers early during boot and only when the system is fully online, I try to unbind and rebind.

I have tried with unbinding the HDMI audio as well and it did not make a difference for me. The same error occurs, but only on the video driver switch.

lspci -nnk output:

00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
	Subsystem: ASRock Incorporation Device [1849:0c00]
	Kernel driver in use: hsw_uncore
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
	Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)
	Subsystem: ASRock Incorporation Device [1849:0412]
	Kernel driver in use: i915
	Kernel modules: i915
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
	Subsystem: ASRock Incorporation Device [1849:0c0c]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1]
	Subsystem: ASRock Incorporation Device [1849:8cb1]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba]
	Subsystem: ASRock Incorporation Device [1849:8cba]
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 [8086:8cad]
	Subsystem: ASRock Incorporation Device [1849:8cad]
	Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0]
	Subsystem: ASRock Incorporation Device [1849:1151]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0)
	Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev d0)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 [8086:8c96] (rev d0)
	Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 [8086:8ca6]
	Subsystem: ASRock Incorporation Device [1849:8ca6]
	Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation H97 Chipset LPC Controller [8086:8cc6]
	Subsystem: ASRock Incorporation Device [1849:8cc6]
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] [8086:8c82]
	Subsystem: ASRock Incorporation Device [1849:8c82]
	Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family SMBus Controller [8086:8ca2]
	Subsystem: ASRock Incorporation Device [1849:8ca2]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] [1002:67b0]
	Subsystem: PC Partner Limited / Sapphire Technology Vapor-X R9 290X Tri-X OC [174b:e282]
	Kernel driver in use: vfio-pci
	Kernel modules: radeon, amdgpu
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X] [1002:aac8]
	Subsystem: PC Partner Limited / Sapphire Technology Device [174b:aac8]
	Kernel driver in use: vfio-pci
	Kernel modules: snd_hda_intel
02:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01)
	Subsystem: Phison Electronics Corporation E12 NVMe Controller [1987:5012]
	Kernel driver in use: nvme
03:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 03)
05:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 10)
	Subsystem: ASRock Incorporation Device [1849:e091]
	Kernel driver in use: alx
	Kernel modules: alx

journalctl -b output: http://ix.io/3vzf

IOMMU groups:

IOMMU Group 0:
	00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
IOMMU Group 1:
	00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
	01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] [1002:67b0]
	01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X] [1002:aac8]
IOMMU Group 2:
	00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)
IOMMU Group 3:
	00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
IOMMU Group 4:
	00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1]
IOMMU Group 5:
	00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba]
IOMMU Group 6:
	00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 [8086:8cad]
IOMMU Group 7:
	00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0]
IOMMU Group 8:
	00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0)
IOMMU Group 9:
	00:1c.2 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev d0)
	03:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 03)
IOMMU Group 10:
	00:1c.3 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 [8086:8c96] (rev d0)
IOMMU Group 11:
	00:1d.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 [8086:8ca6]
IOMMU Group 12:
	00:1f.0 ISA bridge [0601]: Intel Corporation H97 Chipset LPC Controller [8086:8cc6]
	00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] [8086:8c82]
	00:1f.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family SMBus Controller [8086:8ca2]
IOMMU Group 13:
	02:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01)
IOMMU Group 14:
	05:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 10)

Thanks again!

Last edited by PropagandaPanda (2021-08-10 16:17:33)

Offline

#4 2021-08-13 14:16:05

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,085

Re: Kernel errors on binding and unbinding radeon driver to AMD R9 290X

Aug 10 09:59:37 ArchDev kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=68441c90-4862-4222-8511-199021e19e79 rw loglevel=3 quiet intel_iommu=on amdgpu.cik_support=0 radeon.cik_support=1 vfio-pci.ids=1002:67b0,1002:aac8

Usually people set amdgpu.cik_support to 1 and radeon.cik_support to 0 so they can use the amdgpu kernel module instead of radeon.
Have you tried with the amdgpu kernel module ?



Aug 10 09:59:37 ArchDev kernel: DMAR: No ATSR found
Aug 10 09:59:37 ArchDev kernel: DMAR: No SATC found
Aug 10 09:59:37 ArchDev kernel: DMAR: IOMMU feature pgsel_inv inconsistent
Aug 10 09:59:37 ArchDev kernel: DMAR: IOMMU feature sc_support inconsistent
Aug 10 09:59:37 ArchDev kernel: DMAR: IOMMU feature pass_through inconsistent

No idea about the first 2 lines, but the last 3 suggest low level problems .


Aug 10 09:59:37 ArchDev kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./H97 Killer, BIOS P2.60 03/07/2018

Is Bios 2.60 the latest firmware version available for your motherboard ?

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Pages: 1

Board footer

Powered by FluxBB