On Fri, Feb 13, 2015 at 09:19:06AM -0500, Mark Hounschell wrote:
> OK. Attached.
Thanks, the IVRS table looks good. Device 0f.00.0 is listed there as the
alias target for a group of other devices:
> [ 1.405719] AMD-Vi: DEV_ALIAS_RANGE devid: 0f:01.0 flags:
> 00 devid_to: 0f:00.0
> [ 1.405722] AMD-Vi: DEV_RANGE_END devid: 12:1f.7
> BTW when I blacklist the aic7xxx driver [last
> unloaded: aic7xxx] I can load and unload any module all day long.
Okay, this driver seems to be the problem, it has a bug somewhere in
using the DMA-API. This causes the iommu problems.
The device it serves is behind the alias range for 0f:00.0, so any
faults from that device will show up as coming from 0f:00.0, like in the
io-page-faults you see in dmesg.
Joerg
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
