Large and ever expanding Xorg.0.log file

[gadgetwiz]

I was looking at my log files today and noticed that my Xorg.0.log was 78 meg. Deleted it and rebooted, then loaded it into gedit to take a look. After tiling the open apps and moving back, gedit reported that the Xorg.0.log had changed on the disk and asked if I wanted to reload.

I said yes and it appears the following lines are constantly being added to the log as I'm running...

[   618.404] (II) RADEON(0): radeon_dri2_flip_event_handler:1069 fevent[0x94cb590] width 1440 pitch 5888 (/4 1472)
[   618.509] (II) RADEON(0): radeon_dri2_schedule_flip:665 fevent[0x9539178]
[   618.653] (II) RADEON(0): radeon_dri2_flip_event_handler:1069 fevent[0x9539178] width 1440 pitch 5888 (/4 1472)
[   618.690] (II) RADEON(0): radeon_dri2_schedule_flip:665 fevent[0x9589de0]
[   618.722] (II) RADEON(0): radeon_dri2_flip_event_handler:1069 fevent[0x9589de0] width 1440 pitch 5888 (/4 1472)
[   618.731] (II) RADEON(0): radeon_dri2_schedule_flip:665 fevent[0x92fdf18]
[   618.755] (II) RADEON(0): radeon_dri2_flip_event_handler:1069 fevent[0x92fdf18] width 1440 pitch 5888 (/4 1472)
[   618.799] (II) RADEON(0): radeon_dri2_schedule_flip:665 fevent[0x93243a8]
[   618.820] (II) RADEON(0): radeon_dri2_flip_event_handler:1069 fevent[0x93243a8] width 1440 pitch 5888 (/4 1472)
[   705.652] (II) RADEON(0): radeon_dri2_schedule_flip:665 fevent[0x92b8120]
[   705.670] (II) RADEON(0): radeon_dri2_flip_event_handler:1069 fevent[0x92b8120] width 1440 pitch 5888 (/4 1472)

This seems very odd and I've never noticed this behavior before. Any ideas why this is occurring?

Thanks!

[rtguille]

You might want to take a look at https://bugzilla.redhat.com/show_bug.cgi?id=820731

It seems very similar.

[gadgetwiz]

Yes, Thanks!

That certainly looks like the same issue I'm having. I wonder it it has anything to do with recent kernel updates?

I didn't notice this problem until very recently. I need to boot into the older kernels on my list to see if it is indeed a kernel issue.

Update: I checked kernels all the way back to : 3.4.6-2.fc17.i686.PAE and I still have this issue so I guess I can rule out this being a kernel issue. Perhaps I've always had this problem with F17 and have just never noticed it before.