Did this issue just start happening with the 3.2.0-33-generic kernel, or did you see it in prior releases as well?
Did this issue just start happening with the 3.2.0-33-generic kernel, or did you see it in prior releases as well?