This still appears to be a BUG we faced the issue with 3.19 4.2 kernel eventually fixed in 3.16.0-76-generic
not very clear on why the error throws up with the recent releases
This still appears to be a BUG we faced the issue with 3.19 4.2 kernel eventually fixed in 3.16.0-76-generic
not very clear on why the error throws up with the recent releases