![]() Interrupt Storm Detected Proxmox Driver Issue With ![]() Im not a PCI hardware guy, I tried to go down the rabbit hole a little. If anyone actually has PCI-e passthrough working on X399 that would be interesting to know: I havent found a person that was succesful yet. This happens even in normal operation without virt-pci bound (just the normal nvidia or amdgpu modules). Sata bus is basically dead, USB bus is incredibly splotchy (mouse and keyboard stutter visibly at 500ms), GPUs have extreme ghosting and the one that was passed through is unusable.ĪER reports hundreds of unrecoverable errors and crashes everything.Īs a third symptom, there are sporadic TLP errors in the DLL on the bridges for the 16x lanes. Only a reboot will bring the bridge back in to IO state where it can be usedrescanedunbind, really anything. On the 1080Ti, the bridge fails and the 1080Ti goes in to cold D3.Īny subsequent attempts to use the 1080Ti in any way will throw a IO error due to the bridge. The problem is a somewhat deeper issue where when libvirt attempts to start the passthrough device (either GPU) its unable to do so because the bridge in charge of the devices fails. ![]() Lets start from setup: reports have seen this on the ASRock Taichi, Gigabyte, and MSI motherboards. Heres to hoping that a little public awareness will maybe get someone in the right spot to take a look at this. Some of you might have seen my other threads, but Ive been hitting a wall on GPU passthrough for about the last four days.Īdditionally, there are now 4 other reports of users on the X399 platform that are unable to get PCI passthrough to work due to the exact same strange PCI bus issues. Interrupt Storm Detected Proxmox Driver Issue With.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |