From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Lutomirski <luto@mit.edu>
Cc: ilw@linux.intel.com, linux-wireless@vger.kernel.org
Subject: Re: [3.0 regression] DMAR faults in iwlagn
Date: Wed, 22 Jun 2011 20:54:00 +0200 [thread overview]
Message-ID: <1308768840.29571.23.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <BANLkTikKia-UXL8LJ60sLDV1uZBFEP8Kwg@mail.gmail.com> (sfid-20110620_204449_827132_DD43A304)
On Mon, 2011-06-20 at 14:44 -0400, Andrew Lutomirski wrote:
> On 3.0-git today, I get:
>
> [ 40.142872] DRHD: handling fault status reg 2
> [ 40.142892] DMAR:[DMA Write] Request device [03:00.0] fault addr ffe38000
> [ 40.142896] DMAR:[fault reason 05] PTE Write access is not set
Reinette also said she saw this and kindly let me use one of her systems
to track it down.
It looks like this:
iwl_enqueue_hcmd : mapping 1 at ffce2000
dmar_fault : DMAR:[DMA Write] Request device [02:00.0] fault addr ffce2000
DMAR:[fault reason 05] PTE Write access is not set
So it's really due to my command changes, and the device is attempting
to write back to at least some commands. I see it doing that for PHY
calibration data, but I think on Reinette's system it was probably for
other commands as well since it happened a lot...
I think we have to map commands BIDI, even if I don't really understand
why.
johannes
next prev parent reply other threads:[~2011-06-22 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 18:44 [3.0 regression] DMAR faults in iwlagn Andrew Lutomirski
2011-06-20 19:06 ` wwguy
2011-06-20 19:21 ` Andrew Lutomirski
2011-06-20 19:15 ` Guy, Wey-Yi
2011-06-21 13:38 ` Johannes Berg
2011-06-21 13:55 ` wwguy
2011-06-22 18:54 ` Johannes Berg [this message]
2011-06-22 20:24 ` Johannes Berg
2011-06-22 20:26 ` Johannes Berg
2011-06-24 20:55 ` Kyle McMartin
2011-06-24 15:13 ` Andrew Lutomirski
2011-06-25 13:08 ` Johannes Berg
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=1308768840.29571.23.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luto@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).