Bug 1583720
| Summary: | include AMD CPUID 0x00610f01 in RHEL-7 linux-firmware | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Dilip Soman <dsoman> | |
| Component: | linux-firmware | Assignee: | Bruno Meneguele <brdeoliv> | |
| Status: | CLOSED ERRATA | QA Contact: | Rachel Sibley <rasibley> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.6 | CC: | jbastian, rasibley, salmy, skozina, toneata | |
| Target Milestone: | rc | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1584192 1585936 1585937 1585938 1585939 (view as bug list) | Environment: | ||
| Last Closed: | 2018-10-30 10:11:33 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 1584192, 1585936, 1585937, 1585938, 1585939 | |||
|
Description
Dilip Soman
2018-05-29 14:28:02 UTC
ALL TESTS PASSED Verified the missing 0x00610f01 CPUID is now included in the microcode_amd_fam15h.bin file using the latest official linux-firmware build: $ wget linux-firmware-20180717-67.git8d69bab.el7.noarch.rpm ... $ rpm2cpio linux-firmware-20180717-67.git8d69bab.el7.noarch.rpm | cpio -ivd $ ./read-amd-ucode usr/lib/firmware/amd-ucode/microcode_amd_fam15h.bin usr/lib/firmware/amd-ucode/microcode_amd_fam15h.bin: CPUID: 0x00600f12, Patch-ID 0x0600063e, Date: 2018-02-07 usr/lib/firmware/amd-ucode/microcode_amd_fam15h.bin: CPUID: 0x00600f20, Patch-ID 0x06000852, Date: 2018-02-06 usr/lib/firmware/amd-ucode/microcode_amd_fam15h.bin: CPUID: 0x00610f01, Patch-ID 0x06001119, Date: 2012-07-13 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:3119 |