Can you see if this bug still exists in the 3.13.0-106 kernel? It can be downloaded from: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11527714
If it does, can you see if this bug happens with the 3.13.0-100 kernel? It can be downloaded from: https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa/+build/11039050
Both these kernel required installing both the linux-image and linux-image-extra .deb packages.
Can you see if this bug still exists in the 3.13.0-106 kernel? It can be downloaded from: /launchpad. net/~canonical- kernel- team/+archive/ ubuntu/ ppa/+build/ 11527714
https:/
If it does, can you see if this bug happens with the 3.13.0-100 kernel? It can be downloaded from: /launchpad. net/~canonical- kernel- security- team/+archive/ ubuntu/ ppa/+build/ 11039050
https:/
Both these kernel required installing both the linux-image and linux-image-extra .deb packages.