Could be related to bug 60236. If that's not it, can you bisect which kernel change introduced the problem?