Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Results 1 to 4 of 4

Thread: Ubuntu 13.10 dmesg throws "[Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table"

  1. #1
    Vidkoym7 is offline Junior Member
    Join Date
    Oct 2013
    Location
    USA
    Posts
    5

    Default Ubuntu 13.10 dmesg throws "[Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table"

    Ubuntu 13.10 dmesg throws:
    [ 0.021054] [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
    [ 0.021057] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found
    [ 0.021058] AMD-Vi: Disabling interrupt remapping
    [ 0.893016] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
    [ 0.893017] AMD-Vi: Extended features: PreF PPR GT IA
    [ 0.904833] AMD-Vi: Lazy IO/TLB flushing enabled
    [ 12.199193] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
    [ 12.199238] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/LNXVIDEO:00/input/input5
    [ 12.410595] kvm: Nested Virtualization enabled

    Possibly related, VirtualBox 4.3 w/ extensions segfaults when PCI devices are passed through this Ubuntu hypervisor to guest machine-won't even show BIOS text. Runs fine without passthrough, minus the showstopper that I now lack passthrough.

    Ideas as to cause? Missing table? Can I somehow force a table into my hypervisor's boot?

    Motherboard: ASRock FM2A88X Extreme6+
    BIOS: P1.60.
    Hypervisor OS: Ubuntu 13.10.
    CPU: AMD A8.
    IOMMU enabled.
    Guest OS: Not relevant (VM crashes even with no boot drive)

    Thanks
    Last edited by Vidkoym7; 10-25-2013 at 08:24 PM. Reason: botched the VirtualBox version

  2. #2
    Vidkoym7 is offline Junior Member
    Join Date
    Oct 2013
    Location
    USA
    Posts
    5

    Default Re: Ubuntu 13.10 dmesg throws "[Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table"

    Xen hypervisor with this board brings up a similar message:

    (XEN) ACPI: RSDP 000F04A0, 0024 (r2 ALASKA)
    (XEN) ACPI: XSDT AC026080, 007C (r1 ALASKA A M I 1072009 AMI 10013)
    (XEN) ACPI: FACP AC02C210, 010C (r5 ALASKA A M I 1072009 AMI 10013)
    (XEN) ACPI Warning (tbfadt-0464): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000000/1 [20070126]
    (XEN) ACPI: DSDT AC026190, 6079 (r2 ALASKA A M I 0 INTL 20051117)
    (XEN) ACPI: FACS AC053080, 0040
    (XEN) ACPI: APIC AC02C320, 0072 (r3 ALASKA A M I 1072009 AMI 10013)
    (XEN) ACPI: FPDT AC02C398, 0044 (r1 ALASKA A M I 1072009 AMI 10013)
    (XEN) ACPI: MCFG AC02C3E0, 003C (r1 ALASKA A M I 1072009 MSFT 10013)
    (XEN) ACPI: HPET AC02C420, 0038 (r1 ALASKA A M I 1072009 AMI 5)
    (XEN) ACPI: AAFT AC02C458, 02FD (r1 ALASKA OEMAAFT 1072009 MSFT 97)
    (XEN) ACPI: IVRS AC02C758, 0068 (r2 AMD BANTRY 1 AMD 0)
    (XEN) ACPI: SSDT AC02C7C0, 0D40 (r1 AMD BANTRY 1 AMD 1)
    (XEN) ACPI: SSDT AC02D500, 04B7 (r2 AMD BANTRY 1 MSFT 4000000)
    (XEN) ACPI: CRAT AC02D9B8, 0528 (r1 AMD BANTRY 1 AMD 1)
    (XEN) ACPI: SSDT AC02DEE0, 1115 (r1 AMD CPMCMN 1 INTL 20051117)
    (XEN) System RAM: 7600MB (7783132kB)
    (XEN) Domain heap initialised
    (XEN) ACPI: 32/64X FACS address mismatch in FADT - ac053080/0000000000000000, using 32
    (XEN) Processor #16 5:0 APIC version 16
    (XEN) Processor #17 5:0 APIC version 16
    (XEN) Processor #18 5:0 APIC version 16
    (XEN) Processor #19 5:0 APIC version 16
    (XEN) IOAPIC[0]: apic_id 5, version 33, address 0xfec00000, GSI 0-23
    (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
    (XEN) Using scheduler: SMP Credit Scheduler (credit)
    (XEN) Detected 3194.246 MHz processor.
    (XEN) Initing memory sharing.
    (XEN) xstate_init: using cntxt_size: 0x3c0 and states: 0x4000000000000007
    (XEN) PCI: Not using MCFG for segment 0000 bus 00-ff
    (XEN) IVHD Error: no information for IO-APIC 0x5
    (XEN) AMD-Vi: Error initialization
    (XEN) I/O virtualisation disabled

    hmm.

  3. #3
    - wardog -'s Avatar
    - wardog - is offline Spam Killer
    Join Date
    Nov 2012
    Location
    USA
    Posts
    2,128

    Default Re: Ubuntu 13.10 dmesg throws "[Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table"

    Hmmm, I just installed MS Hyper-V 2012 on my FM2A88X Extreme6+ (BIOS 1.30)

    Can you direct me where I might check if this is repeatable on/in Hyper-V?

    I'd be open to installing either of the hypervisors you've tried on my BIOS 1.30 board for that matter. Just that I have Hyper-V installed atm.
    #1 - Please, when seeking help, enter the make and model of ALL parts that your system is comprised of in your Signature, or at least the model #'s in your System Specs, then "Save' it.
    ____If you are overclocking, underclocking, or undervolting any parts, informing us of this and their values would prove beneficial in helping you.

    #2 - G.Skill RAM Configurator for your boardSamsung Memory for your boardLatest AMD Chipset Drivers/WindowsLatest AMD Graphics Drivers/WindowsLatest Intel Drivers

    #3 - Please use the PSU Calculator found HERE to determine if it might be the PSU causing issues. I do(Lifetime PRO ver.) and will mention so if it is marginal for your build.
    ____Consider your PSU to be the foundation from which all else is built upon. Anything built upon a weak foundation is poorly built.

    Mine: ASRock Z77 Extreme6, i7-3770K, 16GB F3-14900CL9D-8GBSR, Seasonic X-750 Gold, On-die HD 4000, Corsair H80i, Antec Spot Cool, Fractal Design R4 Black Pearl w/Window
    Hers: ASRock 990FX Extreme4, FX-4170, 16GB AE316G1601U2K, Seasonic X-650 Gold, Asus HD7770-2GD5, Corsair H80i, Antec Spot Cool, Fractal Design R4 Black Pearl w/Window
    Server 1: ASRock 990FX Extreme9, FX-8150, 32GB AE316G1601U2K, Seasonic X-750 Gold, IBM ServeRAID M1015, PowerColor AX5450 1GBK3-SH, Corsair H80i, Antec Spot Cool, Fractal Design XL R2
    Server 2: ASRock FM2A88X Extreme6+, A10-6800K, 16GB F3-17000CL11D-8GBXL, Seasonic SS-660XP2, Fractal Design Arc Midi R2

  4. #4
    Vidkoym7 is offline Junior Member
    Join Date
    Oct 2013
    Location
    USA
    Posts
    5

    Default Re: Ubuntu 13.10 dmesg throws "[Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table"

    Thanks for replying. I've never used Hyper-V but what seems tricky about it is that it doesn't support raw PCI passthrough (existing cards must have some sort of SR-IOV support to virtualize). This means that there may be deeper features which Hyper-V doesn't check for but are used by Xen/VirtualBox in order to transparently expose the cards to the VMs. If the motherboard BIOS was implemented only far enough to only meet the standards of Hyper-V then that might be why it comes short on some other hypervisors.

    Here is an article which might help in finding possible general issues with a board. Sorry I can't be of much more help than that.
    Looking at the Hyper-V Event Log - Ben Armstrong - Site Home - MSDN Blogs

    Article on SR-IOV
    Overview of Single Root I/O Virtualization (SR-IOV) (Windows Drivers)

Thread Information

Users Browsing this Thread

There are currently 2 users browsing this thread. (0 members and 2 guests)

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •