Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] intel-ucode: restore working firmware blob 06-55-04 to avoid reboot bug
Date: Mon, 20 Jan 2020 04:21:37 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18412@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

There is a new pull request by ahesford against master on the void-packages repository

https://github.com/ahesford/void-packages intel-ucode
https://github.com/void-linux/void-packages/pull/18412

intel-ucode: restore working firmware blob 06-55-04 to avoid reboot bug
Firmware blob 06-55-04 in intel-ucode versions > 20190918 causes lockups when warm-rebooting certain Xeon and HEDT CPUs. ([Upstream issue](https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/21)) This PR replaces the affected blob with the last known good version.

A patch file from https://github.com/void-linux/void-packages/pull/18412.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-intel-ucode-18412.patch --]
[-- Type: text/x-diff, Size: 1898 bytes --]

From fa47363814844cd84b801ab5a030d9f84cbce114 Mon Sep 17 00:00:00 2001
From: "Andrew J. Hesford" <ajh@sideband.org>
Date: Sun, 19 Jan 2020 22:11:32 -0500
Subject: [PATCH] intel-ucode: restore working firmware blob 06-55-04 to avoid
 reboot bug

---
 srcpkgs/intel-ucode/template | 17 +++++++++++++----
 1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/intel-ucode/template b/srcpkgs/intel-ucode/template
index 3304fac8db9..5221acdef48 100644
--- a/srcpkgs/intel-ucode/template
+++ b/srcpkgs/intel-ucode/template
@@ -1,18 +1,27 @@
 # Template file for 'intel-ucode'
 pkgname=intel-ucode
 version=20191115
-revision=1
+revision=2
 archs="i686* x86_64*"
-wrksrc="Intel-Linux-Processor-Microcode-Data-Files-microcode-${version}"
+_wrksrc_base="Intel-Linux-Processor-Microcode-Data-Files-microcode"
+wrksrc="${_wrksrc_base}-${version}"
 short_desc="Microcode update files for Intel CPUs"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="custom: Proprietary"
 homepage="https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files"
-distfiles="https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/archive/microcode-${version}.tar.gz"
-checksum=14b26d27be70774948b8cb582e298f5317263b8b8bb1fe8e41260eae54f531dc
+distfiles="${homepage}/archive/microcode-${version}.tar.gz
+ ${homepage}/archive/microcode-20190918.tar.gz"
+checksum="14b26d27be70774948b8cb582e298f5317263b8b8bb1fe8e41260eae54f531dc
+ 2b6b728d351764dfbf6a9763ac96ae7e04085f382a309fed3abc0118f094c943"
 repository=nonfree
 
 do_install() {
+	# Replace buggy 06-55-04 microcode with last known good version
+	_bad_ucode="intel-ucode/06-55-04"
+	rm "$_bad_ucode"
+	cp "../${_wrksrc_base}-20190918/$_bad_ucode" "$_bad_ucode"
+
+	# Rest of process continues as normal
 	vmkdir usr/lib/firmware/intel-ucode
 	vcopy "intel-ucode/*" usr/lib/firmware/intel-ucode
 	vmkdir usr/lib/dracut/dracut.conf.d

             reply	other threads:[~2020-01-20  3:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20  3:21 voidlinux-github [this message]
2020-01-25  8:04 ` [PR PATCH] [Merged]: " voidlinux-github

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18412@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).