I finally had the chance to retest this Bug. And it is already fixed in 3.5. (I tested 3.5.3)
This is a bit embarrassing: I think I could track the fix to drm-intel-next.
It's included in this build: commit a85d4bcb8a0cd5b3c754f98ff91ef2b9b3a73bc5 Date: Fri Apr 20 11:50:01 2012 -0700
I finally had the chance to retest this Bug. And it is already fixed in 3.5. (I tested 3.5.3)
This is a bit embarrassing: I think I could track the fix to drm-intel-next.
It's included in this build: 3c754f98ff91ef2 b9b3a73bc5
commit a85d4bcb8a0cd5b
Date: Fri Apr 20 11:50:01 2012 -0700