I took time to check Wily and the results are similar. This bug is present with the 4.2.0-27.30 kernel but the 4.2.0-29.31 kernel is OK.
So I'm guessing the updated intel driver fails to build properly with kernels prior to 4.2.0-29????????
I took time to check Wily and the results are similar. This bug is present with the 4.2.0-27.30 kernel but the 4.2.0-29.31 kernel is OK.
So I'm guessing the updated intel driver fails to build properly with kernels prior to 4.2.0-29????????