Bug 1527310

Summary:	Microcode on AMD family 16h processors not updated early in the boot process [rhel-7.2.z]
Product:	Red Hat Enterprise Linux 7	Reporter:	Oneata Mircea Teodor <toneata>
Component:	dracut	Assignee:	Lukáš Nykrýn <lnykryn>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	urgent	Docs Contact:	Marie Hornickova <mdolezel>
Priority:	high
Version:	7.3	CC:	aarapov, bbreard, dhoward, dracut-maint-list, harald, jbastian, jcm, jonteh, jstodola, jsynacek, lnykryn, pmatouse, poros, ppandit, toneata
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	dracut-033-360.el7_2.3	Doc Type:	Bug Fix
Doc Text:	Previously, the dracut tool incorrectly copied the AMD family 15h microcode into the Initial RAM File System (initramfs) on systems with AMD family 16h processors. Consequently, the microcode on such systems was not updated early enough in the boot process. This update fixes dracut to copy the correct AMD family 16h microcode into initramfs, and the microcode is now correctly updated in the early phase of the boot process.	Story Points:	---
Clone Of:	1476039	Environment:
Last Closed:	2018-01-08 16:29:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1476039
Bug Blocks:	1519780

Description Oneata Mircea Teodor 2017-12-19 07:45:58 UTC

This bug has been copied from bug #1476039 and has been proposed to be backported to 7.2 z-stream (EUS).

Comment 4 Lukáš Nykrýn 2018-01-04 10:30:01 UTC

*** Bug 1529310 has been marked as a duplicate of this bug. ***

Comment 5 Jan Stodola 2018-01-04 12:15:35 UTC

Reproduced on RHEL-7.2 GA
Verified with dracut-033-360.el7_2.3, the correct microcode was included in the early CPIO image depending on the CPU family.

Moving to VERIFIED.

Comment 8 errata-xmlrpc 2018-01-08 16:29:28 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0062