December 7, 20196 yr I recently got a new motherboard and GPU and am attempting to set it up with a VM Motherboard: Asus TUF x570-Plus (WiFi) CPU: Ryzen 5 3600X GPU: Radeon Rx 5700xt (Navi10) Motherboard settings: SR-IOV Support Enabled SVM Mode: Enabled Launch CSM: Enabled I tried updating to the latest unraid (GPU now shows as 5700xt instead of simply Navi10) and it seems to freeze here, too. It works fine in VNC, so I can only assume that the issue is with Navi10. I was able to grab some logs in /var/log/syslog before system froze. Dec 7 09:23:19 Tower kernel: vfio-pci 0000:05:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Dec 7 09:23:19 Tower kernel: br0: port 2(vnet0) entered blocking state Dec 7 09:23:19 Tower kernel: br0: port 2(vnet0) entered disabled state Dec 7 09:23:19 Tower kernel: device vnet0 entered promiscuous mode Dec 7 09:23:19 Tower kernel: br0: port 2(vnet0) entered blocking state Dec 7 09:23:19 Tower kernel: br0: port 2(vnet0) entered forwarding state Dec 7 09:23:20 Tower kernel: vfio-pci 0000:05:00.0: enabling device (0000 -> 0003) Dec 7 09:23:20 Tower kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x19@0x270 Dec 7 09:23:20 Tower kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x1b@0x2d0 Dec 7 09:23:20 Tower kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x25@0x400 Dec 7 09:23:20 Tower kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x26@0x410 Dec 7 09:23:20 Tower kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x27@0x440 Dec 7 09:23:20 Tower avahi-daemon[3104]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe54:b6f6. Dec 7 09:23:20 Tower avahi-daemon[3104]: New relevant interface vnet0.IPv6 for mDNS. Dec 7 09:23:20 Tower avahi-daemon[3104]: Registering new address record for fe80::fc54:ff:fe54:b6f6 on vnet0.*. Dec 7 09:23:32 Tower kernel: vfio-pci 0000:0d:00.4: not ready 1023ms after FLR; waiting Dec 7 09:23:35 Tower kernel: vfio-pci 0000:0d:00.4: not ready 2047ms after FLR; waiting Dec 7 09:23:38 Tower kernel: vfio-pci 0000:0d:00.4: not ready 4095ms after FLR; waiting Dec 7 09:23:40 Tower sshd[3124]: Accepted none for root from [192.168.1.x port ...] ssh2 Dec 7 09:23:43 Tower kernel: vfio-pci 0000:0d:00.4: not ready 8191ms after FLR; waiting Let me know if there are any more relevant logs that may shine more light on the issue.
December 7, 20196 yr 3 minutes ago, vitriohl said: Let me know if there are any more relevant logs that may shine more light on the issue. Posting the diagnostics zip file would pretty much encompass anything that would be needed to help
Archived
This topic is now archived and is closed to further replies.