Does the issue go away by just booting the 3.13.0-36-generic kernel and making no other changes? Then the problem comes back if you boot 3.13.0-37-generic? If that is the case, we can perform a kernel bisect to identify the commit that introduced this regression.
Does the issue go away by just booting the 3.13.0-36-generic kernel and making no other changes? Then the problem comes back if you boot 3.13.0-37-generic? If that is the case, we can perform a kernel bisect to identify the commit that introduced this regression.