Excellent, thanks. Are you able to find out which minor release 5.6.N the problem started in? Once we know the number it is sometimes easy to identify the code change that caused it.
Please also test some current kernels like 5.11 and 5.12 to be sure it's not something that's already been fixed.
Excellent, thanks. Are you able to find out which minor release 5.6.N the problem started in? Once we know the number it is sometimes easy to identify the code change that caused it.
Please also test some current kernels like 5.11 and 5.12 to be sure it's not something that's already been fixed.