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: Tue, 21 Jun 2011 15:38:46 +0200 [thread overview]
Message-ID: <1308663526.4276.2.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
>
> lspci says:
>
> 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
>
> This seems to be triggered by interface state changes. The driver
> still works. I don't see this on 2.6.39.1.
Thanks Andy. Do you happen to know if there's any way to figure out what
ffe38000 was? Clearly the device is attempting to write something that
we haven't mapped properly, but I'm not sure _what_?
johannes
next prev parent reply other threads:[~2011-06-21 13:38 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 [this message]
2011-06-21 13:55 ` wwguy
2011-06-22 18:54 ` Johannes Berg
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=1308663526.4276.2.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).