Created attachment 1230240 [details] Smoking Gun Description of problem: INTEL completely went out of any mental sanity, out of any common sense: BDW-U i7 CPUID = SKL-U i7 CPUID??? From the same log (attached), representing here: [ 0.068155] TSC deadline timer enabled [ 0.068161] smpboot: CPU0: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (family: 0x6, model: 0x5e, stepping: 0x3) [ 0.068166] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. And, the same log (attached): [ 1.093757] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4 [ 1.094860] microcode: sig=0x506e3, pf=0x20, revision=0x9e [ 1.095620] microcode: Microcode Update Driver: v2.01 <tigran.co.uk>, Peter Oruba Version-Release number of selected component (if applicable): Latest Fedora 25, kernel 4.8.11-300.fc25.x86_64 How reproducible: Always Steps to Reproduce: INTEL Inside Results: [ 1.093757] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4 [ 1.094860] microcode: sig=0x506e3, pf=0x20, revision=0x9e [ 1.095620] microcode: Microcode Update Driver: v2.01 <tigran.co.uk>, Peter Oruba Expected results: [ 1.093757] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4 [ 1.094860] microcode: sig=0x605e3, pf=0x20, revision=0x9e [ 1.095620] microcode: Microcode Update Driver: v2.01 <tigran.co.uk>, Peter Oruba Additional info: Complete Craziness (INTEL plays some ugly tricks, don't they?)??? Isn't it? ;-) I need in NO time INTEL people here, to start explaining... before what... Before what??? You tell me, INTEL Inside! ;-) Thank you, _nobody_
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days