From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110571] GPU Passthrough of Vega 56 GPU hangs on KVM start.
Date: Wed, 01 May 2019 07:45:43 +0000 [thread overview]
Message-ID: <bug-110571-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1249 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110571
Bug ID: 110571
Summary: GPU Passthrough of Vega 56 GPU hangs on KVM start.
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: James.Dutton@gmail.com
When trying to use IOMMU and passthrough a Vega GPU to the guest VM. KVM fails
to start, and SERR errors are shown with lspci on the GPU device.
Hardware is a Threadripper 1950X, Gigabyte X399 Pro motherboard.
Vega 56.
The same problem also happens with an old Radeon CAICOS GPU.
So, my theory is that this is a AMD Threadripper and X399 motherboard problem.
Maybe related to the IOMMU programming on the X399 chipset not happening
correctly.
Can anyone help give me some pointers as to where to look to help diagnose the
problem.
For example, how do I view iommu settings/mappings?
How do I find out what all the config params for the X399 Bridge GPP do?
What does GPP mean?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2547 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-05-01 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 7:45 bugzilla-daemon [this message]
2019-11-19 9:19 ` [Bug 110571] GPU Passthrough of Vega 56 GPU hangs on KVM start 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-110571-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.