Comment 60 for bug 1167301

Thanks for identifying the culprit, Til. Since the problem still exists from 3.8.8 all the way through to current mainline (3.11), I think the best course of action is for you to file a bug against DRM on bugzilla.kernel.org, so that upstream can sort out how they want to address it. We'll mirror whatever method upstream prefers to address it (fix, revert, override switch, etc.) in 3.8-stable and Raring.