Bug 25546

Summary: Display corruption after monitor standby
Product: xorg Reporter: Ancoron <ancoron>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED WORKSFORME QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: 7.4 (2008.09)   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg
none
Xorg.0.log
none
photo of the noise (cannot be captured through software) none

Description Ancoron 2009-12-09 14:44:27 UTC 
Created attachment 31900 [details]
dmesg

OS: Kubuntu 9.10 Karmic Koala
Kernel: 2.6.31-16-generic (amd64)
GPU: Radeon X1950XTX
Monitor: Dell 3007WFP-HC
Setup: 2560x1600@60Hz (automatically through monitor supplied timings)

If my monitor was some more time into automatic standby (> 30 minutes) and if I wake it up again through mouse movement flickering noise appears all over the screen, but really heavy in pure black areas.

I can fix the flickering by switching into another terminal (see https://bugs.freedesktop.org/show_bug.cgi?id=25545 for that) and back again.

After that all things are fine again.

I also have to note that the monitor standby is NOT the result of power management through software as it is disabled. Also if I wait less that half an hour (haven't measured that exactly yet) after the monitor went into standby the flickering noise doesn't appear.

I'll attach a bad handy shot of the noise.
Comment 1 Ancoron 2009-12-09 14:44:51 UTC 
Created attachment 31901 [details]
Xorg.0.log
Comment 2 Ancoron 2009-12-09 14:45:39 UTC 
Created attachment 31902 [details]
photo of the noise (cannot be captured through software)
Comment 3 Ancoron 2010-03-10 16:01:07 UTC 
I have another machine now with a Radeon HD4770 and a Dell 3007WFP-HC.

On that system those corruptions do not appear.
Comment 4 Alex Deucher 2010-10-19 18:54:45 UTC 
Is this still an issue with KMS or a newer version of the driver?
Comment 5 Ancoron 2010-10-25 15:25:07 UTC 
Oh my, mixed this one up with bug #24722.

Nevertheless I must say that the card burned itself so I can't verify this anymore.

And I never saw anything like this again with any other card so I simply say that it was some hardware failure and not the software. :)

This can be safely closed I guess.

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.