From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34709] New: with r300 (rv530) kms loaded cannot suspend kernel 2.6.37+ with uswsusp
Date: Fri, 25 Feb 2011 03:43:41 -0800 (PST) [thread overview]
Message-ID: <bug-34709-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=34709
Summary: with r300 (rv530) kms loaded cannot suspend kernel
2.6.37+ with uswsusp
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: hramrach@gmail.com
After upgrading from kernel 2.6.36 to 2.6.37 I can no longer suspend the system
with uswsusp.
The suspend operation hangs with displays blanked before the part when "Saving
image to disk" takes place.
Suspending with "echo disk > /sys/power/state" works but is obviously useless
as the system cannot be resumed.
Upgrading to 2.6.38 does not help, not loading the radeon module allows to
suspend as usual.
A pointer to a repo with Radeon changesets between 2.6.36 and 2.6.37 without
needlessly intermingled changes to other kernel parts would be appreciated.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-25 11:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 11:43 bugzilla-daemon [this message]
2011-02-25 17:06 ` [Bug 34709] with r300 (rv530) kms loaded cannot suspend kernel 2.6.37+ with uswsusp bugzilla-daemon
2011-02-25 17:55 ` bugzilla-daemon
2011-02-25 18:51 ` bugzilla-daemon
2011-03-06 15:38 ` bugzilla-daemon
2011-03-17 9:31 ` bugzilla-daemon
2011-04-01 20:36 ` [Bug 34709] [bisected] " bugzilla-daemon
2011-04-01 20:38 ` bugzilla-daemon
2011-04-01 21:20 ` bugzilla-daemon
2011-04-01 21:32 ` bugzilla-daemon
2011-04-01 22:11 ` bugzilla-daemon
2011-04-02 13:30 ` bugzilla-daemon
2011-04-04 18:14 ` bugzilla-daemon
2011-04-04 19:55 ` bugzilla-daemon
2011-04-04 22:11 ` bugzilla-daemon
2011-04-04 22:18 ` bugzilla-daemon
2011-04-12 12:47 ` bugzilla-daemon
2011-04-12 14:00 ` bugzilla-daemon
2011-04-12 14:09 ` bugzilla-daemon
2011-04-12 14:13 ` bugzilla-daemon
2011-04-12 15:20 ` bugzilla-daemon
2011-04-12 17:38 ` bugzilla-daemon
2011-05-05 7:48 ` 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-34709-502@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