Skip to contentSkip to conversation

AR9882 IOMMU faults

DISCUSSION Ben Skeggs 3 participants 4 messages Jul 8, 2016 Qualcomm Atheros ATH10K wireless driver

lore
Share & tools
lore

Ben Skeggs

author
#0 lore raw

Hey,

I've just installed a COMPEX WLE600VX (AR9882) in my router machine, operating in AP mode.

While it appears to be working well enough, I get massive floods of IOMMU faults reported in my kernel log. These appear to increase with the load on the network.

I've attached both the info that ath10k reports when it detects the device, and a sample of one of the DMAR messages (worth nothing that it's the same fault address in all the messages).

Is this a known issue, and anything I can do to help get it resolved?

Thanks,
Ben.

Jul 08 14:53:08 ramiel kernel: ath10k_pci 0000:04:00.0: Direct firmware load for ath10k/cal-pci-0000:04:00.0.bin failed with error -2
Jul 08 14:53:08 ramiel kernel: ath10k_pci 0000:04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
Jul 08 14:53:08 ramiel kernel: ath10k_pci 0000:04:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Jul 08 14:53:08 ramiel kernel: ath10k_pci 0000:04:00.0: firmware ver 10.2.4.70.52 api 5 features no-p2p,raw-mode,mfp crc32 67c4d25c
Jul 08 14:53:08 ramiel kernel: ath10k_pci 0000:04:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
Jul 08 14:53:08 ramiel kernel: ath10k_pci 0000:04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 1272.056416] DMAR: DRHD: handling fault status reg 3
[ 1272.057129] DMAR: DMAR:[DMA Write] Request device [04:00.0] fault addr ff9c0000 
               DMAR:[fault reason 05] PTE Write access is not set

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#1 lore raw

Logs are so limited. If possible, revert below commit and give a try

"ath10k: do not use coherent memory for allocated device memory chunks"

If revert is not so clean, try with this patch.

https://patchwork.kernel.org/patch/9175029/

-Rajkumar
________________________________________
From: ath10k <[email protected]> on behalf of Ben Skeggs <[email protected]>
Sent: Friday, July 8, 2016 10:59 AM
To: [email protected]
Subject: AR9882 IOMMU faults

Hey,

I've just installed a COMPEX WLE600VX (AR9882) in my router machine, operating in AP mode.

While it appears to be working well enough, I get massive floods of IOMMU faults reported in my kernel log. These appear to increase with the load on the network.

I've attached both the info that ath10k reports when it detects the device, and a sample of one of the DMAR messages (worth nothing that it's the same fault address in all the messages).

Is this a known issue, and anything I can do to help get it resolved?

Thanks,
Ben.

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#2 lore raw
Quoted 7 lines · Rajkumar

Logs are so limited. If possible, revert below commit and give a try

"ath10k: do not use coherent memory for allocated device memory chunks"

If revert is not so clean, try with this patch.

https://patchwork.kernel.org/patch/9175029/

I use this patch, I don't think it is upstream, and per comment, I have not tested this on other than x86 platform:

[greearb@ben-dt ath10k]$ git show 0e6e6f6b2
commit 0e6e6f6b2fac0ade990de56eef3841dbe7128f35

Author: Ben Greear <[email protected]>
Date:   Thu Jan 21 18:57:11 2016 -0800

ath10k: wmi-alloc-chunk should use DMA_BIDIRECTIONAL.

These memory chunks are often used as 'swap' by the NIC, so it will be both reading and writing to these areas.

This seems to fix errors like this on my x86-64 machine:

kernel: DMAR: DMAR:[DMA Write] Request device [05:00.0] fault addr ff5de000
DMAR:[fault reason 05] PTE Write access is not set

Should be tested and verified by someone who uses other platforms though...

