The issue was still present in linux-4.4.0 - but today (after switching to the first beta of 4.5.0) it did no more happen.
If we are really lucky this means the issue is resolved in that version of the kernel. Will comment this bug again once I have more experience with this kernel version.
The issue was still present in linux-4.4.0 - but today (after switching to the first beta of 4.5.0) it did no more happen.
If we are really lucky this means the issue is resolved in that version of the kernel. Will comment this bug again once I have more experience with this kernel version.