It looks like the commit you mentioned is in v3.9-rc1: git describe --contains d3f677afb8076d09d090ff0a5d1229c9dd9f136e v3.9-rc1~139^2~61
Can you test the v3.9-rc1 kernel to confirm it resolves this bug? If it does, we can submit an SRU request to have that commit included in raring.
It looks like the commit you mentioned is in v3.9-rc1: 9d090ff0a5d1229 c9dd9f136e
git describe --contains d3f677afb8076d0
v3.9-rc1~139^2~61
Can you test the v3.9-rc1 kernel to confirm it resolves this bug? If it does, we can submit an SRU request to have that commit included in raring.