I can confirm that the issue with kernel 3.13.0-46 still exist. The only way around I see is using 3.14-kernel
I can confirm that the issue with kernel 3.13.0-46 still exist. The only way around I see is using 3.14-kernel