public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: ath10k@lists.infradead.org
Cc: "open list:MEDIATEK MT76 WIRELESS LAN DRIVER"
	<linux-wireless@vger.kernel.org>
Subject: DMA write/fault when 802.11w is enabled
Date: Fri, 23 May 2025 10:07:40 -0700	[thread overview]
Message-ID: <bd2f333e-28e3-46bb-8b2b-b61537ea6288@gmail.com> (raw)

Hi,

After enabling 802.11w on some internal networks I noticed all of our 
ath10k client devices now show this during and just after every 
connection/roam. It started immediately after flipping to 802.11w on the 
APs, for every client running ath10k.

They are all running the QCA6174 hw3.2 WLAN.RM.4.4.1-00288-

I don't see it causing any delays or issues in the connection or 
afterwards, but it caught me off guard and was slightly concerning. 
Anyone else notice this with 802.11w enabled on the QCA6174?

kernel: DMAR: DRHD: handling fault status reg 2
kernel: DMAR: [DMA Write NO_PASID] Request device [02:00.0] fault addr 
0xffe4c000 [fault reason 0x05] PTE Write access is not set


                 reply	other threads:[~2025-05-23 17:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bd2f333e-28e3-46bb-8b2b-b61537ea6288@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.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