From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42997] New: [R600] Corruption after resume from suspend to ram
Date: Wed, 16 Nov 2011 17:03:15 +0000 [thread overview]
Message-ID: <bug-42997-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=42997
Bug #: 42997
Summary: [R600] Corruption after resume from suspend to ram
Classification: Unclassified
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: thoemy@gmail.com
Created attachment 53605
--> https://bugs.freedesktop.org/attachment.cgi?id=53605
Xorg log showing start, suspend and resume
After resuming from suspend to ram I experience corruptions on the whole
screen. I'm using a compositing desktop with gnome-shell but the corruption is
also visible in the text consoles. I can recover from the corruption and
continue work normally if I change the resolution or screen orientation.
This bug is present in the kernel versions 3.0 - 3.2rc2 and I think also in
some releases before them. The graphics card is a HD3870, X.Org X Server
1.11.1.902
The radeon module is loaded with dynclks=1 audio=1
Attached are pictures of the corruption and a my Xorg.log. Any other
information I can provide?
--
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-11-16 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 17:03 bugzilla-daemon [this message]
2011-11-16 17:04 ` [Bug 42997] [R600] Corruption after resume from suspend to ram bugzilla-daemon
2011-11-16 17:05 ` bugzilla-daemon
2011-11-16 17:12 ` bugzilla-daemon
2011-11-16 17:13 ` bugzilla-daemon
2011-11-16 17:15 ` bugzilla-daemon
2019-11-19 8:23 ` 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-42997-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