Bug#609145: results of git-bisecting when attempting to trigger displayed image corruption

[Arthur Marsh <arthur.marsh@internode.on.net>]

Hi, I did another git-bisect run where if the image at:  
 
http://photojournal.jpl.nasa.gov/jpeg/PIA13706.jpg 
 
loaded successfully in iceweasel, I would try to get it corrupted by moving a konsole 
window around over the displayed JPEG and the moving the iceweasel window rapidly. 
 
If the image corrupted or went black, or errors appeared in dmesg, I then ran  
 
git bisect bad. 
 
This resulted in a different "first bad commit": 
 
 
  time git bisect good 
d9fdaafbe912a34ef06ed569c6606fe2811f325b is the first bad commit 
commit d9fdaafbe912a34ef06ed569c6606fe2811f325b 
Author: Dave Airlie <airlied@redhat.com> 
Date:   Mon Aug 2 10:42:55 2010 +1000 
 
    drm/radeon/kms: move a bunch of modesetting debug to correct debug usage. 
 
    This migrates a bunch of DRM_DEBUG->DRM_DEBUG_KMS so we can get more modesetting related info without all the other ioctl handling easily. 
 
    Also the PM code moves to DRM_DEBUG_DRIVER mostly. 
 
    Signed-off-by: Dave Airlie <airlied@redhat.com> 
 
:040000 040000 7f060e1ae1a98eca3cf326a4409ba8d490a5beac 553fef7ee7f6c98f53a9079e40755792b4f798bd M      drivers