Created attachment 59619 [details] [review] Xorg log from incident When I turn off my monitor, the X server freezes and stops updating output to monitors. When I power monitor up again, instead of screen see no signal HDMI. This is specific to DisplayPort --> HDMI, and specific to ASUS VH242HL 23" monitor. Condition did not occur with DVI --> HDMI connection. Condition also does not occur power cycling of Sharp Aquos TV running on dual monitor setup. However, when powering up ASUS monitor in dual monitor setup, video freezes on last frame on second Aquos monitor. So I power cycle the ASUS and the picture on the Aquos stops on the last frame and is unresponsive. (Audio through separate sound card continues) Freeze can be recovered by restarting xorg server ctrl-Alt-Backspace (twice). Running OpenSuse 12.1 on AMD 64 (Phenom II). Video card is AMD ATI FirePRO 2270 with DMS59 connector. Problem occurs when using DMS59 adapter --> DisplayPort --> HDMI. Have used catalyst ffglx recently troubleshooting HDMI audio but presently not installed. Using opensource ATI driver. Issue makes DisplayPort --> HDMI unusable.
Please attach your dmesg output.
Created attachment 59702 [details] truncated dmesg output from bug reproduced bug for new output
Bug consistently occurs from pressing power button on ASUS monitor. However, less severe than first thought because GNOME 3 screen/power management tools work ok and put monitor into powersaving mode/off eventually without pressing button. Monitor not completely shut off that way; power button shows standby. Wakes without problem from GNOME 3-initiated powersave.
-- 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/259.
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.