Re: ath9k and AMD IOMMU alias breakage on 3.16?

Hi Joerg,

I've performed both experiments you've asked for.

intremap=off seems to have everything working with the IOMMU on
although I've only been running it for a few minutes and not tested
things exhaustively.

The ivrs_ioapic test however results in ath9k failing to load.

I've attached dmesg's of both test cases.

Also, I noticed SWIOTLB is in use - is that common with a IOMMU these days?

-Jason

On Fri, Sep 12, 2014 at 9:17 AM, Joerg Roedel [off-list ref] wrote:

Hi Jason,

On Fri, Sep 05, 2014 at 10:28:01PM -0700, Jason Newton wrote:

quoted

[    0.021820] AMD-Vi: device: 00:00.2 cap: 0040 seg: 0 flags: b8 info 0000
[    0.021827] AMD-Vi:        mmio-addr: 00000000feb80000
[    0.021844] AMD-Vi:   DEV_SELECT_RANGE_START        devid: 00:01.0 flags: 00
[    0.021848] AMD-Vi:   DEV_RANGE_END                 devid: ff:1f.6
[    0.022730] AMD-Vi:   DEV_ALIAS_RANGE               devid: 02:00.0 flags: 00 devid_to: 00:14.4
[    0.022735] AMD-Vi:   DEV_RANGE_END                 devid: 02:1f.7
[    0.022745] AMD-Vi:   DEV_SPECIAL(HPET[0])         devid: 00:14.0
[    0.022749] AMD-Vi:   DEV_SPECIAL(IOAPIC[5])               devid: 00:14.0
[    0.022753] AMD-Vi:   DEV_SPECIAL(IOAPIC[6])               devid: 00:00.0

It is just a test, as I don't know how the hardware is actually wired in
your system, but can you try to boot with 'ivrs_ioapic[6]=00:00.1' on
the kernel command line and report if it makes any difference?

Thanks,

        Joerg