Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

microcodeIntel: 20191113 -> 20191115 #73497

Merged
merged 2 commits into from Nov 27, 2019

Conversation

dtzWill
Copy link
Member

@dtzWill dtzWill commented Nov 16, 2019

Motivation for this change

https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20191115

cc #73383 and related.

Backport please!

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@FRidh
Copy link
Member

FRidh commented Nov 16, 2019

Keeping up with their microcode changes is like a dayjob in itself 😛

@mweinelt
Copy link
Member

Tested on 19.09 and works for me on an 8700k.

[    0.000000] microcode: microcode updated early to revision 0xca, date = 2019-10-03

The date seems off, but that's probably due to Intels release process. It clearly updated the microcode though.

@andir andir merged commit 2930ea5 into NixOS:master Nov 27, 2019
@andir
Copy link
Member

andir commented Nov 27, 2019

Backported to 19.09: ca9f709

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants