All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>
To: Ben Skeggs <bskeggs@redhat.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: AR9882 IOMMU faults
Date: Fri, 8 Jul 2016 13:09:48 +0000	[thread overview]
Message-ID: <1467983388208.13042@qti.qualcomm.com> (raw)
In-Reply-To: <4b0fdabc-ff87-c182-7db6-68bf32755407@redhat.com>

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 <ath10k-bounces@lists.infradead.org> on behalf of Ben Skeggs <bskeggs@redhat.com>
Sent: Friday, July 8, 2016 10:59 AM
To: ath10k@lists.infradead.org
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
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2016-07-08 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08  5:29 AR9882 IOMMU faults Ben Skeggs
2016-07-08 13:09 ` Manoharan, Rajkumar [this message]
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=1467983388208.13042@qti.qualcomm.com \
    --to=rmanohar@qti.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=bskeggs@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.