You are not logged in.

#1 2016-12-26 11:59:00

Roken
Member
From: South Wales, UK
Registered: 2012-01-16
Posts: 1,251

CPU Firmware Bug

Should I worry about this. Early boot reports:

[Firmware Bug]: CPU2: APIC id mismatch. Firmware: 2 CPUID: 3

The CPU numbers vary.

System boots, and /proc/cpuinfo seems fine (restricted to CPU2 & 3, since they were the ones reported on this boot)

processor	: 2
vendor_id	: AuthenticAMD
cpu family	: 16
model		: 4
model name	: AMD Phenom(tm) II X4 965 Processor
stepping	: 3
microcode	: 0x10000c8
cpu MHz		: 3400.000
cache size	: 512 KB
physical id	: 0
siblings	: 4
core id		: 1
cpu cores	: 4
apicid		: 2
initial apicid	: 2
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
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 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid eagerfpu pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save
bugs		: tlb_mmatch apic_c1e fxsave_leak sysret_ss_attrs null_seg
bogomips	: 6802.45
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor	: 3
vendor_id	: AuthenticAMD
cpu family	: 16
model		: 4
model name	: AMD Phenom(tm) II X4 965 Processor
stepping	: 3
microcode	: 0x10000c8
cpu MHz		: 3400.000
cache size	: 512 KB
physical id	: 0
siblings	: 4
core id		: 3
cpu cores	: 4
apicid		: 3
initial apicid	: 3
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
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 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid eagerfpu pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save
bugs		: tlb_mmatch apic_c1e fxsave_leak sysret_ss_attrs null_seg
bogomips	: 6802.44
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

If I should worry, is there a fix?


Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

Offline

#2 2016-12-26 13:17:05

seth
Member
Registered: 2012-09-03
Posts: 50,008

Offline

#3 2016-12-26 14:35:18

Roken
Member
From: South Wales, UK
Registered: 2012-01-16
Posts: 1,251

Re: CPU Firmware Bug

Thanks, Seth, though that patch appears to be for virtual machines. I run Arch natively as the system host.

Having said that, I only noticed the problem after a VM problem in Windows guest not recognising either keyboard or mouse, but grabbing both nevertheless, which meant I couldn't interact with the VM, nor switch to the host Arch and my only escape was a hard reset.

I have tried a complete powerdown since, which I would expect to resolve any such problem, though no.

Mind you, that's only when I noticed, and not necessarily when it first appeared.

There are no ill effects, as far as I can tell.


Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

Offline

#4 2016-12-26 14:49:15

seth
Member
Registered: 2012-09-03
Posts: 50,008

Re: CPU Firmware Bug

"arch/x86/kernel/cpu/common.c" ;-)
The covered issue that introduces this error message seems to have been troublesome on VMs (only), but you now get that whenever the APIC id doesn't fit.

The point is that this has (very likely) been an incident on that system forever, just now you get a warning while silently fixed before - AMD might just as well "violate" the spec and the patch rather intel-centric.

Offline

#5 2016-12-26 15:17:51

Roken
Member
From: South Wales, UK
Registered: 2012-01-16
Posts: 1,251

Re: CPU Firmware Bug

So, in view of no discernible effects, I can just ignore, then?


Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

Offline

#6 2016-12-26 15:34:27

seth
Member
Registered: 2012-09-03
Posts: 50,008

Re: CPU Firmware Bug

The odds that your CPU broke around the same time when this was added to the kernel (reliably, reproducably and in exactly this matter ;-) are pretty low, so if the CPU was good in the past, it's good now.
Other users of that CPU (family) could add some data to this (whether it's reported there as well, so it's just a general problem)

What's the error message for the other core? 3/3/4?

BTW, sure this isn't CPU0 & CPU1? - apicid and initial apicid have the same values in the pasted cpuinfo.

Offline

#7 2016-12-26 18:13:48

Roken
Member
From: South Wales, UK
Registered: 2012-01-16
Posts: 1,251

Re: CPU Firmware Bug

The precise arrangement differes between boots. For example, on the current boot:

[Mon Dec 26 18:07:38 2016] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 1 CPUID: 2
[Mon Dec 26 18:07:38 2016] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 2 CPUID: 3
[Mon Dec 26 18:07:38 2016] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 3 CPUID: 1

I'm thinking that the fact cpuinfo reports it correctly it's a warning that gets fixed.

EDIT: Ahh, wait, cpuinfo now is also mismatched. coreid and apicid are per the error.

Last edited by Roken (2016-12-26 18:15:44)


Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

Offline

#8 2016-12-27 21:03:13

DeadMetaler
Member
Registered: 2016-03-16
Posts: 42

Re: CPU Firmware Bug

I have a same issue with "firmware bug" after upgrading from 4.8 to 4.9 kernel.
Also tried 4.10rc1 and there is no "firmware bug" with that kernel. Maybe upcoming 4.9.1 release will fix a problem.

Offline

Board footer

Powered by FluxBB