drivers/net/wireless/ath/ath10k/wmi.c +1 -1
index af37a77..502f0e0 100644
@@ -4404,7 +4404,7 @@ static int ath10k_wmi_alloc_chunk(struct ath10k *ar, u32 req_id,
        if (!num_units)
                return -ENOMEM;
 
-       paddr = dma_map_single(ar->dev, vaddr, pool_size, DMA_TO_DEVICE);
+       paddr = dma_map_single(ar->dev, vaddr, pool_size, DMA_BIDIRECTIONAL);
        if (dma_mapping_error(ar->dev, paddr)) {
                kfree(vaddr);
                return -ENOMEM;

[greearb@ben-dt ath10k]$

Quoted 31 lines

-Rajkumar
________________________________________
From: ath10k <[email protected]> on behalf of Ben Skeggs <[email protected]>
Sent: Friday, July 8, 2016 10:59 AM
To: [email protected]
Subject: AR9882 IOMMU faults

Hey,

I've just installed a COMPEX WLE600VX (AR9882) in my router machine, operating in AP mode.

While it appears to be working well enough, I get massive floods of IOMMU faults reported in my kernel log. These appear to increase with the load on the network.

I've attached both the info that ath10k reports when it detects the device, and a sample of one of the DMAR messages (worth nothing that it's the same fault address in all the messages).

Is this a known issue, and anything I can do to help get it resolved?

Thanks,
Ben.

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

Signature · 7 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
author
#3 lore raw
Quoted 5 lines · Ben Greear
Quoted 2 lines · Rajkumar

Logs are so limited. If possible, revert below commit and give a try

Quoted 8 lines
Quoted 5 lines

"ath10k: do not use coherent memory for allocated device memory chunks"

If revert is not so clean, try with this patch.

https://patchwork.kernel.org/patch/9175029/

I use this patch, I don't think it is upstream, and per comment, I have not tested this on other than x86 platform:

Both the revert, and the change too DMA_BIDIRECTIONAL seem to resolve the issue here (also on x86).

Thank you!
Ben.

Quoted 38 lines

[greearb@ben-dt ath10k]$ git show 0e6e6f6b2
commit 0e6e6f6b2fac0ade990de56eef3841dbe7128f35

Author: Ben Greear <[email protected]>
Date:   Thu Jan 21 18:57:11 2016 -0800

ath10k: wmi-alloc-chunk should use DMA_BIDIRECTIONAL.

These memory chunks are often used as 'swap' by the NIC, so it will be both reading and writing to these areas.

This seems to fix errors like this on my x86-64 machine:

kernel: DMAR: DMAR:[DMA Write] Request device [05:00.0] fault addr
ff5de000
DMAR:[fault reason 05] PTE Write access is not set

Should be tested and verified by someone who uses other platforms though...

drivers/net/wireless/ath/ath10k/wmi.c +1 -1
index af37a77..502f0e0 100644
@@ -4404,7 +4404,7 @@ static int ath10k_wmi_alloc_chunk(struct ath10k
 *ar, u32 req_id,
        if (!num_units)
                return -ENOMEM;
 
-       paddr = dma_map_single(ar->dev, vaddr, pool_size, DMA_TO_DEVICE);
+       paddr = dma_map_single(ar->dev, vaddr, pool_size,
 DMA_BIDIRECTIONAL);
        if (dma_mapping_error(ar->dev, paddr)) {
                kfree(vaddr);
                return -ENOMEM;
Quoted 35 lines

[greearb@ben-dt ath10k]$

Quoted 32 lines

-Rajkumar
________________________________________
From: ath10k <[email protected]> on behalf of Ben Skeggs <[email protected]>
Sent: Friday, July 8, 2016 10:59 AM
To: [email protected]
Subject: AR9882 IOMMU faults

Hey,

I've just installed a COMPEX WLE600VX (AR9882) in my router machine, operating in AP mode.

While it appears to be working well enough, I get massive floods of IOMMU faults reported in my kernel log. These appear to increase with the load on the network.

I've attached both the info that ath10k reports when it detects the device, and a sample of one of the DMAR messages (worth nothing that it's the same fault address in all the messages).

Is this a known issue, and anything I can do to help get it resolved?

Thanks,
Ben.

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k