https://bugzilla.kernel.org/show_bug.cgi?id=201527
Andrej Podzimek (and...@podzimek.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |and...@podzimek.org
--- Comment #19 from Andrej Podzimek (and...@podzimek.org) ---
I have a very similar resource allocation issue on a completely different
platform (ASRock Creator X570, Ryzen 3950X, Razer Core X Chroma, NVidia Quadro
P5000). Here are my posts on egpu.io with dmesg and other details:
https://egpu.io/forums/postid/90573/
https://egpu.io/forums/postid/90608/
The kernel command line magic I’ve been using:
pcie_ports=native
pci=assign-busses,hpbussize=0x33,realloc,hpmmiosize=128M,hpmmioprefsize=16G
The number of errors in dmesg depends on hpmmiosize and hpmmioprefsize like
this (based on what I tried, which is in no way exhaustive):
256M / 64G: A huge number of errors affecting multiple BARs, even before the
eGPU connection: https://pastebin.com/kcdHADw6 The eGPU works though.
128M / 16G: BAR 15 has errors during boot, BAR 13 has errors upon eGPU
connection. The eGPU works.
128M / 512M: Exactly the same number and type of errors as above. The eGPU
works.
128M / 256M: No I/O resource errors. But the eGPU doesn’t work; initialization
fails in almost the same way as reported here:
https://bbs.archlinux.org/viewtopic.php?id=261303 (Almost as if the pci= tweaks
on the kernel command line had no effect.)
(By "eGPU works" I mean that it can run Folding@Home. (I haven’t tested it in
other ways.) There is (I guess) a performance penalty due to the missing MMIO
resources.)
Unfortunately I have no clue which of the errors are benign and which ones
require further attention. But I’ll be more than to experiment of there are any
suggestions.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
