From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71051] Cannot suspend with radeon drivers.
Date: Fri, 23 Jan 2015 21:05:53 +0000 [thread overview]
Message-ID: <bug-71051-2300-e61DlpKROs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71051-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=71051
Thomas J. Moore <darktjm@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |darktjm@gmail.com
--- Comment #16 from Thomas J. Moore <darktjm@gmail.com> ---
I have a Dell Inspiron with AMD A6 (Advanced Micro Devices, Inc. [AMD/ATI]
Mullins [Radeon R4/R5 Graphics]), and stopped upgrading my kernel at 3.16.3
because it would no longer resume from disk about 90% or more of the time. I
have finally given in and looked for the cause a bit, and have traced it to
this patch. Without this patch, 3.18.3 (and probably all other versions I
skipped before it) works fine for me. That said, I never suspend to memory,
and so I tried with and without, and indeed the patch seems to be necessary for
resume-from-memory on my system as well. So, while this patch does fix a bug,
it introduces a regression for me. Is it possible the value of nb_dpm_enabled
is not restored or initialized properly on resume from disk, due to the video
mode change?
The symptoms when resuming from disk are similar to comment 9 (ring test
failures, which do not occur without the patch), with X crashing (and, due to
the fact that I start it in inittab, retrying with "couldn't schedule ib" error
until I reboot or disable the inittab entry).
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-01-23 21:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-71051-2300@https.bugzilla.kernel.org/>
2014-02-24 12:22 ` [Bug 71051] Cannot suspend with radeon drivers bugzilla-daemon
2014-02-24 14:28 ` bugzilla-daemon
2014-02-24 15:33 ` bugzilla-daemon
2014-02-24 15:34 ` bugzilla-daemon
2014-02-24 15:46 ` bugzilla-daemon
2014-02-24 15:47 ` bugzilla-daemon
2014-09-18 8:32 ` bugzilla-daemon
2014-09-18 15:46 ` bugzilla-daemon
2014-09-18 15:47 ` bugzilla-daemon
2014-09-19 5:27 ` bugzilla-daemon
2014-09-19 5:30 ` bugzilla-daemon
2014-09-19 5:36 ` bugzilla-daemon
2014-09-19 8:50 ` bugzilla-daemon
2014-09-20 5:04 ` bugzilla-daemon
2014-10-07 21:32 ` bugzilla-daemon
2014-10-10 22:40 ` bugzilla-daemon
2015-01-23 21:05 ` 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-71051-2300-e61DlpKROs@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.