Bug 60510 - AMD Mobility Radeon HD4650 Screen Corruption with DPM
Summary: AMD Mobility Radeon HD4650 Screen Corruption with DPM
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-04 22:25 UTC by Wong Yong Jie
Modified: 2013-07-10 03:24 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.10.0-drm-next-20130705
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg (70.85 KB, text/x-log)
2013-07-04 22:28 UTC, Wong Yong Jie 		Details
lspci (2.38 KB, text/x-log)
2013-07-04 22:29 UTC, Wong Yong Jie 		Details
glxinfo (53.14 KB, text/x-log)
2013-07-04 22:30 UTC, Wong Yong Jie 		Details
Video BIOS (62.00 KB, application/octet-stream)
2013-07-04 22:32 UTC, Wong Yong Jie 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Wong Yong Jie 2013-07-04 22:25:06 UTC 
I'm testing out the new DPM patches on drm-next-3.11.

When there is heavy screen updates (i.e. dragging windows around), screen corruption appears (see video). DPM otherwise works perfectly; system runs cooler and UVD also works perfectly fine. 

Corruption does not occur with radeon.dpm off.

There is nothing unusual in the kernel logs.

I can provide more info if requested.

Video link: http://www.youtube.com/watch?v=WaWHBckwPpo&feature=youtu.be
Comment 1 Wong Yong Jie 2013-07-04 22:28:32 UTC 
Created attachment 106792 [details]
dmesg
Comment 2 Wong Yong Jie 2013-07-04 22:29:20 UTC 
Created attachment 106793 [details]
lspci
Comment 3 Wong Yong Jie 2013-07-04 22:30:05 UTC 
Created attachment 106794 [details]
glxinfo
Comment 4 Wong Yong Jie 2013-07-04 22:32:25 UTC 
Created attachment 106795 [details]
Video BIOS
Comment 6 Wong Yong Jie 2013-07-09 07:30:37 UTC 
Thanks! :D Building and testing it out, will report back when I'm done.
Comment 7 Wong Yong Jie 2013-07-10 03:24:02 UTC 
I can confirm that the issue has been resolved. Thanks!
Note You need to log in before you can comment on or make changes to this bug.