On Thu, Oct 24, 2019 at 11:18:59AM -0400, Derek Yerger wrote: > On 10/22/19 4:28 PM, Sean Christopherson wrote: > >On Thu, Oct 17, 2019 at 07:57:35PM -0400, Derek Yerger wrote: > >Heh, should've checked from the get go... It's definitely not the memslot > >issue, because the memslot bug is in 5.1.16 as well. :-) > I didn't pick up on that, nice catch. The memslot thread was the closest > thing I could find to an educated guess. > >>I'm stuck on 5.1.x for now, maybe I'll give up and get a dedicated windows > >>machine /s > >What hardware are you running on? I was thinking this was AMD specific, > >but then realized you said "AMD Radeon 540 GPU" and not "AMD CPU". > Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz > > 07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7) > Subsystem: Gigabyte Technology Co., Ltd Device 22fe > Kernel driver in use: vfio-pci > Kernel modules: amdgpu > (plus related audio device) > > I can't think of any other data points that would be helpful to solving > system instability in a guest OS. Can you bisect starting from v5.2? Identifying which commit in the kernel introduced the regression would help immensely. > But given my troubleshooting before, it > looks like presence/absence of a PCI passthrough device is inconsequential > to whether the problem is occurring. > > I may have to try out other VMs or a fresh windows guest.
