From: Guenter Roeck <linux@roeck-us.net>
To: linux-kernel@vger.kernel.org
Subject: WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar with Intel Motherboard
Date: Tue, 9 Jul 2013 13:24:06 -0700 [thread overview]
Message-ID: <20130709202406.GA11867@roeck-us.net> (raw)
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.
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 ]---
next reply other threads:[~2013-07-09 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 20:24 Guenter Roeck [this message]
2013-07-09 21:05 ` WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar with Intel Motherboard Bjorn Helgaas
2013-07-09 22:31 ` Guenter Roeck
2013-07-09 23:22 ` Chris Wright
2013-07-09 23:43 ` Guenter Roeck
2013-07-10 0:05 ` Chris Wright
2013-07-10 0:18 ` Guenter Roeck
2013-07-10 0:53 ` David Woodhouse
2013-07-10 3:55 ` Guenter Roeck
2013-07-11 19:00 ` Chris Wright
2013-07-11 20:59 ` Guenter Roeck
2013-07-11 22:31 ` Chris Wright
2013-08-14 9:36 ` 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=20130709202406.GA11867@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.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).