Bug 867078 - RHEL 6.4:Please include AMD microcode for processor families 10h-14h(microcode_amd.bin) and 15h(microcode_amd_fam15h.bin)
RHEL 6.4:Please include AMD microcode for processor families 10h-14h(microcod...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: microcode_ctl (Show other bugs)
6.4
x86_64 Linux
unspecified Severity high
: rc
: 6.4
Assigned To: Anton Arapov
Jeff Bastian
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-16 13:56 EDT by Kim Naru
Modified: 2014-06-18 04:03 EDT (History)
3 users (show)

See Also:
Fixed In Version: microcode_ctl-1.17-14.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-21 03:52:31 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Tar file containing : microcode_amd.bin,microcode_fam15h.bin (20.00 KB, application/octet-stream)
2012-10-16 13:56 EDT, Kim Naru
no flags Details

  None (edit)
Description Kim Naru 2012-10-16 13:56:24 EDT
Created attachment 628308 [details]
Tar file containing : microcode_amd.bin,microcode_fam15h.bin

Description of problem:
The the two microcode files are:

microcode_amd.bin    - Family  10h-14h
microcode_fam15h.bin - Family 15h.


I had opened bug  #866700 for RHEL 7.0 with the only difference being the version number.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 8 errata-xmlrpc 2013-02-21 03:52:31 EST
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.

http://rhn.redhat.com/errata/RHBA-2013-0348.html

Note You need to log in before you can comment on or make changes to this bug.