Bug 81121 - WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/drivers/iommu/dmar.c:488 warn_invalid_dmar+0x7e/0x90()
Summary: WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/drivers/iommu/dmar.c:488...
Status: RESOLVED WILL_NOT_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-26 00:54 UTC by Cristian Aravena Romero
Modified: 2014-08-21 19:13 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.13.11.4
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg 3.13.11.4 (72.52 KB, text/x-log)
2014-07-26 00:54 UTC, Cristian Aravena Romero
Details
lspci -vvnn (12.14 KB, text/plain)
2014-07-26 00:55 UTC, Cristian Aravena Romero
Details

Description Cristian Aravena Romero 2014-07-26 00:54:35 UTC
Created attachment 144251 [details]
dmesg 3.13.11.4

[    0.000000] ------------[ cut here ]------------
[    0.000000] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/drivers/iommu/dmar.c:488 warn_invalid_dmar+0x7e/0x90()
[    0.000000] Your BIOS is broken; DMAR reported at address 0!
[    0.000000] BIOS vendor: Insyde; Ver: F.24; Product Version: 0882100000305E00000610100
[    0.000000] Modules linked in:
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.13.0-32-generic #57-Ubuntu
[    0.000000] Hardware name: Hewlett-Packard HP Pavilion 14 Notebook PC/2165, BIOS F.24 02/13/2014
[    0.000000]  000000000000000b ffffffff81c01de8 ffffffff8171bcb4 ffffffff81c01e30
[    0.000000]  ffffffff81c01e20 ffffffff810676cd ffffffff81fde008 ffffffff81fde048
[    0.000000]  0000000000000000 ffffffff81de12c0 ffffffff81c01fb0 ffffffff81c01e80
[    0.000000] Call Trace:
[    0.000000]  [<ffffffff8171bcb4>] dump_stack+0x45/0x56
[    0.000000]  [<ffffffff810676cd>] warn_slowpath_common+0x7d/0xa0
[    0.000000]  [<ffffffff81067784>] warn_slowpath_fmt_taint+0x44/0x50
[    0.000000]  [<ffffffff81d502c4>] ? early_ioremap+0x13/0x15
[    0.000000]  [<ffffffff81d45ee6>] ? __acpi_map_table+0x13/0x18
[    0.000000]  [<ffffffff815f2bae>] warn_invalid_dmar+0x7e/0x90
[    0.000000]  [<ffffffff81d8ab6e>] check_zero_address+0x68/0xf4
[    0.000000]  [<ffffffff81d8ac0f>] detect_intel_iommu+0x15/0xae
[    0.000000]  [<ffffffff81d3ffb5>] pci_iommu_alloc+0x4a/0x6c
[    0.000000]  [<ffffffff81d4fc61>] mem_init+0x17/0x9c
[    0.000000]  [<ffffffff81d35d3a>] start_kernel+0x202/0x443
[    0.000000]  [<ffffffff81d35941>] ? repair_env_string+0x5c/0x5c
[    0.000000]  [<ffffffff81d35120>] ? early_idt_handlers+0x120/0x120
[    0.000000]  [<ffffffff81d355ee>] x86_64_start_reservations+0x2a/0x2c
[    0.000000]  [<ffffffff81d35733>] x86_64_start_kernel+0x143/0x152
[    0.000000] ---[ end trace 488581fbeae80768 ]---
Comment 1 Cristian Aravena Romero 2014-07-26 00:55:08 UTC
Created attachment 144261 [details]
lspci -vvnn
Comment 2 Cristian Aravena Romero 2014-07-26 00:58:28 UTC
https://bugs.launchpad.net/linux/+bug/1348858
Comment 3 Alan 2014-07-29 15:10:37 UTC
"Your BIOS is broken; DMAR reported at address 0!"

as far as I can see this is not a Linux bug. 

You may find enabling the IOMMU in the BIOS makes the BIOS report something sensible

Note You need to log in before you can comment on or make changes to this bug.