From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111244] amdgpu kernel 5.2 blank display after resume from suspend
Date: Thu, 19 Sep 2019 19:37:28 +0000 [thread overview]
Message-ID: <bug-111244-502-wfi2skA9Ew@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111244-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 877 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111244
--- Comment #29 from Gabriel C <nix.or.die@gmail.com> ---
Michael,
I see the same on a Ryzen 7 35750H APU + RX 560x Nitro5 Laptop.
reverting
https://github.com/freedesktop/xorg-xf86-video-amdgpu/commit/a2b32e72fdaff3007a79b84929997d8176c2d512
fixes the problem for me.
I tested kernels 5.2*, 5.3, and all have the same problem
when suspending from X with that commit, without the commit
everything is working fine.
( will test 5.4git once drm-next is in but I tested amd-staging-drm-next
some days ago and that didn't work also )
If you need more informations please let me know.
I can test any kind patches kernel/X/mesa and/or give
you debug info if you tell me what you may need.
Best Regards,
Gabriel C
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1791 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 prev parent reply other threads:[~2019-09-19 19:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 4:02 [Bug 111244] amdgpu kernel 5.2 blank display after resume from suspend bugzilla-daemon
2019-07-29 4:04 ` bugzilla-daemon
2019-07-29 4:04 ` bugzilla-daemon
2019-07-29 8:34 ` bugzilla-daemon
2019-07-29 8:37 ` bugzilla-daemon
2019-07-29 9:22 ` bugzilla-daemon
2019-07-29 9:50 ` bugzilla-daemon
2019-07-29 18:38 ` bugzilla-daemon
2019-08-02 11:01 ` bugzilla-daemon
2019-08-02 13:19 ` bugzilla-daemon
2019-08-02 13:21 ` bugzilla-daemon
2019-08-02 13:27 ` bugzilla-daemon
2019-08-02 13:28 ` bugzilla-daemon
2019-08-02 18:14 ` bugzilla-daemon
2019-08-03 2:43 ` bugzilla-daemon
2019-08-03 8:19 ` bugzilla-daemon
2019-08-04 18:02 ` bugzilla-daemon
2019-08-05 18:59 ` bugzilla-daemon
2019-08-07 9:41 ` bugzilla-daemon
2019-08-07 9:42 ` bugzilla-daemon
2019-08-07 9:44 ` bugzilla-daemon
2019-08-07 9:51 ` bugzilla-daemon
2019-08-07 10:22 ` bugzilla-daemon
2019-08-07 10:39 ` bugzilla-daemon
2019-08-07 13:48 ` bugzilla-daemon
2019-08-07 13:58 ` bugzilla-daemon
2019-08-07 21:43 ` bugzilla-daemon
2019-08-14 12:29 ` bugzilla-daemon
2019-08-14 19:14 ` bugzilla-daemon
2019-08-14 21:15 ` bugzilla-daemon
2019-08-16 19:25 ` bugzilla-daemon
2019-09-17 21:32 ` bugzilla-daemon
2019-09-19 19:37 ` bugzilla-daemon [this message]
2019-09-19 19:38 ` bugzilla-daemon
2019-09-20 12:05 ` bugzilla-daemon
2019-10-04 13:47 ` bugzilla-daemon
2019-10-04 13:47 ` bugzilla-daemon
2019-10-22 11:45 ` bugzilla-daemon
2019-11-19 9:38 ` 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-111244-502-wfi2skA9Ew@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;
as well as URLs for NNTP newsgroup(s).