since updating to the 4.4.0-28-generic kernel I have not seen this issue. I believe we can declare it fixed. Do we declare it Fix Released, or some other status?
since updating to the 4.4.0-28-generic kernel I have not seen this issue. I believe we can declare it fixed. Do we declare it Fix Released, or some other status?