Comment 2 for bug 1457655

Well, the bug seems to have gone away under 4.1.0-rc5. So, either it's a heisenbug or, more likely, there was some kernel problem that has been fixed. I'll try again on 4.0.4 one of these days to see if I can repeat it, but, at least for now, I'm closing this as invalid.