Bug 2232284 - missing update for AMD 19h fam cpus.
Summary: missing update for AMD 19h fam cpus.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: linux-firmware
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-16 07:00 UTC by customercare
Modified: 2023-08-16 09:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 08:47:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description customercare 2023-08-16 07:00:43 UTC
Description of problem:

According to the spectre-meltdown-checker for a :

vendor_id	: AuthenticAMD
cpu family	: 25
model		: 33
model name	: AMD Ryzen 5 5600X 6-Core Processor
stepping	: 0
microcode	: 0xa201005

the cpu did not get the newest microcode:

 * CPU microcode is the latest known available version:  NO  
 (latest version is 0xa201016 dated 2021/04/08 according to builtin firmwares DB v222+i20220208)

So this :

Name        : linux-firmware
Version     : 20230625
Release     : 151.fc37

needs an update for the 19h fam microcode blob.

Comment 1 Fedora Release Engineering 2023-08-16 08:06:48 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 2 Peter Robinson 2023-08-16 08:47:03 UTC
> Name        : linux-firmware
> Version     : 20230625
> Release     : 151.fc37
> 
> needs an update for the 19h fam microcode blob.

The AMD microcode updates were included in both 152 and then 153 so please ensure you actually have all available updates applied before filing bugs!

Details in the last update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-755b8bb6db

Comment 3 customercare 2023-08-16 09:00:16 UTC
Your update is not in stable, it's still in TESTING!

Comment 4 Peter Robinson 2023-08-16 09:04:16 UTC
(In reply to customercare from comment #3)
> Your update is not in stable, it's still in TESTING!

It is only is testing on F-37, it's stable on F38 and later releases, you reported against F39. There are instructions on the F-37 page for how to pull it in from testing.


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