Linux (Debian/Ubuntu) guest shows CPU firmware bug on startup

[richard_berger]

Hello,

I've got a new PC with a AMD Ryzon 5900HX CPU. When I boot up a linux guest (tested with Debian 11 & Ubuntu 20/21), I see the following messages on startup:

[ 0.006318] [Firmware Bug]: cpu 1, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.006318] [Firmware Bug]: cpu 2, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.006318] [Firmware Bug]: cpu 3, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.006318] [Firmware Bug]: cpu 4, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.006318] [Firmware Bug]: cpu 5, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.006318] [Firmware Bug]: cpu 6, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.006318] [Firmware Bug]: cpu 7, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu

With my very aged old PC with Intel CPU I don't get these messages with the same VMs.

Is this critical, or can this be ignored? Any idea how to fix this?

Any tip is appreciated.

PS: I am using VMware Workstation Pro 16.2.1 build-18811642

[BonnY_8]

Same issue, have you found any solutions to this cuz I get huge performance drops from the moment this started appearing, mostly noticeable in firefox when scrolling(impossible task to do). I have the latest ver of vmware and I am using win 11 as a host and Linux in vm, also I have good pc. 

dmesg | grep -i firmware
[ 0.000000] [Firmware Bug]: TSC doesn't count with P0 frequency!
[ 0.404594] [Firmware Bug]: cpu 0, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.021941] [Firmware Bug]: cpu 1, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.021941] [Firmware Bug]: cpu 2, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.021941] [Firmware Bug]: cpu 3, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.021941] [Firmware Bug]: cpu 4, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.021941] [Firmware Bug]: cpu 5, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.021941] [Firmware Bug]: cpu 6, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.021941] [Firmware Bug]: cpu 7, try to use APIC520 (LVT offset 2) for vector 0xf4, but the register is already in use for vector 0x0 on this cpu
[ 0.530114] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

[totalnoob]

I have this exact issue.

I am wondering if it could have anything to do with the amount of cpu usage we have allocated to various vms or interference with host tasks? 

Either way hopefully a fix turns up. It is so hard to type in the terminal it keeps spasming out. example I press p once and then I get ppppppppppppp. 

VMWARE   16.2.3 build-

[richard_berger]

No, unfortunately I did not find a solution yet. I don't think there can be much done on my site, so this must be fixed in VMware Workstation I guess.

[flegma9]

Hi everyone, has this issue been solve at your side?

I'm using Workstation Pro 16.2.4 build-20089737 and I realized lately (after the last upated) that my booting time has been tripled AND the above firmeware bugs started jumping up. 

I did try to install a fresh new VM guest OS, with fresh installed vm tools and it takes forever to boot with firmware bug messeges.

Any suggestion for the workaround?

Thx

[richard_berger]

Update: This is still an issue in VMware Workstation 17 build 20800274 ☹️

[joedon31]

Thanks for the Workstation 17 update.  I've been getting these errors on Workstation 16.2.x since the get-go with Debian 11.  I'm also getting a lot of Kernel panics that freeze the system for a few minutes occasionally.  I just upgraded to 16.2.5 and it still persists.

I saw Workstation 17 'officially' supports Debian 11 so I was considering upgrading to mitigate these errors.  I'm glad I didn't spend the $$$ to upgrade

I'm running an ASUS ROG X-399 e-Gaming mobo with a Threadripper 2990wx and 128GB RAM.   Base OS is Windows 11 (only due to chipset driver issues with any Linux Distro).

I don't understand why this is such huge issue with AMD chipsets...  Linus uses a threadripper for cryin' out loud....  😕