Comment 8 for bug 1080320

Similar messages reported on LKML:
https://lkml.org/lkml/2012/10/16/291

However, it seems like the LKML thread states this bug does not happen in v3.6 and the commit in question was introduced in v3.7-rc1:

git describe --contains 65fe1f0f66a57380229a4ced844188103135f37b
v3.7-rc1~138^2~9