Comment 94 for bug 1384342

Øyvind, zob, everyone,

This bug has more than one cause. If you still see this in 3.16.0-33 or later and can reproduce it, then test the 4.0.0 kernel, and if it is fixed for you in 4.0.0 (and you can be bothered), you can do a bisect and figure out which patch fixed it.. but if it is not fixed in 4.0.0, then to get it fixed you will need to report it upstream to Intel: boot with drm.debug=0xe and get the complete dmesg up to the WARNING then follow the instructions at https://01.org/linuxgraphics/documentation/how-report-bugs