Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753317Ab3GIVGC (ORCPT ); Tue, 9 Jul 2013 17:06:02 -0400 Received: from mail-oa0-f49.google.com ([209.85.219.49]:57347 "EHLO mail-oa0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751950Ab3GIVGA (ORCPT ); Tue, 9 Jul 2013 17:06:00 -0400 MIME-Version: 1.0 In-Reply-To: <20130709202406.GA11867@roeck-us.net> References: <20130709202406.GA11867@roeck-us.net> From: Bjorn Helgaas Date: Tue, 9 Jul 2013 15:05:39 -0600 Message-ID: Subject: Re: WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar with Intel Motherboard To: Guenter Roeck Cc: "linux-kernel@vger.kernel.org" , Joerg Roedel , "open list:INTEL IOMMU (VT-d)" , David Woodhouse Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2674 Lines: 52 [+cc Joerg, David, iommu list] On Tue, Jul 9, 2013 at 2:24 PM, Guenter Roeck 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. > 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] [] dump_stack+0x45/0x56 > [ 0.000000] [] warn_slowpath_common+0x70/0xa0 > [ 0.000000] [] warn_slowpath_fmt_taint+0x44/0x50 > [ 0.000000] [] ? early_ioremap+0x13/0x15 > [ 0.000000] [] ? __acpi_map_table+0x13/0x1a > [ 0.000000] [] warn_invalid_dmar+0x86/0xa0 > [ 0.000000] [] check_zero_address+0x57/0xf7 > [ 0.000000] [] detect_intel_iommu+0x15/0xb6 > [ 0.000000] [] pci_iommu_alloc+0x49/0x70 > [ 0.000000] [] mem_init+0x17/0x9c > [ 0.000000] [] start_kernel+0x1c5/0x3e2 > [ 0.000000] [] ? repair_env_string+0x5e/0x5e > [ 0.000000] [] x86_64_start_reservations+0x2a/0x2c > [ 0.000000] [] 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@vger.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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/