Bug 93753 - Sometimes wrong clk frequency of Display after dpms mode changes.
Summary: Sometimes wrong clk frequency of Display after dpms mode changes.
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-18 10:29 UTC by t.graziadei
Modified: 2019-11-19 09:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Screenshot of failure (92.32 KB, image/jpg)
2016-01-18 10:29 UTC, t.graziadei
no flags Details
original test image (125.85 KB, image/jpg)
2016-01-18 10:30 UTC, t.graziadei
no flags Details
dmesg output of startup in case of failure (100.07 KB, text/plain)
2016-01-18 10:31 UTC, t.graziadei
no flags Details
Screenshot of failure (92.32 KB, image/jpeg)
2016-01-18 10:32 UTC, t.graziadei
no flags Details
original test image (125.85 KB, image/jpeg)
2016-01-18 10:32 UTC, t.graziadei
no flags Details

Description t.graziadei 2016-01-18 10:29:56 UTC
Created attachment 121103 [details]
Screenshot of failure

Sometimes after the deactivation of the screensaver or also on bootup the screen shows flickering noise and a duplicated screen image. (Attached there is the used test image and a screenshot of the failure image). 

We tested on various kernel versions, latest kernel tested was 4.4.0. We run a customized debian image. 

Further investigations showed, that in the failure scenario the measured clk frequency was only 25MHz but it should be 35MHz. 

We also tried to deactivate dpms completly (radeon.dpm=0 in kernel parameters) and also turned the dpms off in the screensaver, but we still sometimes encounter the problem after a reboot. 

Attached you will find a dmesg output with drm.debug=0xf activated. 

We use a Radeon PALM on a AMD G-T40E 2x1GHz
Comment 1 t.graziadei 2016-01-18 10:30:56 UTC
Created attachment 121104 [details]
original test image
Comment 2 t.graziadei 2016-01-18 10:31:18 UTC
Created attachment 121105 [details]
dmesg output of startup in case of failure
Comment 3 t.graziadei 2016-01-18 10:32:28 UTC
Created attachment 121106 [details]
Screenshot of failure
Comment 4 t.graziadei 2016-01-18 10:32:58 UTC
Created attachment 121107 [details]
original test image
Comment 5 Alex Deucher 2016-02-05 17:19:59 UTC
What mode are you trying to set?  Please attach your xorg log and and config (if you have one) and the xrandr --verbose output.
Comment 6 Alex Deucher 2016-02-05 17:28:48 UTC
DPM has nothing to do with the display clocks or dpms.  It's engine clock management.  Also which display are you having problems with, VGA or LVDS?
Comment 7 Martin Peres 2019-11-19 09:11:20 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/678.


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.