From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 214197] [Asus G713QY] RX6800M not usable after exiting Vulkan application
Date: Sat, 28 Aug 2021 17:49:40 +0000 [thread overview]
Message-ID: <bug-214197-2300-iio7g84owG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214197-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214197
--- Comment #4 from velemas@gmail.com ---
(In reply to Alex Deucher from comment #2)
> Does this patch fix the issue?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
> ?id=202ead5a3c589b0594a75cb99f080174f6851fed
Kernel 5.13.13 has this patch already. So apparently it does not fix the
problem.
It occurs with radv, amdvlk, and amdvlk-pro. External monitor is attached via
HDMI (although it happens without ext. monitor too).
Sometimes dmesg does not contain above mentioned lines but dGPU is still
unusable. Sometimes DXVK delivers VK_ERROR_DEVICE_LOST status even during
runtime.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-08-28 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 10:44 [Bug 214197] New: [Asus G713QY] RX6800M not usable after exiting Vulkan application bugzilla-daemon
2021-08-27 15:05 ` [Bug 214197] " bugzilla-daemon
2021-08-27 17:27 ` bugzilla-daemon
2021-08-28 17:48 ` bugzilla-daemon
2021-08-28 17:49 ` bugzilla-daemon [this message]
2021-10-19 5:36 ` bugzilla-daemon
2021-10-20 20:30 ` bugzilla-daemon
2021-10-21 8:57 ` bugzilla-daemon
2022-01-30 11:56 ` bugzilla-daemon
2022-01-30 11:57 ` 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-214197-2300-iio7g84owG@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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