[Bug 237920] devcpu-data missing microcode Xeon v4

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237920

            Bug ID: 237920
           Summary: devcpu-data missing microcode Xeon v4
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: lampa at fit.vutbr.cz

Microcode 06-4f-01 for Xeon v4 family is not installed from
intel-ucode-with-caveats.

===>   devcpu-data-1.22 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by devcpu-data-1.22 for building
===>  Extracting for devcpu-data-1.22
=> SHA256 Checksum OK for amd64-microcode.20181214.tar.xz.
=> SHA256 Checksum OK for
intel-Intel-Linux-Processor-Microcode-Data-Files-1.22-microcode-20190514_GH0.tar.gz.
cp -f -p /usr/ports/sysutils/devcpu-data/files/Makefile
/usr/ports/sysutils/devcpu-data/files/ucode-split.c
/usr/ports/sysutils/devcpu-data/work/Intel-Linux-Processor-Microcode-Data-Files-microcode-20190514
/usr/bin/sed -i.bak 's|%%GH_TAGNAME%%|microcode-20190514|g'
/usr/ports/sysutils/devcpu-data/work/Intel-Linux-Processor-Microcode-Data-Files-microcode-20190514/Makefile
/bin/cat
/usr/ports/sysutils/devcpu-data/work/Intel-Linux-Processor-Microcode-Data-Files-microcode-20190514/Intel-Linux-Processor-Microcode-Data-Files-microcode-20190514/intel-ucode/*
/usr/ports/sysutils/devcpu-data/work/Intel-Linux-Processor-Microcode-Data-Files-microcode-20190514/Intel-Linux-Processor-Microcode-Data-Files-microcode-20190514/intel-ucode-with-caveats/*
>
/usr/ports/sysutils/devcpu-data/work/Intel-Linux-Processor-Microcode-Data-Files-microcode-20190514/intel-ucode.bin
===>  Patching for devcpu-data-1.22
===>  Configuring for devcpu-data-1.22
===>  Building for devcpu-data-1.22
--- ucode ---
mkdir -p mcodes
cd mcodes &&  for file in 
../Intel-Linux-Processor-Microcode-Data-Files-microcode-20190514/intel-ucode/[0-9,a-f][0-9,a-f]-[0-9,a-f][0-9,a-f]-[0-9,a-f][0-9,a-f];
do  ../ucode-split $file;  done

ucode-split doesn't look in intel-ucode-with-caveats (but cat does).

What is intel-ucode-with-caveats?

-- intel-ucode-with-caveats/ --
This directory holds microcode that might need special handling.
BDX-ML microcode is provided in directory, because it need special commits in
the Linux kernel, otherwise, updating it might result in unexpected system
behavior. OS vendors must ensure that the late loader patches (provided in
linux-kernel-patches) are included in the distribution before packaging the
BDX-ML microcode for late-loading.
-----

This ucode with caveats started with 20180703 version and it is used in current
BIOS microcode (Supermicro X10*) anyway. Mentioned linux kernel patches looks
like features re-detection after microcode update. The only Broadwell specific
patch is:
-----
Subject: x86/microcode/intel: Writeback and invalidate caches before updating
 microcode

Updating microcode is less error prone when caches have been flushed and
depending on what exactly the microcode is updating. For example, some
of the issues around certain Broadwell parts can be addressed by doing a
full cache flush.
-----

That is already handled in dev/cpuctl.c:

        /*
         * Perform update.  Flush caches first to work around seemingly
         * undocumented errata applying to some Broadwell CPUs.
         */
        wbinvd();

Is there any reason that this microcode update is still skipped?

-- 
You are receiving this mail because:
You are the assignee for the bug.