From: Ben Skeggs <bskeggs@redhat.com>
To: ath10k@lists.infradead.org
Subject: AR9882 IOMMU faults
Date: Fri, 8 Jul 2016 15:29:05 +1000 [thread overview]
Message-ID: <4b0fdabc-ff87-c182-7db6-68bf32755407@redhat.com> (raw)
[-- Attachment #1.1.1.1: Type: text/plain, Size: 552 bytes --]
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.
[-- Attachment #1.1.1.2: dmesg-ath10k.txt --]
[-- Type: text/plain, Size: 731 bytes --]
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
[-- Attachment #1.1.1.3: dmesg-ath10k-dmar.txt --]
[-- Type: text/plain, Size: 206 bytes --]
[ 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
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2016-07-08 5:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 5:29 Ben Skeggs [this message]
2016-07-08 13:09 ` AR9882 IOMMU faults Manoharan, Rajkumar
2016-07-08 13:57 ` Ben Greear
2016-07-08 23:45 ` Ben Skeggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b0fdabc-ff87-c182-7db6-68bf32755407@redhat.com \
--to=bskeggs@redhat.com \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox