Comment 3 for bug 1408471

Also, did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.