Hi,
when starting a video I'm getting the following error with activated IOMMU under Coreboot:
[ 230.800362] AMD-Vi: Event logged [ [ 230.800368] IO_PAGE_FAULT device=08:00.0 domain=0x0000 address=0x0000000073700000 flags=0x0050] [ 230.800371] AMD-Vi: Event logged [ [ 230.800373] IO_PAGE_FAULT device=08:00.0 domain=0x0000 address=0x0000000073700040 flags=0x0050] [ 230.800375] AMD-Vi: Event logged [ [ 230.800376] IO_PAGE_FAULT device=08:00.0 domain=0x0000 address=0x0000000073700000 flags=0x0050] [ 230.800377] AMD-Vi: Event logged [ [ 230.800378] IO_PAGE_FAULT device=08:00.0 domain=0x0000 address=0x0000000073700040 flags=0x0050]
There are over 100 lines in dmesg and it's caused by my Xonar DX sound card. With the proprietary BIOS everthing works fine. I'm using the latest Linux-kernel and the Raptor build config for Coreboot.
This is basically the same bug: https://bugzilla.kernel.org/show_bug.cgi?id=111711
Hey silly question did you turn on IOMMU in the vendor BIOS? by default it is off.
This is caused by a bad driver or bad hardware, I had a old graphics card that did the same.
My D16 works fine and I am able to assign a variety of devices to VM's with vfio, I doubt this is a coreboot issue.
On 2017-05-04 05:52, Taiidan@gmx.com wrote:
Hey silly question did you turn on IOMMU in the vendor BIOS? by default it is off.
This is caused by a bad driver or bad hardware, I had a old graphics card that did the same.
My D16 works fine and I am able to assign a variety of devices to VM's with vfio, I doubt this is a coreboot issue.
Yes, I turned it on and everything works fine. I use it to passthrough my graphics card to my virtual machine.
On 05/04/2017 01:50 PM, lowsec@airmail.cc wrote:
On 2017-05-04 05:52, Taiidan@gmx.com wrote:
Hey silly question did you turn on IOMMU in the vendor BIOS? by default it is off.
This is caused by a bad driver or bad hardware, I had a old graphics card that did the same.
My D16 works fine and I am able to assign a variety of devices to VM's with vfio, I doubt this is a coreboot issue.
Yes, I turned it on and everything works fine. I use it to passthrough my graphics card to my virtual machine.
Hmm...strange. I have no idea as to why this is happening. Thanks for bringing this up btw, I was about to buy one for my VM gaming setup.
My guess is that it is related to the fact that ASUS's PCI-e audio cards use a PCI audio chip, and thus require a PCI-e>PCI bridge. I hope they release some native PCI-e audio cards soon.
Shot in the dark - but can you post your lspci -vv and IOMMU groups from both the vendor bios and coreboot?
-
lowsec＠airmail.cc -
Taiidan＠gmx.com