linux-kernel - Re: DMAR error messages after 'shutdown -r'.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <22265.1457386917@turing-police.cc.vt.edu>
Date:	Mon, 07 Mar 2016 16:41:57 -0500
From:	Valdis.Kletnieks@...edu
To:	Joerg Roedel <joro@...tes.org>,
	Hans de Goede <hdegoede@...hat.com>,
	Tejun Heo <tj@...nel.org>
cc:	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org
Subject: Re: DMAR error messages after 'shutdown -r'.

(Sorry for the delay, $DAYJOB took a lot of cycles.  Adding AHCI maintainers to cc:)

On Tue, 16 Feb 2016 17:47:45 +0100, Joerg Roedel said:
> 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?

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.

Cold and warm boot dmesg's attached.


View attachment "dmesg.coldboot" of type "text/plain " (16884 bytes)

View attachment "dmesg.reboot" of type "text/plain " (17102 bytes)