From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100979] Radeon r4 on a6-6310(BEEMA) APU hard lockup on hibernate and on second resume from suspend
Date: Fri, 15 Feb 2019 15:10:32 +0000 [thread overview]
Message-ID: <bug-100979-502-4FnkpuufeT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100979-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100979
Przemek <soprwa@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #14 from Przemek <soprwa@gmail.com> ---
I have tested hibernation on amd-staging-drm-next (git status - commit
fa16d1eb6a78b265480bd4c2b8739c1ea261cdd8 ) and it's working as it should (with
minor glitch).
Moreover I can suspend and resume the machine many times in a row without
freeze/lockup.
I nave no idea which commit made things work again, because haven't checked
this future lately.
The only problem is that the second monitor connected to hdmi output is turning
of after suspend/hibernate, and eDP screen brightness level is maxed out after
resume from hibernate but this is not the case of this report.
Given the above I'm closing this bug report as RESOLVED/FIXED.
Thank you very much,
Przemek.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2774 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-02-15 15:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 21:11 [Bug 100979] Radeon r4 on a6-6310(BEEMA) APU hard lockup on hibernate and on second resume from suspend bugzilla-daemon
2017-05-09 21:12 ` bugzilla-daemon
2017-05-09 21:13 ` bugzilla-daemon
2017-05-09 21:14 ` bugzilla-daemon
2017-05-09 21:15 ` bugzilla-daemon
2017-05-09 21:17 ` bugzilla-daemon
2017-06-02 15:33 ` bugzilla-daemon
2017-06-28 8:58 ` bugzilla-daemon
2017-07-03 16:07 ` bugzilla-daemon
2018-01-31 10:55 ` bugzilla-daemon
2018-01-31 11:29 ` bugzilla-daemon
2018-01-31 12:12 ` bugzilla-daemon
2018-02-06 23:30 ` bugzilla-daemon
2018-03-28 10:54 ` bugzilla-daemon
2019-02-15 15:10 ` bugzilla-daemon [this message]
2019-02-16 9:20 ` 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-100979-502-4FnkpuufeT@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).