I have the same issue with similar kern.log entries after upgrading to kernel 3.16.0-48. Removing that and falling back to 3.16.0-46 fixed it for me.
I have the same issue with similar kern.log entries after upgrading to kernel 3.16.0-48. Removing that and falling back to 3.16.0-46 fixed it for me.