From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Valdis Kletnieks <Valdis.Kletnieks-PjAqaU27lzQ@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: DMAR error messages after 'shutdown -r'.
Date: Tue, 16 Feb 2016 17:47:45 +0100 [thread overview]
Message-ID: <20160216164745.GZ18805@8bytes.org> (raw)
In-Reply-To: <38172.1455047940-+bZmOdGhbsPr6rcHtW+onFJE71vCis6O@public.gmane.org>
On Tue, Feb 09, 2016 at 02:59:00PM -0500, Valdis Kletnieks wrote:
> [ 0.027629] Freeing SMP alternatives memory: 28K (ffffffff8e111000 - ffffffff8e118000)
> [ 0.048199] ftrace: allocating 31090 entries in 122 pages
> [ 0.061837] DMAR: Host address width 36
> [ 0.061841] DMAR: DRHD base: 0x000000fed90000 flags: 0x1
> [ 0.061894] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c9008020660262 ecap f0105a
> [ 0.061896] DMAR: RMRR base: 0x000000cdb11000 end: 0x000000cdb30fff
> [ 0.061899] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed90000 IOMMU 0
> [ 0.061901] DMAR-IR: HPET id 0 under DRHD base 0xfed90000
> [ 0.061903] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
> ---- Error here....
> [ 0.062027] DMAR: DRHD: handling fault status reg 2
> [ 0.062034] DMAR: DMAR:[DMA Read] Request device [00:1f.2] fault addr cdacd000
> DMAR:[fault reason 06] PTE Read access is not set
> ----
This is probably from a missing RMRR entry for device 00:1f.2. Can you
please post full dmesg after boot?
Thanks,
Joerg
next prev parent reply other threads:[~2016-02-16 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 19:59 DMAR error messages after 'shutdown -r' Valdis Kletnieks
[not found] ` <38172.1455047940-+bZmOdGhbsPr6rcHtW+onFJE71vCis6O@public.gmane.org>
2016-02-16 16:47 ` Joerg Roedel [this message]
[not found] ` <20160216164745.GZ18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-03-07 21:41 ` Valdis.Kletnieks-PjAqaU27lzQ
2016-03-16 17:46 ` Joerg Roedel
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=20160216164745.GZ18805@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=Valdis.Kletnieks-PjAqaU27lzQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).