From: Jeremy Fitzhardinge <jeremy@goop.org>
To: NetDev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 3.0-rc1: DMAR errors from iwlagn
Date: Tue, 31 May 2011 14:14:14 -0700 [thread overview]
Message-ID: <4DE55A26.6040702@goop.org> (raw)
I have a Lenovo X220 with:
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at d2500000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlagn
Kernel modules: iwlagn
With 3.0-rc1, I'm seeing these in dmesg:
DRHD: handling fault status reg 2
DMAR:[DMA Write] Request device [03:00.0] fault addr ffe8a000
DMAR:[fault reason 05] PTE Write access is not set
DRHD: handling fault status reg 2
DMAR:[DMA Write] Request device [03:00.0] fault addr ffd5a000
DMAR:[fault reason 05] PTE Write access is not set
DRHD: handling fault status reg 2
DMAR:[DMA Write] Request device [03:00.0] fault addr ffd52000
DMAR:[fault reason 05] PTE Write access is not set
but the device seems to be working OK.
Thanks,
J
next reply other threads:[~2011-05-31 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 21:14 Jeremy Fitzhardinge [this message]
2011-06-01 23:34 ` 3.0-rc1: DMAR errors from iwlagn Jeremy Fitzhardinge
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=4DE55A26.6040702@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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