From: Joerg Roedel <joro@8bytes.org>
To: Valdis.Kletnieks@vt.edu
Cc: Hans de Goede <hdegoede@redhat.com>, Tejun Heo <tj@kernel.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: DMAR error messages after 'shutdown -r'.
Date: Wed, 16 Mar 2016 18:46:08 +0100 [thread overview]
Message-ID: <20160316174608.GF2195@8bytes.org> (raw)
In-Reply-To: <22265.1457386917@turing-police.cc.vt.edu>
On Mon, Mar 07, 2016 at 04:41:57PM -0500, Valdis.Kletnieks@vt.edu wrote:
>
> lspci says:
> 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
>
> Not sure why I only see it on reboots - that means that when powering up, the kernel
> gets handed a device config it likes, but when rebooting, something is leaving the
> device in a config the kernel doesn't want to see.
Okay, so the BIOS defines one RMRR entry:
DMAR: RMRR base: 0x000000cdb11000 end: 0x000000cdb30fff
But the device-scope doesn't seem to match any existing devices in your
system. At least no device gets the RMRR mappings later on.
That doesn't really matter, as the the fault-address of 0xcdacd000 is
outside of the defined RMRR range anyway.
Looking at the fault-address as system physical, is would be in this
range of system memory:
BIOS-e820: [mem 0x00000000cd99b000-0x00000000ce3a0fff] reserved
Which is reserved for BIOS use. This looks very much like a missing RMRR
entry for that range, that has the sata controler in its device scope.
Joerg
prev parent reply other threads:[~2016-03-16 17:46 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
[not found] ` <20160216164745.GZ18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-03-07 21:41 ` Valdis.Kletnieks-PjAqaU27lzQ
2016-03-16 17:46 ` Joerg Roedel [this message]
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=20160316174608.GF2195@8bytes.org \
--to=joro@8bytes.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=hdegoede@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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).