I've been trying to reproduce this locally, but failed on all my machines, unfortunately. Skimming over net indicates that it's an issue that can't be easily fixed: https://bugzilla.kernel.org/show_bug.cgi?id=190281 Intel couldn't spend development resource for the older chips like this...