Comment # 5
on bug 106111
from Max
(In reply to Alex Williamson from comment #4) > There is a difference, now we have: > > [ 84.997634] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x19@0x270 > [ 84.997645] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1b@0x2d0 > [ 84.997653] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1e@0x370 > [ 145.518307] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x19@0x270 > [ 145.518313] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1b@0x2d0 > [ 145.518318] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1e@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. Thanks for the explaination Alex. Something could be done ? By AMD or VFIO mainteners ?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
