linux-kernel - Re: WARNING: at drivers/iommu/dmar.c:484 warn_invalid

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]

Date:	Tue, 9 Jul 2013 15:31:06 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Joerg Roedel <joro@...tes.org>,
	"open list:INTEL IOMMU (VT-d)" <iommu@...ts.linux-foundation.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar with
 Intel Motherboard

On Tue, Jul 09, 2013 at 03:05:39PM -0600, Bjorn Helgaas wrote:
> [+cc Joerg, David, iommu list]
> 
> On Tue, Jul 9, 2013 at 2:24 PM, Guenter Roeck <linux@...ck-us.net> wrote:
> > I started seeing this problem after updating the BIOS trying fix another issue,
> > though I may have missed it earlier.
> >
> > I understand this is a BIOS bug. Would be great if someone can pass this on
> > to Intel BIOS engineers.
> 
> Maybe.  It'd be nice if Linux handled it better, though.
> 
If anyone has an idea how to do that, I'll be happy to write a patch.

Guenter

> > CPU is i7-4770K.
> >
> > Guenter
> >
> > ---
> >
> > [    0.000000] WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar+0x86/0xa0()
> > [    0.000000] Your BIOS is broken; DMAR reported at address 0!
> > [    0.000000] BIOS vendor: Intel Corp.; Ver: RLH8710H.86A.0320.2013.0606.1802; Product Version:
> > [    0.000000] Modules linked in:
> > [    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.10.0+ #1
> > [    0.000000] Hardware name:                  /DH87RL, BIOS RLH8710H.86A.0320.2013.0606.1802 06/06/2013
> > [    0.000000]  000000000000000b ffffffff81c01e20 ffffffff81671cfc ffffffff81c01e68
> > [    0.000000]  ffffffff81c01e58 ffffffff81043370 ffffffff81f6800c ffffffff81cbb520
> > [    0.000000]  0000000000000000 ffff88061fdaad40 00000000c73cc018 ffffffff81c01eb8
> > [    0.000000] Call Trace:
> > [    0.000000]  [<ffffffff81671cfc>] dump_stack+0x45/0x56
> > [    0.000000]  [<ffffffff81043370>] warn_slowpath_common+0x70/0xa0
> > [    0.000000]  [<ffffffff81043404>] warn_slowpath_fmt_taint+0x44/0x50
> > [    0.000000]  [<ffffffff81d162eb>] ? early_ioremap+0x13/0x15
> > [    0.000000]  [<ffffffff81d0d6a6>] ? __acpi_map_table+0x13/0x1a
> > [    0.000000]  [<ffffffff81548bf6>] warn_invalid_dmar+0x86/0xa0
> > [    0.000000]  [<ffffffff81d4b994>] check_zero_address+0x57/0xf7
> > [    0.000000]  [<ffffffff81d4ba49>] detect_intel_iommu+0x15/0xb6
> > [    0.000000]  [<ffffffff81d07d28>] pci_iommu_alloc+0x49/0x70
> > [    0.000000]  [<ffffffff81d15de4>] mem_init+0x17/0x9c
> > [    0.000000]  [<ffffffff81d01c54>] start_kernel+0x1c5/0x3e2
> > [    0.000000]  [<ffffffff81d01898>] ? repair_env_string+0x5e/0x5e
> > [    0.000000]  [<ffffffff81d015a3>] x86_64_start_reservations+0x2a/0x2c
> > [    0.000000]  [<ffffffff81d0169b>] x86_64_start_kernel+0xf6/0xf9
> > [    0.000000] ---[ end trace a7e3512e2fa85eaf ]---
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@...r.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/