Comment 10 for bug 1546985

After looking at the several logs, they seem to be a bit inconsistent and make it difficult to point to a commit in this specific release. Also, I've failed to reproduce the issue locally.

Would it be possible for you to test the previous kernel (3.2.0-98.138) and double check that the issue does not occur there? If it doesn't, I guess we'll need to start a bisect.