GPU Reset script not working on new kernel

[Joris L.]

I could boot, but system froze or rebooted when starting the previously working VMs with PCI pass through. I reset CMOS, loaded defaults and went over all settings. Some settings about IOMMU etc were no longer available in BIOS. I did not try a reinstall of Proxmox and trying to get pass through working again, because the system did not give me any error messages. Without a clue on what was broken and given that more AGESA versions did NOT work rather than did work, I just reverted. But I have a different brand and chipset than you.

@Joris L. Which 1.0.0.6 version? AMD AGESA 1.0.0.6 from end of 2018 or AMD AGESA Combo-AM4 PI 1.0.0.6 from summer 2020? They restarted version numbering serveral times... I wanted to use the first one, but my motherboard came with a later version (support for Zen 2), which would not let me downgrade and I had to use a Beta-version to get pass through to work.

(beta) Agesa version of summer 2020, works like a charm. As it is running today the GPU scores higher than systems not running in a VM
i think i actually reinstalled proxmox due to the many weird things going on, as i had also upgraded ram i had no clue what caused the issue really

what i also did was run the ram at 2667 instead of 3200, since it runs solid as can be

 

[paulmorabi]

@Joris L. I removed all the boot parameters and also restored the BIOS to default settings. It still hung even with VFIO disabled. I also confirmed the root partition and other local partitions were all mounted fine. The only thing I didn't do was regenerate the initramfs but I ran out of time for this. My guess is that the device ID's and other underlying changes caused an issue somewhere. Given that the Ubuntu live CD worked, I am confident it was not a hardware issue. Because it hung during boot and didn't start networking, I couldn't SSH in and the rescue mode also hung in the same way. I would have expected/hoped the rescue boot would fix situations like this but not in my case. I'm tempted to try this again and do a full reinstall when I have more time and my node config and also VM's are backed up fully.

@avw Thanks also. The changes between AGESA versions seem significant. I jumped from a Jan 2019 BIOS to a June 2020 release. Still, it's strange to just hang the system. Anyhow, one other factor is MSI likely reduced some features/functions in the B450 bios software to support the Ryzen 3x series chips. My board and most others are 16mb rather than 32mb so get the "lite" interface.

I ended up reverting the BIOS back to the version I was previously using and that immediately restored everything back to how it was. For anyone else facing this, MSI and/or AMD block flashing to previous versions but if you are using the B450 boards then you can use the Flashback feature.