Bug 8887 - [Firmware Bug]: AMD-Vi: IOAPIC[2] not in IVRS table
Summary: [Firmware Bug]: AMD-Vi: IOAPIC[2] not in IVRS table
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-29 20:48 CET by Philippe Flat
Modified: 2015-03-28 21:16 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Extract of Dmesg (13.66 KB, application/octet-stream)
2013-01-29 20:50 CET, Philippe Flat
Details

Description Philippe Flat 2013-01-29 20:48:47 CET
Description of problem:
When booting, a message is displayed:
[    0.104882] [Firmware Bug]: AMD-Vi: IOAPIC[2] not in IVRS table
[    0.104886] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
[    0.104888] AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)

Version-Release number of selected component (if applicable):
Cauldron (beta1 up to date)

How reproducible:
Every time when IOMMU is activated in Bios
Motherboard: ASUS M4A89TD PRO USB3, BIOS 2001
No message in mageia1 on the same desktop.


Steps to Reproduce:
1.Enable IOMMU in the BIOS 
2.Boot
3.
Comment 1 Philippe Flat 2013-01-29 20:50:29 CET
Created attachment 3461 [details]
Extract of Dmesg

This is the part of dmesg where the trouble appears.
Comment 2 Nic Baxter 2015-02-25 04:40:19 CET
I have a very similar motherboard - M4A89GTD PRO USB3 and IOMMU is not supported on mine. I understand on other boards IOMMU is only supported for a subset of CPU. 
No comments for over 2 years should this be closed?

CC: (none) => nic

Comment 3 Marja Van Waes 2015-03-28 21:16:50 CET
(In reply to Nic Baxter from comment #2)
> I have a very similar motherboard - M4A89GTD PRO USB3 and IOMMU is not
> supported on mine. I understand on other boards IOMMU is only supported for
> a subset of CPU. 
> No comments for over 2 years should this be closed?

yeah, that's better than leaving it open forever

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD


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