[Bug 69514] New: R770 (Radeon 4850) screen/buffer corruption when waking up from sleep mode
https://bugs.freedesktop.org/show_bug.cgi?id=69514
Priority: medium Bug ID: 69514 Assignee: dri-devel@lists.freedesktop.org Summary: R770 (Radeon 4850) screen/buffer corruption when waking up from sleep mode Severity: normal Classification: Unclassified OS: All Reporter: peterasplund@gentoo.se Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI
If I put my computer in sleep/hibernate (doesn't seem to matter which one) the screen gets corrupted with colors everywhere. It does update, and things jump around when I try to press buttons, bring out menus, etc. It's like the drawing buffer is all jumbled up and it's reading/writing from/to the wrong place.
When something is updated, it's like I can see the picture/pixmap/icon for a fraction of a second, but then it's corrupted again. If I move the mouse continuously over a menu, to update the highlighting of it, I can see at least where I am on the screen. But the fonts are complete garbage, and it's unreadable. Perhaps I can photograph the screen if it's needed. I haven't tried taking a screenshot.
I'm using Gentoo, 3.11 gentoo-kernel, with Systemd and Gnome 3.8.
The TTY:s are not corrupted, so I'm able to switch to a TTY without problems.
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #1 from Peter Asplund peterasplund@gentoo.se --- I'm using a green background, and the whole corrupted screen is green. The screen looks like big green chunks that flickers when it's updated as I move the mouse.
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #2 from Alex Deucher agd5f@yahoo.com --- You mean when you wake up from suspend/hibernate so see the corruption? Please attach your xorg log and dmesg output.
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #3 from Alex Deucher agd5f@yahoo.com --- Also is this a regression? If so, can you bisect?
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #4 from Peter Asplund peterasplund@gentoo.se --- Created attachment 86071 --> https://bugs.freedesktop.org/attachment.cgi?id=86071&action=edit Xorg log including sleep and wakeup cycle, as well as shutting down afterwards.
Yes exactly, the corruption occurs when the computer wakes up from sleep/hibernation.
The behavior started at least two kernel versions ago, probably at 3.10. I _think_ it was working with 3.8, but I will check that soon, and get back to you.
Here's the Xorg.0.log.old from previous run. I was running for a while, and then put the computer in sleep mode, and then awoke it immediately. When the corruption has occurred, I shut it down normally.
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #5 from Peter Asplund peterasplund@gentoo.se --- Created attachment 86072 --> https://bugs.freedesktop.org/attachment.cgi?id=86072&action=edit dmesg, including hibernate cycle
Here's my dmesg output from last boot, including hibernation. The hibernation does not seem to work for some reason, because the computer wakes up immediately, but the screen still gets corrupted.
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #6 from Peter Asplund peterasplund@gentoo.se --- The screen gets corrupted on kernel 3.8.5 (which is the oldest kernel I have lying around) as well. I'm typing this blindly.
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #7 from Peter Asplund peterasplund@gentoo.se --- I don't know if I can bisect... I need some help in that case.
Gentoo has recently added a dependency on Systemd as a part of Gnome 3.8, and I think recovering from sleep/hibernate was working before that. But I'm not completely sure. Without systemd, sleep/hibernate doesn't work at all, so I'm unable to revert and test without it.
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #8 from Peter Asplund peterasplund@gentoo.se --- Here's a link to a video showing the problem. https://www.youtube.com/watch?v=t3RBRwMxrsk
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #9 from Alex Deucher agd5f@yahoo.com --- Make sure you kernel has this patch: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=02...
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #10 from Peter Asplund peterasplund@gentoo.se --- Yes, the patch seems to be in 3.11.1, as well as 3.11.0. I'm currently running: $ uname -a Linux skare 3.11.1-gentoo #1 SMP PREEMPT Thu Sep 19 15:18:53 CEST 2013 x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #11 from Peter Asplund peterasplund@gentoo.se --- Is there any debugging information/logging I can turn on during boot, and test again for more information?
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #12 from Alex Deucher agd5f@yahoo.com --- Ideally you could bisect.
https://bugs.freedesktop.org/show_bug.cgi?id=69514
--- Comment #13 from Peter Asplund peterasplund@gentoo.se --- I haven't been able to disect anything yet, but I do have some updated information. I switched back my BIOS settings to Hibernate via S3 instead of S1 (which I was forced to switch to because of Windows 7 somehow disabling my hibernate possibility because of some "known issue with power management" or something like it) and now my glitches are gone! The hibernate and wake-up works perfectly. I have yet to try Sleep I think, but I think I tried and it doesn't work at all since my motherboard only supports _either_ S1 or S3. This is very strange though, since I'm fairly certain I've used both of them before.
https://bugs.freedesktop.org/show_bug.cgi?id=69514
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #14 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/383.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org