cancel
Showing results for 
Search instead for 
Did you mean: 

PC Processors

alzinati
Journeyman III

CPU uncorrected error

I have a server that has 2 CPU sockets. The server got rebooted because of uncorrected error. 

The question is, how do I identify which CPU? 

please see the logs below 

kernel: BERT: Error records from previous boot:
kernel: [Hardware Error]: event severity: fatal
kernel: [Hardware Error]: Error 0, type: fatal
kernel: [Hardware Error]: fru_text: ProcessorError
kernel: [Hardware Error]: section_type: IA32/X64 processor error
kernel: [Hardware Error]: Local APIC_ID: 0x63
kernel: [Hardware Error]: CPUID Info:
kernel: [Hardware Error]: 00000000: 00830f10 00000000 63400800 00000000
kernel: [Hardware Error]: 00000010: 76d8320b 00000000 178bfbff 00000000
kernel: [Hardware Error]: 00000020: 00000000 00000000 00000000 00000000
kernel: [Hardware Error]: Error Information Structure 0:
kernel: [Hardware Error]: Error Structure Type: cache error
kernel: [Hardware Error]: Check Information: 0x000000000602001f
kernel: [Hardware Error]: Transaction Type: 2, Generic
kernel: [Hardware Error]: Operation: 0, generic error
kernel: [Hardware Error]: Level: 0
kernel: [Hardware Error]: Processor Context Corrupt: true
kernel: [Hardware Error]: Uncorrected: true
kernel: [Hardware Error]: Context Information Structure 0:
kernel: [Hardware Error]: Register Context Type: MSR Registers (Machine Check and other MSRs)
kernel: [Hardware Error]: Register Array Size: 0x0050
kernel: [Hardware Error]: MSR Address: 0xc0002051
kernel: [Hardware Error]: Register Array:
kernel: [Hardware Error]: 00000000: bea0000000000108 0001ffff959a666c
kernel: [Hardware Error]: 00000010: d01c0ff500000000 0000000300000079
kernel: [Hardware Error]: 00000020: 000500b000000000 000000004d000000
kernel: [Hardware Error]: 00000030: 0000000000000000 0000000000000000
kernel: [Hardware Error]: 00000040: 0000000000000000 0000000000000000
kernel: [Hardware Error]: Context Information Structure 1:
kernel: [Hardware Error]: Register Context Type: Unclassified Data
kernel: [Hardware Error]: Register Array Size: 0x0010
kernel: [Hardware Error]: Register Array:
kernel: [Hardware Error]: 00000000: 00000000 00000000 00000000 00000000
kernel: rtc_cmos 00:01: setting system clock to 2023-08-09 08:47:03 UTC (1691570823)

 

----------------------------------------------------------------------------------------------------------------------------------------

lscpu:

rchitecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Thread(s) per core: 1
Core(s) per socket: 64
Socket(s): 2
NUMA node(s): 8
Vendor ID: AuthenticAMD
BIOS Vendor ID: Advanced Micro Devices, Inc.
CPU family: 23
Model: 49
Model name: AMD EPYC 7702 64-Core Processor
BIOS Model name: AMD EPYC 7702 64-Core Processor
Stepping: 0
CPU MHz: 1845.170
CPU max MHz: 2183.5930
CPU min MHz: 1500.0000
BogoMIPS: 3992.69
Virtualization: AMD-V
L1d cache: 32K
L1i cache: 32K
L2 cache: 512K
L3 cache: 16384K
NUMA node0 CPU(s): 0-15
NUMA node1 CPU(s): 16-31
NUMA node2 CPU(s): 32-47
NUMA node3 CPU(s): 48-63
NUMA node4 CPU(s): 64-79
NUMA node5 CPU(s): 80-95
NUMA node6 CPU(s): 96-111
NUMA node7 CPU(s): 112-127
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr wbnoinvd amd_ppin arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca sme sev sev_es

0 Likes
2 Replies
GrahamMax
Journeyman III

Depending on the operating system running on the server, there might be utilities that can help identify hardware issues. For example, on Linux, you can use commands like lscpu to display CPU information and dmesg to view kernel messages that might provide insights into the error.

0 Likes
GrahamMax
Journeyman III

Resetting the motherboard's CMOS can sometimes help when switching to a new CPU. This will reset all BIOS settings to default. You can usually do this by either using a CMOS reset button on the motherboard (if available), or by temporarily removing the CMOS battery for a few minutes while the PC is unplugged.

0 Likes