AMD [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vector 0x400 on another cpu

[Jonathan Brier]

After running the system testing default and hwsubmit tests I see in dmesg -l err the following firmware bug noted:

[Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vector 0x400 on another cpu
[ 1563.122513] [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 0 (MSR00000413=0xc000000001000000)
[ 1563.122514] [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vector 0x400 on another cpu
[ 1563.122515] [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 1 (MSRC0000408=0xc000000001000000)

This is a fresh install of 14.10 on an HP laptop.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-firmware 1.138.1
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 29 21:28:25 2015
Dependencies:

EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-29 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141015)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity
Dependencies:

DistroRelease: Ubuntu 14.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-29 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141015)
Package: linux-firmware 1.138.1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Tags: utopic
Uname: Linux 3.16.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Jonathan Brier (brierjon)]

apport information

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bryan Morrison (skeeter-mcbee-y)]

Also true for Ubuntu 14.04 on Lenovo G505s w/ AMD A10 5750M APU.

[Bryan Morrison (skeeter-mcbee-y)]

Bug is apparent in kernel 3.16 and 3.17 as well.

[jgddg cyfszsad (fadioadfgoa-deactivatedaccount)]

Hi, I am using Arch linux with kernel 4.2 and the issue is still present. It cause my one core to run 100% load withou any process using it (htop) and draws my battery quickly :( I didn't had an issue with kernel 3.13

AMD A8-4500M APU with Radeon(tm) HD Graphics

Log

```
Nov 26 16:30:25 NORMANDY kernel: ACPI: Preparing to enter system sleep state S3
Nov 26 16:30:25 NORMANDY kernel: ACPI : EC: EC stopped
Nov 26 16:30:25 NORMANDY kernel: PM: Saving platform NVS memory
Nov 26 16:30:25 NORMANDY kernel: Disabling non-boot CPUs ...
Nov 26 16:30:25 NORMANDY kernel: smpboot: CPU 1 is now offline
Nov 26 16:30:25 NORMANDY kernel: smpboot: CPU 2 is now offline
Nov 26 16:30:25 NORMANDY kernel: smpboot: CPU 3 is now offline
Nov 26 16:30:25 NORMANDY kernel: ACPI: Low-level resume complete
Nov 26 16:30:25 NORMANDY kernel: ACPI : EC: EC started
Nov 26 16:30:25 NORMANDY kernel: PM: Restoring platform NVS memory
Nov 26 16:30:25 NORMANDY kernel: Using NULL legacy PIC
Nov 26 16:30:25 NORMANDY kernel: LVT offset 0 assigned for vector 0x400
Nov 26 16:30:25 NORMANDY kernel: [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vect
Nov 26 16:30:25 NORMANDY kernel: [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 0 (MSR00000413=0xc000000001000000)
Nov 26 16:30:25 NORMANDY kernel: [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vect
Nov 26 16:30:25 NORMANDY kernel: [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 1 (MSRC0000408=0xc000000001000000)
Nov 26 16:30:25 NORMANDY kernel: Enabling non-boot CPUs ...
Nov 26 16:30:25 NORMANDY kernel: x86: Booting SMP configuration:
Nov 26 16:30:25 NORMANDY kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
Nov 26 16:30:25 NORMANDY kernel: [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
Nov 26 16:30:25 NORMANDY kernel: cache: parent cpu1 should not be sleeping
Nov 26 16:30:25 NORMANDY kernel: CPU1 is up
Nov 26 16:30:25 NORMANDY kernel: smpboot: Booting Node 0 Processor 2 APIC 0x12
Nov 26 16:30:25 NORMANDY kernel: [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
Nov 26 16:30:25 NORMANDY kernel: cache: parent cpu2 should not be sleeping
Nov 26 16:30:26 NORMANDY kernel: CPU2 is up
Nov 26 16:30:26 NORMANDY kernel: smpboot: Booting Node 0 Processor 3 APIC 0x13
Nov 26 16:30:26 NORMANDY kernel: [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
Nov 26 16:30:26 NORMANDY kernel: cache: parent cpu3 should not be sleeping
Nov 26 16:30:26 NORMANDY kernel: CPU3 is up
Nov 26 16:30:26 NORMANDY kernel: ACPI: Waking up from system sleep state S3
Nov 26 16:30:26 NORMANDY kernel: ohci-pci 0000:00:12.0: System wakeup disabled by ACPI
Nov 26 16:30:26 NORMANDY kernel: ohci-pci 0000:00:13.0: System wakeup disabled by ACPI
Nov 26 16:30:26 NORMANDY kernel: xhci_hcd 0000:00:10.0: System wakeup disabled by ACPI
Nov 26 16:30:26 NORMANDY kernel: xhci_hcd 0000:00:10.1: System wakeup disabled by ACPI
Nov 26 16:30:26 NORMANDY kernel: PM: noirq resume of devices complete after 14.220 msecs
Nov 26 16:30:26 ...

[Linux (palswim)]

Supposedly, [bug #1152484](https://bugs.launchpad.net/bugs/1152484) addresses "AMD family 10h cpus". I am having this issue with the Trinity CPU (15h), the same processor from this bug report, which [according to a user who submitted a kernel patch for the other bug](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152484/comments/20) indicates a slightly different bug.

Perhaps we need to re-open this bug and address the actual firmware bug and system slowness that results from this issue.