I am not sure if I did not speak too soon. I just booted 3.1.6-1.fc16.x86_64 and I again see in dmesg for every detected connector "No monitor connected or invalid EDID", which is not really the case, and repeated attempts to read "Raw EDID" blocks filled with 0. I guess that I will keep "anti-poll" measures in place.
These series of "radeon_dri2_schedule_flip:670" and "radeon_dri2_flip_event_handler:1067" are still there.
I am not sure if I did not speak too soon. I just booted 3.1.6-1.fc16.x86_64 and I again see in dmesg for every detected connector "No monitor connected or invalid EDID", which is not really the case, and repeated attempts to read "Raw EDID" blocks filled with 0. I guess that I will keep "anti-poll" measures in place.
These series of "radeon_ dri2_schedule_ flip:670" and "radeon_ dri2_flip_ event_handler: 1067" are still there.