On Mon, Feb 19, 2018 at 01:18:59AM -0600, listreader wrote:
On Sun, 18 Feb 2018 23:34:07 -0600 listreader <suselist@cableone.net> wrote:
I've had 20180108-16.1 ucode-intel on kaby lake under 42.3 since 11-Jan and nothing has seemed out of place. Dell today (18-Feb) released a new BIOS for my T3620 for "Update to the latest CPU microcode to address CVE-2017-5715 and associated Intel Reboot issue." I haven't installed this yet (the package self-installs itself through the existing BIOS boot menu so the OS is not relevant to the install).
Sorry if this is a dumb question but: am I safe to assume that your rollback from 20180108-16.1 ucode-intel to 20170707-10.1 tomorrow will have no effect on this new Dell burn under 42.3?
I burned the new Dell BIOS which gives me microcode:
sig=0x906e9, pf=0x2, revision=0x84
and the 'early microcode' load doesn't happen now under 42.3 so my question is moot, I suppose. 0x84 is so new that it's not even in the Intel 12-Feb "Microcode Revision Guidance" pdf.
The rollback and generally the ucode-intel package microcode loading does not override what the BIOS has already done. ucode-intel will also only upgrade the version and not downgrade if the BIOS has a newer ucode version embedded. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org