I was able to speak with folks at Intel about this and got some good info from them:
* To avoid confusion, we need to be clear that the i7-8565U is a Whiskey Lake processor (*not* a Kaby Lake) - https://ark.intel.com/content/www/us/en/ark/products/149091/intel-core-i7-8565u-processor-8m-cache-up-to-4-60-ghz.html * There is an upstream intel-microcode bug report that is already tracking this issue - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 * The upstream bug report suggests that the problem is seen with both the 20190312 and 20190514 microcode releases * This may be a bug in how the kernel is loading the microcode
I was able to speak with folks at Intel about this and got some good
info from them:
* To avoid confusion, we need to be clear that the i7-8565U is a Whiskey /ark.intel. com/content/ www/us/ en/ark/ products/ 149091/ intel-core- i7-8565u- processor- 8m-cache- up-to-4- 60-ghz. html /github. com/intel/ Intel-Linux- Processor- Microcode- Data-Files/ issues/ 1
Lake processor (*not* a Kaby Lake)
- https:/
* There is an upstream intel-microcode bug report that is already
tracking this issue
- https:/
* The upstream bug report suggests that the problem is seen with both
the 20190312 and 20190514 microcode releases
* This may be a bug in how the kernel is loading the microcode