From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106111] [GPU Passthrough]GPU (Polaris) not reinitialized with Linux VM (Reset bug)
Date: Wed, 18 Apr 2018 16:13:52 +0000 [thread overview]
Message-ID: <bug-106111-502-4x7nDHL5J2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106111-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1451 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106111
--- Comment #4 from Alex Williamson <alex.williamson@redhat.com> ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2318 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-18 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 22:29 [Bug 106111] [GPU Passthrough]GPU (Polaris) not reinitialized with Linux VM (Reset bug) bugzilla-daemon
2018-04-17 22:30 ` bugzilla-daemon
2018-04-17 22:55 ` bugzilla-daemon
2018-04-18 6:11 ` bugzilla-daemon
2018-04-18 16:13 ` bugzilla-daemon [this message]
2018-04-18 16:33 ` bugzilla-daemon
2018-08-18 8:31 ` bugzilla-daemon
2018-09-14 10:30 ` bugzilla-daemon
2019-11-19 8:35 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-106111-502-4x7nDHL5J2@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox