From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76761] radeon DPM breaks suspend to disk and resume from RAM in 3.14
Date: Fri, 29 Aug 2014 18:28:44 +0000 [thread overview]
Message-ID: <bug-76761-2300-rglRsD5pRa@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-76761-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=76761
StephenH <hafflys@earthlink.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hafflys@earthlink.net
--- Comment #19 from StephenH <hafflys@earthlink.net> ---
Fedora kernel 3.15.x versions on an Acer Aspire One netbook with AMD C50
processor and Radeon driver has this problem.
Kernel 3.14.x and earlier kernel versions did not have this problem.
Whatever changed between 3.14.x and 3.15.x has caused this problem. I have a
bug report at https://bugzilla.redhat.com/show_bug.cgi?id=1121838 but I think
the problem will need to be addressed here, upstream from Fedora.
Kernels 3.14 and under = work fine.
Kernels 3.15.x != work
I asked in the buzilla report cited above what changed that could cause this
and how do I fix it? With Fedora working to rebase Fedora 20 to 3.16.x, if the
problem has not been fixed, then there will be problems. This will be even more
so when Fedora 21 is released and Fedora 19 becomes an E.O.L. version. I am
currently running Fedora 20, but I have to use a Fedora 19 kernel
(3.14.17-100.fc19.x86_64) in order to have suspend/resume work properly.
Please don't ask me to bisect unless you give me explicit directions on how to
do so. I have no idea what bisecting does or how to do it. I'm not a developer.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2014-08-29 18:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 19:35 [Bug 76761] New: radeon driver breaks suspend to disk and resume from RAM in 3.14 bugzilla-daemon
2014-05-22 19:51 ` [Bug 76761] " bugzilla-daemon
2014-05-22 19:56 ` bugzilla-daemon
2014-05-22 19:57 ` [Bug 76761] radeon DPM " bugzilla-daemon
2014-05-23 23:24 ` bugzilla-daemon
2014-05-24 16:43 ` bugzilla-daemon
2014-05-27 21:23 ` bugzilla-daemon
2014-05-28 0:11 ` bugzilla-daemon
2014-05-30 14:31 ` bugzilla-daemon
2014-05-30 14:49 ` bugzilla-daemon
2014-05-30 22:34 ` bugzilla-daemon
2014-05-30 22:42 ` bugzilla-daemon
2014-06-02 21:33 ` bugzilla-daemon
2014-06-09 7:19 ` bugzilla-daemon
2014-06-09 13:46 ` bugzilla-daemon
2014-06-10 3:25 ` bugzilla-daemon
2014-06-10 3:36 ` bugzilla-daemon
2014-06-10 7:22 ` bugzilla-daemon
2014-06-10 8:29 ` bugzilla-daemon
2014-06-10 14:00 ` bugzilla-daemon
2014-08-29 18:28 ` 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-76761-2300-rglRsD5pRa@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 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.