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

[Backport release-24.05] microcodeIntel: 20240531 -> 20240813 #335589

Merged
merged 1 commit into from
Aug 29, 2024

Conversation

github-actions[bot]
Copy link
Contributor

Bot-based backport to release-24.05, triggered by a label in #334505.

  • Before merging, ensure that this backport is acceptable for the release.
    • Even as a non-commiter, if you find that it is not acceptable, leave a comment.

@github-actions github-actions bot added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Aug 18, 2024
@ofborg ofborg bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 1-10 10.rebuild-linux: 1 labels Aug 18, 2024
@evilmav
Copy link
Contributor

evilmav commented Aug 22, 2024

@Atemu do we need anything else to merge this?

@Atemu
Copy link
Member

Atemu commented Aug 22, 2024

No, just waiting a bit for complaints on unstable. If there's none in a week's time or so, we can merge.

Copy link
Member

@felixsinger felixsinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's get this in?

@evilmav
Copy link
Contributor

evilmav commented Aug 28, 2024

No, just waiting a bit for complaints on unstable. If there's none in a week's time or so, we can merge.

Isn't this the update fixing the self-destruct through elevated voltages issue on the 13th gen CPUs though? If so, delay might cause hardware degradation.

@felixsinger
Copy link
Member

No, just waiting a bit for complaints on unstable. If there's none in a week's time or so, we can merge.

Isn't this the update fixing the self-destruct through elevated voltages issue on the 13th gen CPUs though? If so, delay might cause hardware degradation.

No, that specific update is not applicable from OS level but it needs to be applied much earlier by the BIOS firmware. So Intel doesn't want to pubiish that update in order to avoid "confusion" and thus open source firmware projects like coreboot are not able to ship the update. See intel/Intel-Linux-Processor-Microcode-Data-Files#81

However, the new release also contains updates with security fixes.

@Atemu
Copy link
Member

Atemu commented Aug 29, 2024

Thanks for the ping, I haven't heard of any issues that could reasonably be caused by the microcode.

@Atemu Atemu merged commit 63cd8b8 into release-24.05 Aug 29, 2024
21 checks passed
@Atemu Atemu deleted the backport-334505-to-release-24.05 branch August 29, 2024 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 1-10 10.rebuild-linux: 1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants