From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: 3.6.8: dmar: DRHD: handling fault status reg 602
Date: Tue, 27 Nov 2012 10:16:45 -0500 [thread overview]
Message-ID: <00e101cdccb2$371dd780$a5598680$@lucidpixels.com> (raw)
In-Reply-To: <00e001cdccb2$1c4dfb10$54e9f130$@lucidpixels.com>
-----Original Message-----
From: Justin Piszcz [mailto:jpiszcz@lucidpixels.com]
Sent: Tuesday, November 27, 2012 10:16 AM
To: linux-kernel@vger.kernel.org
Subject: 3.6.8: dmar: DRHD: handling fault status reg 602
Hello,
Any idea why this is happening (e.g. why is PTE Read Access not set?)
[ 13.204560] dmar: DRHD: handling fault status reg 602
[ 13.208078] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
[ 13.208078] DMAR:[fault reason 06] PTE Read access is not set
[ 15.777874] dmar: DRHD: handling fault status reg 702
[ 15.777879] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
[ 15.777879] DMAR:[fault reason 06] PTE Read access is not set
[ 16.100453] dmar: DRHD: handling fault status reg 2
[ 16.100458] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
[ 16.100458] DMAR:[fault reason 06] PTE Read access is not set
[ 16.141058] dmar: DRHD: handling fault status reg 102
[ 16.141062] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
[ 16.141062] DMAR:[fault reason 06] PTE Read access is not set
[ 16.210102] dmar: DRHD: handling fault status reg 202
[ 16.210111] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
[ 16.210111] DMAR:[fault reason 06] PTE Read access is not set
[ 16.918149] ixgbe 0000:86:00.0: eth2: NIC Link is Up 10 Gbps, Flow
Control: RX/TX
This is from:
http://lkml.org/lkml/2012/11/27/263
Justin.
--
Hi,
Disregard, appears to be a nouveau bug:
https://bugzilla.redhat.com/show_bug.cgi?id=573173
Justin.
next prev parent reply other threads:[~2012-11-27 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 15:16 3.6.8: dmar: DRHD: handling fault status reg 602 Justin Piszcz
2012-11-27 15:16 ` Justin Piszcz [this message]
2012-11-28 1:17 ` Robert Hancock
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='00e101cdccb2$371dd780$a5598680$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@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 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.