Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1352010 > unrolled thread
| Started by | Valdis.Kletnieks@vt.edu |
|---|---|
| First post | 2016-03-07 22:50 +0100 |
| Last post | 2016-03-16 18:50 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: DMAR error messages after 'shutdown -r'. Valdis.Kletnieks@vt.edu - 2016-03-07 22:50 +0100
Re: DMAR error messages after 'shutdown -r'. Joerg Roedel <joro@8bytes.org> - 2016-03-16 18:50 +0100
| From | Valdis.Kletnieks@vt.edu |
|---|---|
| Date | 2016-03-07 22:50 +0100 |
| Subject | Re: DMAR error messages after 'shutdown -r'. |
| Message-ID | <rabcl-8ob-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
(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.
[toc] | [next] | [standalone]
| From | Joerg Roedel <joro@8bytes.org> |
|---|---|
| Date | 2016-03-16 18:50 +0100 |
| Message-ID | <rdnK2-3Gs-3@gated-at.bofh.it> |
| In reply to | #1352010 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web