From: Joerg Roedel <joro@8bytes.org>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
intel-gfx@lists.freedesktop.org
Cc: David Woodhouse <dwmw2@infradead.org>,
Jiang Liu <jiang.liu@linux.intel.com>
Subject: Re: dmar messages caused by graphics.
Date: Mon, 20 Oct 2014 12:05:38 +0200 [thread overview]
Message-ID: <20141020100537.GA10074@8bytes.org> (raw)
In-Reply-To: <20141017211716.GA9149@redhat.com>
Adding David and Jiang, they might have an idea whats going wrong.
On Fri, Oct 17, 2014 at 05:17:16PM -0400, Dave Jones wrote:
> Just hit this while fuzz-testing, (curiously, no graphics
> related stuff was happening, X isn't even loaded on that box).
>
> dmar: DRHD: handling fault status reg 2
> dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 7ffffff000
> DMAR:[fault reason 05] PTE Write access is not set
>
>
> 00:02:0 is..
>
> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
> Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00
> [VGA controller])
>
> 00: 86 80 12 04 07 04 90 00 06 00 00 03 00 00 00 00
> 10: 04 00 00 c0 00 00 00 00 0c 00 00 b0 00 00 00 00
> 20: 01 30 00 00 00 00 00 00 00 00 00 00 86 80 12 22
> 30: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00
>
>
> So then I rebooted, and noticed it spewed the exact same message on boot up too.
>
> I power cycled, and this time got
>
> [ 0.576231] dmar: Host address width 39
> [ 0.576336] dmar: DRHD base: 0x000000fed90000 flags: 0x0
> [ 0.576491] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 ecap f0101a
> [ 0.576659] dmar: DRHD base: 0x000000fed91000 flags: 0x1
> [ 0.576793] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap d2008020660462 ecap f010da
> [ 0.576961] dmar: RMRR base: 0x000000a2a1f000 end: 0x000000a2a32fff
> [ 0.577075] dmar: RMRR base: 0x000000ad800000 end: 0x000000af9fffff
> [ 6.715745] DMAR: No ATSR found
> [ 8.081845] [drm] DMAR active, disabling use of stolen memory
> [ 9.927343] dmar: DRHD: handling fault status reg 2
> [ 9.928335] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 3c11284000
> DMAR:[fault reason 05] PTE Write access is not set
> [ 11.916211] dmar: DRHD: handling fault status reg 2
> [ 11.917105] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 3c11284000
> DMAR:[fault reason 05] PTE Write access is not set
>
>
> Same thing, different fault address. It seems to change every time I boot.
>
>
> Looking in the logs, this started happening on the 15th. The first instance
> was this during boot..
>
> [ 9.917240] dmar: DRHD: handling fault status reg 2
> [ 9.918150] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 7300000000
> [ 9.918150] DMAR:[fault reason 05] PTE Write access is not set
> [ 9.919582] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 7ffffff000
> [ 9.919582] DMAR:[fault reason 05] PTE Write access is not set
> [ 10.157240] dmar: DRHD: handling fault status reg 3
> [ 10.158017] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 3579736000
> [ 10.158017] DMAR:[fault reason 05] PTE Write access is not set
> [ 11.926114] dmar: DRHD: handling fault status reg 3
> [ 11.927117] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 7300000000
> [ 11.927117] DMAR:[fault reason 05] PTE Write access is not set
>
> That time, the 'reg 3' showed up.
>
> Dying hardware ? Or bug ?
>
> Dave
>
next prev parent reply other threads:[~2014-10-20 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 21:17 dmar messages caused by graphics Dave Jones
2014-10-20 10:05 ` Joerg Roedel [this message]
2014-10-21 15:36 ` [Intel-gfx] " Daniel Vetter
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=20141020100537.GA10074@8bytes.org \
--to=joro@8bytes.org \
--cc=davej@redhat.com \
--cc=dwmw2@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jiang.liu@linux.intel.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 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).