[Bug 106111] [GPU Passthrough]GPU (Polaris) not reinitialized with Linux VM (Reset bug)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 18 16:13:52 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=106111

--- Comment #4 from Alex Williamson <alex.williamson at redhat.com> ---
There is a difference, now we have:

[   84.997634] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x19 at 0x270
[   84.997645] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1b at 0x2d0
[   84.997653] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1e at 0x370
[  145.518307] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x19 at 0x270
[  145.518313] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1b at 0x2d0
[  145.518318] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1e at 0x370

So prior to time 145.5 the VM was shutdown and started again and we could still
read config space of the device.  Previously we were already getting IOMMU
faults before the second startup.  But shortly after:

[  193.328586] AMD-Vi: Completion-Wait loop timed out
[  193.488711] AMD-Vi: Completion-Wait loop timed out
[  194.169913] iommu ivhd0: AMD-Vi: Event logged [
[  194.169921] iommu ivhd0: IOTLB_INV_TIMEOUT device=0a:00.0
address=0x000000043e8aaca0]
[  194.169924] iommu ivhd0: AMD-Vi: Event logged [
[  194.169928] iommu ivhd0: IOTLB_INV_TIMEOUT device=0a:00.0
address=0x000000043e8aacc0]

And the stuck in D3 state is evidence that the device is no longer accessible
on the bus.  So that only delayed the issue, some interaction between the IOMMU
and GPU is still failing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20180418/c62d176d/attachment.html>


More information about the dri-devel mailing list