@James Page, Did this bug just start happening after a new kernel update? Was there a prior kernel that did not get this fault? If so, we can perform a bisect to identify the commit that introduced the regression.
Also, the 3.11.0-3.7 kernel is now available, which is rebased to upstream v3.11-rc6. Can you test this latest kernel to confirm it still exhibits this bug?
@James Page, Did this bug just start happening after a new kernel update? Was there a prior kernel that did not get this fault? If so, we can perform a bisect to identify the commit that introduced the regression.
Also, the 3.11.0-3.7 kernel is now available, which is rebased to upstream v3.11-rc6. Can you test this latest kernel to confirm it still exhibits this bug?