Bug 82241 - IOAPIC Firemware Bug
Summary: IOAPIC Firemware Bug
Status: CLOSED DOCUMENTED
Alias: None
Product: ACPI
Classification: Unclassified
Component: BIOS (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_bios
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-12 14:49 UTC by Leonidas Spyropoulos
Modified: 2014-09-22 13:32 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.15.8
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Leonidas Spyropoulos 2014-08-12 14:49:14 UTC
Description: Kernel logs reports the following Firmware bug:
[...]
Aug 12 08:16:43 tiamat kernel:[Firmware Bug]: AMD-Vi: IOAPIC[9] not in IVRS table
Aug 12 08:16:43 tiamat kernel: [Firmware Bug]: AMD-Vi: IOAPIC[10] not in IVRS table
Aug 12 08:16:43 tiamat kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found
Aug 12 08:16:43 tiamat kernel: AMD-Vi: Disabling interrupt remapping
[...]

Additional info:
My motherboard is ASUS Crosshair V with an AMD-FX 8200. with IOACPI Enabled. Inside the BIOS there's also IOACPI Mode which I can set to 'Disabled' or '64Mb'. In both cases the error occurs. If I disable the IOACPI complete my PC freeze - no keyboard input.

Kernel package version
~$ pacman -Qi linux
Name : linux
Version : 3.15.8-1
Description : The Linux kernel and modules
Architecture : x86_64
URL : http://www.kernel.org/
Licenses : GPL2

linux-firmware package:

$ pacman -Qi linux-firmware
Name : linux-firmware
Version : 20140603.a4f3bc0-1
Description : Firmware files for Linux
Architecture : any
URL : http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git;a=summary
Licenses : GPL2 GPL3 custom

Steps to reproduce:
Reboot

Archlinux reference bug: https://bugs.archlinux.org/task/41534
Comment 1 Leonidas Spyropoulos 2014-08-12 14:50:19 UTC
If this is wrong category apologies - didn't know what to pick.
Comment 2 Alan 2014-08-21 17:54:53 UTC
Firmware bugs in this case are referring to the BIOS. The kernel is discovering the BIOS tables appear to be bogus and warning you. It'll do it's best to work around these anyway

Note You need to log in before you can comment on or make changes to this bug.