| Summary: | R770 (Radeon 4850) screen/buffer corruption when waking up from sleep mode | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Peter Asplund <peterasplund> | ||||||
| Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||||
| Status: | RESOLVED MOVED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | medium | ||||||||
| Version: | XOrg git | ||||||||
| Hardware: | Other | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Peter Asplund
2013-09-18 08:53:22 UTC
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. You mean when you wake up from suspend/hibernate so see the corruption? Please attach your xorg log and dmesg output. Also is this a regression? If so, can you bisect? Created attachment 86071 [details]
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.
Created attachment 86072 [details]
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.
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. 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. Here's a link to a video showing the problem. https://www.youtube.com/watch?v=t3RBRwMxrsk Make sure you kernel has this patch: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=022374c02e357ac82e98dd2689fb2efe05723d69 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 Is there any debugging information/logging I can turn on during boot, and test again for more information? Ideally you could bisect. 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. -- 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. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.