Does this bug still exist in an up-to-date kernel?
It is not an issue in intel-microcode, but rather a kernel defect. It has to be fixed by an updated kernel (and likely it has already been fixed)...
Does this bug still exist in an up-to-date kernel?
It is not an issue in intel-microcode, but rather a kernel defect. It has to be fixed by an updated kernel (and likely it has already been fixed)...