@Philipp: The way I read them, your comment #35 and your comment #27 contradict each other.
@Xiong: The way I read all of this stuff, it has not been proven that the issue is in the microcode itself. However, the work done by Sharar in earlier postings, in my opinion, narrows it down to either the microcode itself or some loading issue when it is updated during boot. I had an idea to use "iucode_tool" to further isolate the issue, by going back and forth between microcodes, but now I see that one can not downgrade the microcode on the fly, it only works for upgrading. So now I am thinking maybe it would be possible to make the same microcode with a newer version number to "trick" the system into loading it. I.E. if upgrading to the fake "newer" microcode during boot also caused issues, then the root issue would be the load procedure. By the way, I don't have Xeon processor, I'm just trying to help with this bug report. >From all that I have been reading today, microcode 29 should be O.K., but >wasn't for Sharar. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776431 ** Bug watch added: Debian Bug tracker #776431 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776431 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480349 Title: Intel Microcode Breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1480349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
