I'm pretty certain that what you're seeing is already reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=17805 That particular bug is fixed in later versions of the intel driver. -- David Härdeman