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: Sat, 18 Aug 2018 08:31:32 +0000 [thread overview]
Message-ID: <bug-106111-502-uwpwppGItD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106111-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 671 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106111
--- Comment #6 from Radosław Szkodziński <astralstorm@gmail.com> ---
This is still happening. It seems that these GPU need engine resets before bus
reset, similar to what was done for Fury and Polaris, but more extensive.
Temporary workaround (yeah sure) is to eject the driver - rmmod in guest or
eject in Windows. This resets the engines.
Windows did the resets on shutdown until version 18.5.1 where they broke
shutdown sequence again - read release notes on Radeon Pro Vega FE drivers
where they actually slightly care.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1516 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-08-18 8:31 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
2018-04-18 16:33 ` bugzilla-daemon
2018-08-18 8:31 ` bugzilla-daemon [this message]
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-uwpwppGItD@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.