From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196615] amdgpu - resume from suspend is no longer working on rx480
Date: Thu, 02 Nov 2017 16:52:21 +0000 [thread overview]
Message-ID: <bug-196615-2300-v4Y2sulqij@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196615-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196615
--- Comment #33 from Florian Schmitt (kommerz11@galois.de) ---
Looks like the patch made it into 4.13.11. Yay. Thanks!
From the changelog:
commit 0d74253003e6370e65468f5aec8c969bdef6733e
Author: Rex Zhu <Rex.Zhu@amd.com>
Date: Fri Oct 20 15:07:41 2017 +0800
drm/amd/powerplay: fix uninitialized variable
commit 8b95f4f730cba02ef6febbdc4ca7e55ca045b00e upstream.
refresh_rate was not initialized when program
display gap.
this patch can fix vce ring test failed
when do S3 on Polaris10.
bug: https://bugs.freedesktop.org/show_bug.cgi?id=103102
bug: https://bugzilla.kernel.org/show_bug.cgi?id=196615
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-11-02 16:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 20:12 [Bug 196615] New: amdgpu - resume from suspend is no longer working on rx480 bugzilla-daemon
2017-08-08 20:14 ` [Bug 196615] " bugzilla-daemon
2017-08-08 20:15 ` bugzilla-daemon
2017-08-08 20:44 ` bugzilla-daemon
2017-08-09 21:20 ` bugzilla-daemon
2017-08-09 21:21 ` bugzilla-daemon
2017-08-13 10:48 ` bugzilla-daemon
2017-08-17 17:39 ` bugzilla-daemon
2017-08-17 20:12 ` bugzilla-daemon
2017-08-17 20:12 ` bugzilla-daemon
2017-08-17 20:22 ` bugzilla-daemon
2017-08-17 20:28 ` bugzilla-daemon
2017-08-17 20:32 ` bugzilla-daemon
2017-08-25 12:28 ` bugzilla-daemon
2017-08-25 14:18 ` bugzilla-daemon
2017-09-07 17:43 ` bugzilla-daemon
2017-09-07 17:58 ` bugzilla-daemon
2017-09-07 18:07 ` bugzilla-daemon
2017-09-28 7:32 ` bugzilla-daemon
2017-10-01 21:29 ` bugzilla-daemon
2017-10-02 7:04 ` bugzilla-daemon
2017-10-09 14:15 ` bugzilla-daemon
2017-10-12 14:48 ` bugzilla-daemon
2017-10-12 14:56 ` bugzilla-daemon
2017-10-12 15:09 ` bugzilla-daemon
2017-10-12 20:18 ` bugzilla-daemon
2017-10-13 6:03 ` bugzilla-daemon
2017-10-13 21:36 ` bugzilla-daemon
2017-10-14 9:59 ` bugzilla-daemon
2017-10-17 7:09 ` bugzilla-daemon
2017-10-20 14:09 ` bugzilla-daemon
2017-10-20 20:17 ` bugzilla-daemon
2017-10-20 22:18 ` bugzilla-daemon
2017-10-21 13:58 ` bugzilla-daemon
2017-10-29 23:15 ` bugzilla-daemon
2017-11-02 16:52 ` bugzilla-daemon [this message]
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-196615-2300-v4Y2sulqij@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;
as well as URLs for NNTP newsgroup(s).