Is this still an issue with the latest drm-next-4.12-wip branch? I just a squashed in a fix for this.