Bug 39953 - Flicker after waking from DPMS sleep
Summary: Flicker after waking from DPMS sleep
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: medium minor
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2011-08-08 23:56 UTC by Lauri Kasanen
Modified: 2019-11-19 08:20 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

lspci -vvnn (10.86 KB, text/plain)
2011-08-08 23:56 UTC, Lauri Kasanen
no flags Details
dmesg (35.20 KB, text/plain)
2011-08-09 00:07 UTC, Lauri Kasanen
no flags Details

Description Lauri Kasanen 2011-08-08 23:56:54 UTC
Created attachment 50058 [details]
lspci -vvnn

My E-350 laptop screen flickers for ~5 minutes every time after waking from DPMS. The flicker persists through VT switches and changing the power profile to high.

After the wait it stabilizes and picture is good again.

It looks similar to a CRT on 60Hz, but xrandr is confident the mode is right for the lcd (60hz, not something lower).

Lenovo G575 laptop
AMD E-350
Linux 3.0.1
Comment 1 Lauri Kasanen 2011-08-09 00:07:30 UTC
Created attachment 50060 [details]
Comment 2 Lauri Kasanen 2011-08-09 00:08:56 UTC
Now that I tried to make it happen manually (sleep 1 && xset dpms force off), it didn't show itself; though for the last few days, it's always happened after X's 10-minute delay DPMS.
Comment 3 Simon Strandman 2011-10-04 01:05:19 UTC
I have this problem too on similar E350-based hardware.

Sometimes I get this flicker, sometimes the screen is garbled (bug #36513). When I get a garbled screen the flicker usually persists even after a reboot. (Though this never happens in windows so I don't think it's a hardware issue.)
Comment 4 Marc Deslauriers 2011-10-15 20:03:41 UTC
I am getting this on a C-50 based Acer Aspire One 522.
I can reliably reproduce the issue with:

xset dpms force off; sleep 10; xset dpms force on
Comment 5 Martin Peres 2019-11-19 08:20:21 UTC
-- 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/208.

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.