Are you able to reproduce this bug consistently with 3.5.0-20.31 ? Does this issue not happen if you boot the previous kernel?
Are you able to reproduce this bug consistently with 3.5.0-20.31 ? Does this issue not happen if you boot the previous kernel?