https://bugs.freedesktop.org/show_bug.cgi?id=27731
--- Comment #21 from Thomas Vander Stichele <[email protected]> 2012-08-29 09:39:36 UTC --- I have the same issue. When my screen goes blank, the thing that works for me is to switch to console (ctrl-alt-Fx) and then back to X. I have a Fedora 16 box, with HDMI output going to a Sony AV, and then to a Sony TV. (I also use this machine a lot for audio playback using pulseaudio from my desktop, a bunch of meters away. Annoyingly right now that means I need to go over and 'wake up' the video again, but that's beside the point now) When sound stops, this is a related message in dmesg: [338173.088914] radeon 0000:01:00.0: Disabling not enabled HDMI After waking it up again, I get this: [475218.002803] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 220 Some of these messages get repeated (not sure why it repeatedly tries to disable), and sometimes I get raw EDID dumps too. [15507.482647] radeon 0000:01:00.0: Disabling not enabled HDMI [15508.113106] radeon 0000:01:00.0: Disabling not enabled HDMI [15508.240386] radeon 0000:01:00.0: Disabling not enabled HDMI [15508.863102] radeon 0000:01:00.0: Disabling not enabled HDMI [100442.985122] radeon 0000:01:00.0: Disabling not enabled HDMI [100443.615132] radeon 0000:01:00.0: Disabling not enabled HDMI [191169.540320] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 186 [191169.540328] Raw EDID: [191169.540333] 00 ff ff ff ff ff ff 00 4d d9 01 0b 01 01 01 01 [191169.540339] 1c 11 01 03 80 a0 5a 78 0a 0d c9 a0 57 47 98 27 [191169.540344] 12 48 4c 20 00 00 01 01 01 01 01 01 01 01 01 01 [191169.540348] 01 07 ff ff ff ff ff ff ff ff ff ff ff ff ff ff [191169.540353] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [191169.540358] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [191169.540362] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [191169.540367] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Tracing the message through the code, I see r600_hdmi_disable in drivers/gpu/drm/radeon which prints it, and gets called from radeon_atom_encoder_disable. However, I assume the suspend is being done correctly, and it's the wakeup code that causes the problem, and I'm not sure what the entry point is there. How can I assist in debugging this ? I'm interested enough to learn how to hack on this particular kernel module if necessary. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
