ASUS Crosshair IV Formula AMD Firmware Bug AMD-Vi IOAPIC not in IVRS table

Bug #1304655 reported by Jonathan Brier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

When running 14.04 on the Asus Crosshair IV Formula with the IOMMU enabled and AMD-virtualization enabled. The dmesg -l err shows:
[ 0.108481] [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
[ 0.108483] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found
[ 0.108484] AMD-Vi: Disabling interrupt remapping

This also occurs when loading with the the latest mainline kernel 3.14.0-031400-generic

Expected no dmesg errors

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-23-generic 3.13.0-23.45
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: jonathan 3204 F.... pulseaudio
 /dev/snd/controlC2: jonathan 3204 F.... pulseaudio
 /dev/snd/controlC1: jonathan 3204 F.... pulseaudio
 /dev/snd/controlC0: jonathan 3204 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 8 16:24:07 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=5aba1ebe-fee7-4527-b2a4-ac022892d6fd
InstallationDate: Installed on 2012-11-29 (494 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB:
 0 radeondrmfb
 1 radeondrmfb
 2 radeondrmfb
 3 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=c4ec6b3f-ea2f-479a-9ad4-f1eab2c84e9c ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-23-generic N/A
 linux-backports-modules-3.13.0-23-generic N/A
 linux-firmware 1.127
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-03-28 (10 days ago)
dmi.bios.date: 09/14/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Crosshair IV Formula
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd09/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCrosshairIVFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Jonathan Brier (brierjon) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
tags: added: kernel-bug-exists-upstream
penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-3.14 latest-bios-2101
removed: kernel-bug-exists-upstream
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.