This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2228670 - dmidecode shows Processor Upgrade: <OUT OF SPEC> in aws R7a insatnces
Summary: dmidecode shows Processor Upgrade: <OUT OF SPEC> in aws R7a insatnces
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: dmidecode
Version: 9.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lichen Liu
QA Contact: Jeff Bastian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-03 04:36 UTC by Frank Liang
Modified: 2023-09-25 19:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-25 19:06:20 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
r7a.medium_dmidecode_debug.bin (583 bytes, application/octet-stream)
2023-08-03 04:36 UTC, Frank Liang 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-9007 0 None Migrated None 2023-09-25 19:06:16 UTC
Red Hat Issue Tracker RHELPLAN-164300 0 None None None 2023-08-03 04:37:51 UTC

Description Frank Liang 2023-08-03 04:36:57 UTC 
Created attachment 1981395 [details]
r7a.medium_dmidecode_debug.bin

Description of problem:

During test R7a instances in 2227069, dmidecode shows Processor Upgrade: <OUT OF SPEC>.
Below is details:

From the dumped bin file, it seems that aws provides value in this field, so I guess it is because '4a' is new defined in smbios spec 3.7(Socket SP5).
Please double check. I guess the tool needs update accordingly.

00000100  45 43 32 00 00 04 2a 04  00 01 03 6b 02 11 0f a1  |EC2...*....k....|
00000110  00 ff fb 8b 17 03 89 64  00 74 0e 28 0a 41 4a 05  |.......d.t.(.AJ.|

$ dmidecode --from-dump r7a.medium_dmidecode_debug.bin -t 4
# dmidecode 3.4
Reading SMBIOS/DMI data from file r7a.medium_dmidecode_debug.bin.
SMBIOS 2.7 present.

Handle 0x0004, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 0
Type: Central Processor
Family: Zen
Manufacturer: Advanced Micro Devices, Inc.
ID: 11 0F A1 00 FF FB 8B 17
Signature: Family 25, Model 17, Stepping 1
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
HTT (Multi-threading)
Version: AMD EPYC 9R14
Voltage: 0.9 V
External Clock: 100 MHz
Max Speed: 3700 MHz
Current Speed: 2600 MHz
Status: Populated, Enabled
Upgrade: <OUT OF SPEC>
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: 0x0007
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 1
Core Enabled: 1
Thread Count: 1
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection

RHEL Version:
RHEL-9.2(5.14.0-284.18.1.el9_2.x86_64)

How reproducible:
100%

Steps to Reproduce:
1. launch aws r7a.medium instance
2. check dmidecode

Actual results:
Processor Upgrade is 'OUT OF SPEC'

Expected results:
no 'OUT OF SPEC' detected

Additional info:
- N/A
Comment 1 RHEL Program Management 2023-09-25 19:04:41 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2 RHEL Program Management 2023-09-25 19:06:20 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.