Changes between Version 1 and Version 2 of Ticket #13656, comment 4


Ignore:
Timestamp:
06/15/2020 09:44:27 PM (5 years ago)
Author:
ken@…

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13656, comment 4

    v1 v2  
    11I thought I'd already closed this (done in r23272), but it seems I hadn't updated the ticket.
    22
    3 For 06-5e-03 I see no point in making our own tarball.  A quick look at my notes for my own skylake i3 (which is normally powered off) suggest mine is 06-4e-03 so irrelevant to this. Looking at the Release notes for 20200609 mine is SKL-U/Y or SKL-U23e, affected machines are SKL-H/S. No idea what those suffixes mean, but oddly both are using the same microcode versions in the update.
     3For 06-4e-03 I see no point in making our own tarball.  A quick look at my notes for my own skylake i3 (which is normally powered off) suggest mine is 06-5e-03 so irrelevant to this. Looking at the Release notes for 20200609 mine is SKL-H/S, affected machines are SKL-U/Y or SKL-U23e. No idea what those suffixes mean, but oddly both 4e and 5e are using the same microcode versions in the update.
    44
    5 (Edit: I initially swapped 4e and 5e in tha paragraph, now corrected - mine is 4e)
     5(Edit: I became mistaken about which verion I had, and miscorrected it, should now be correct again)
    66
    77One of the Arch links from that issue [https://bugs.archlinux.org/task/66988] says that the problem on an i7-6600 was caused by using their -1 version of the microcode, and they already had a -2 which fixed it. According to their PKGBUILD [https://git.archlinux.org/svntogit/packages.git/plain/trunk/PKGBUILD?h=packages/intel-ucode] they are applying a git commit for 06-4e-03 over the shipped blob.